mirror of
https://github.com/rustfs/rustfs.git
synced 2026-07-26 16:28:15 +00:00
20 KiB
20 KiB
Architecture Migration Progress
Status values: [ ] not started, [~] in progress, [x] complete, [!] blocked.
Current Context
- Issue:
rustfs/backlog#660 - Branch:
overtrue/arch-storage-api-helper-cleanup - Baseline:
origin/mainat2f7cc7cb9e5891b46db6e686c67636e9343762ce - PR type for this branch:
dependency-migration - Runtime behavior changes: none.
- Rust code changes: narrow scanner data-usage cache load/save helper generic
bounds away from full
StorageAPIwhere helpers only need object I/O. - CI/script changes: none.
- Docs changes: record API-010 completion and the current scanner cache bound-narrowing context, verification evidence, and expert review outcomes.
Phase 0 Tasks
G-001Refreshmainand record baseline.- Acceptance: baseline commit, title, and branch are recorded.
- Verification:
git fetch upstream main --prune;git rev-parse upstream/main.
G-002Create migration tracking checklist.- Acceptance: this file records task state, context, verification, and handoff.
G-003Classify PR types.- Acceptance:
crate-boundaries.mdlists exactly one allowed PR type per PR.
- Acceptance:
G-004Define re-export and wrapper policy.- Acceptance: temporary compatibility code must use
RUSTFS_COMPAT_TODO.
- Acceptance: temporary compatibility code must use
G-005Add dependency direction guard.- Acceptance:
./scripts/check_layer_dependencies.shpasses on currentupstream/mainwhile still rejecting new unaccepted layer dependencies.
- Acceptance:
- [~]
G-006Create migration loss-prevention checks.- Current branch: add a mechanical admin route matrix guard from
admin-route-action-snapshot.mdandrustfs/src/admin/route_registration_test.rs. - Remaining follow-up: add checks for public re-export and storage trait coverage before pure moves.
- Current branch: add a mechanical admin route matrix guard from
G-007Create startup timeline table.- Acceptance:
startup-timeline.mdrecords current binary startup order, side effects, fatal boundaries, and readiness stages.
- Acceptance:
G-008Capture admin route-action snapshot.- Acceptance:
admin-route-action-snapshot.mdrecords current route families, handler ownership, authorization actions, public exceptions, table-catalog routes, and/minio/admincompatibility alias behavior.
- Acceptance:
G-009Enforce pre-push three-expert review.- Acceptance:
crate-boundaries.mdrequires quality/architecture, migration-preservation, and testing/verification review before push.
- Acceptance:
G-010Inventoryecstore::config::{Config, KV, KVS}consumers.- Acceptance:
ecstore-config-consumer-inventory.mdrecords the current model definitions, global accessors, persistence helpers, consumer groups, migration risks, and do-not-change contract.
- Acceptance:
TEST-PRTYPE-001Check PR type enum consistency.- Acceptance:
./scripts/check_architecture_migration_rules.shparses the allowed PR types fromcrate-boundaries.mdand fails whenARCHITECTURE.mdor architecture docs reference an unknown PR type.
- Acceptance:
COMPAT-REG-001Check temporary compatibility cleanup consistency.- Acceptance:
./scripts/check_architecture_migration_rules.shfails when a sourceRUSTFS_COMPAT_TODO(<task-id>)marker lacks a cleanup-register entry, when a register entry lacks a source marker, or when a source marker omits a removal condition.
- Acceptance:
Phase 1a Config Model Tasks
CFG-001Inventoryecstore::config::{Config, KV, KVS}consumers.- Acceptance:
ecstore-config-consumer-inventory.mdrecords the current definitions, persistence helpers, global accessors, consumer groups, migration risks, and do-not-change contract.
- Acceptance:
CFG-002Decide model boundary.- Acceptance:
config-model-boundary-adr.mdrecordsrustfs-configas the target package,server_configas the future model module, allowed dependencies, forbidden dependencies, preserved shape, and extraction verification gates.
- Acceptance:
CFG-003Move pure model definitions.- Next boundary: move only
Config,KV,KVS, and default-registration surface intorustfs-config; keep persistence helpers and global server-config state inecstore.
- Next boundary: move only
CFG-004Keep oldecstore::config::*compatibility path.- Required compatibility: source must contain
RUSTFS_COMPAT_TODO(CFG-004)and a matching cleanup-register entry.
- Required compatibility: source must contain
Phase 1 Security Governance Tasks
S-001Addcrates/security-governance.- Acceptance: the crate is a workspace member and has no dependency on
rustfs,ecstore, admin handlers, Axum, or runtime state. - Verification:
cargo check -p rustfs-security-governance.
- Acceptance: the crate is a workspace member and has no dependency on
S-002Add admin route matrix core types.- Acceptance:
AdminRouteSpec,AdminRouteAccess,AdminActionRef,PublicRouteKind,RouteRiskLevel, and validation errors model route governance metadata without registering routes or enforcing auth. - Verification:
cargo test -p rustfs-security-governance.
- Acceptance:
S-003Add redaction contract types.- Acceptance:
RedactionRule,RedactionLevel, and validation errors model sensitive field handling without logging, masking, or runtime integration. - Verification:
cargo test -p rustfs-security-governance.
- Acceptance:
S-004Add serde policy marker types.- Acceptance:
SerdePolicy,SerdePolicyKind,UnknownFieldPolicy, and validation errors model strict ingress and compatibility serde contracts without changing deserialization behavior. - Verification:
cargo test -p rustfs-security-governance.
- Acceptance:
S-005Add supply-chain policy contract types.- Acceptance:
ArtifactIntegrityPolicy,ArtifactSourceKind, and validation errors model digest, signature, and provenance requirements without changing release or CI behavior. - Verification:
cargo test -p rustfs-security-governance.
- Acceptance:
S-006Addrustfs/src/admin/route_policy.rsbacked by these contract types, without changing route registration or auth behavior.- Acceptance: direct
AdminRouteSpecentries cover routes with a single stable admin policy action, deferred inventory records routes that need richer contract support, and tests prove the combined inventory covers every registered admin route.
- Acceptance: direct
S-011Add KMS action taxonomy.- Acceptance:
KmsActioncan parse and serialize dedicated configure, service-control, clear-cache, generate-data-key, delete, rotate, list, and describe actions; wildcard matching still works. - Verification:
cargo test -p rustfs-policy action --no-fail-fast.
- Acceptance:
S-012Migrate KMS handlers to dedicated actions.- Acceptance: KMS data-key, delete/cancel-delete, cache, configure,
service-control, list, and describe handlers use dedicated
kms:*actions. - Compatibility: legacy KMS create/status admin actions are retained only as
temporary compatibility paths and registered in
compat-cleanup-register.md. - Verification: focused handler and route policy tests, migration rules,
formatting, and
make pre-commit.
- Acceptance: KMS data-key, delete/cancel-delete, cache, configure,
service-control, list, and describe handlers use dedicated
S-013Apply KMS redaction.- Acceptance: KMS Debug output and admin status response summaries contain no Vault token, AppRole secret ID, or local master key values.
- Must preserve: internal KMS config values remain available to runtime code and persisted config serialization still writes the original secret values.
- Verification: focused KMS redaction/status tests, full KMS tests, migration
guards, Rust quality scan, clippy, and
make pre-commitpassed.
KMSD-001Inventory KMS development defaults.- Acceptance:
kms-development-defaults-inventory.mdrecords Local and Vault defaults for missing master keys, temp key dirs, HTTP Vault addresses, default dev-token credentials, and skip-TLS behavior. - Must preserve: no KMS runtime behavior, config serialization, authorization, startup order, storage path, or crate boundary changes.
- Verification: docs diff review, migration guards, metrics reference guard,
and
git diff --check.
- Acceptance:
Phase 2 Storage API Tasks
-
API-001Addcrates/storage-api.- Acceptance:
rustfs-storage-apiis a workspace member and remains a dependency-free contract crate. - Verification:
cargo check -p rustfs-storage-api.
- Acceptance:
-
API-002Move public storage error/result contracts.- Current PR:
rustfs/rustfs#3313merged. - Completed slice: add public
StorageErrorCodeandStorageResultcontracts inrustfs-storage-api, then make ECStoreStorageError::to_u32/from_u32consume the shared code table. - Deferred: keep the full ECStore
StorageErrorenum and ECStore-specific conversions inrustfs-ecstoreuntil theDiskError, filemeta, lock, andstd::io::Errordowncast boundary is proven safe. - Acceptance: storage-api contract tests pass, ECStore compatibility tests
prove numeric codes match the new contract, and
cargo check -p rustfs-storage-api -p rustfs-ecstorepasses. - Must preserve: storage error display, conversions, object error mapping,
quorum classification, and reserved code gaps
0x2B/0x2C. - Risk defense: no storage hot-path enum move in this PR; only numeric code mapping uses the new contract.
- Current PR:
-
API-003Move DTOs.- Current PR:
rustfs/rustfs#3314merged. - Completed slice: move the pure bucket/options DTO subset:
MakeBucketOptions,SRBucketDeleteOp,DeleteBucketOptions,BucketOptions, andBucketInfo. - Acceptance:
rustfs-storage-apiexports these DTOs, ECStore re-exports them from the oldecstore::store_apipath, and compatibility cleanup is registered withRUSTFS_COMPAT_TODO(API-003). - Must preserve: no
ObjectOptions,ObjectInfo, reader, compression, encryption, filemeta conversion, multipart conversion, route, storage, or runtime behavior changes in this PR.
- Current PR:
-
API-006Add disk inventory/admin trait.- Current PR:
rustfs/rustfs#3330merged. - Completed slice: add
StorageAdminApiandDiskSetSelectortorustfs-storage-api. - Acceptance:
StorageAdminApiexposes backend info, global storage info, local storage info, disk-set inventory, and drive-count surfaces without depending on ECStore implementation types. - Must preserve: no
StorageAPI::get_disksremoval, no ECStore implementation change, no admin/readiness/capacity behavior change. - Risk defense: use associated types for backend/storage/disk DTOs so this
contract slice does not pull
rustfs-madminorrustfs-ecstoreintorustfs-storage-api. - Verification: focused storage-api tests, dependency tree, migration guards, formatting, and diff hygiene.
- Current PR:
-
API-007Dual-routeget_disksconsumers.- Completed first slice:
rustfs/rustfs#3331boundECStoretoStorageAdminApiwhile keeping all consumers unchanged. - Completed second slice:
rustfs/rustfs#3332migrated the admin storage-class config drive-count consumer toStorageAdminApi::set_drive_counts. - Completed third slice:
rustfs/rustfs#3333migratedDefaultAdminUsecasestorage-info reads toStorageAdminApi::storage_info. - Completed fourth slice:
rustfs/rustfs#3334migrated account-infobackend_info, rebalance statusstorage_info, and runtime readinessstorage_info. - Completed fifth slice:
rustfs/rustfs#3335migrated grouped observability, RPC health, server-info, realtime metrics, and notification read-side consumers. - Completed sixth slice:
rustfs/rustfs#3336migrated ECStore internal decommission space, local-storage-info, backend-info, drive-count, and disk-inventory admin handlers away from oldStorageAPImethod calls. - Completed seventh slice:
rustfs/rustfs#3337migrated maintenance and background read-side storage inventory consumers in rebalance metadata initialization, heal resume disk lookup, and scanner local disk scan lookup. - Completion acceptance: admin inventory consumers no longer use old
StorageAPIcalls for backend info, storage info, local storage info, drive-count, or disk-set inventory when the inventory-facingStorageAdminApicontract represents the same read-only operation.
- Completed first slice:
-
API-008Remove duplicate old-path admin surfaces.- Completed slice:
rustfs/rustfs#3340removed duplicate admin-read methods from the oldStorageAPItrait and its ECStore/Sets/SetDisks/test implementations after API-007 migrated their consumers. - Acceptance: old
StorageAPIkeeps storage operation traits andnew_ns_lock, while admin inventory surfaces live only onStorageAdminApi.
- Completed slice:
-
API-009Narrow metadata helper storage bounds.- Completed slice:
rustfs/rustfs#3343narrowed server config, tier config, rebalance metadata, and startup metadata migration helper bounds away from fullStorageAPIwhen the helper only needsObjectIO,ObjectOperations,BucketOperations,ListOperations, orStorageAdminApi. - Acceptance: metadata helper contracts express the actual operation group they need, while callers and persistence behavior remain unchanged.
- Completed slice:
-
API-010Narrow replication resync metadata bounds.- Completed slice:
rustfs/rustfs#3345narrowed replication resync status load/save/mark/persist helper bounds away from fullStorageAPIwhen the helper only needsObjectIO. - Acceptance: resync metadata helpers express object-I/O-only persistence
requirements, while replication execution, delete replication, multipart
replication, object lookups, and scheduling behavior remain on full
StorageAPIwhere needed.
- Completed slice:
-
[~]
API-011Narrow scanner cache helper storage bounds.- Current branch slice: narrow scanner data-usage cache load/save and cache
snapshot persistence helper bounds away from full
StorageAPIwhen the helper only needsObjectIO. - Acceptance: scanner cache persistence helpers express object-I/O-only requirements, while scanner cycle orchestration, bucket scanning, local disk selection, cache publication, and storage hot paths remain unchanged.
- Must preserve: data-usage cache wire format, cache object paths, backup cache paths, retry and timeout behavior, cache-save metrics, publish/update channel behavior, scanner cycle scheduling, disk scan concurrency, bucket scan semantics, lifecycle/replication decisions, and storage hot paths.
- Risk defense: do not move traits to
rustfs-storage-api, do not removeStorageAPI, do not alter helper bodies, and do not narrow scanner paths that need bucket operations, disk inventory, or full storage orchestration. - Verification: focused compile/tests, migration guards, and Rust risk scan passed; required quality/architecture, migration-preservation, and testing/verification review is pending before push.
- Current branch slice: narrow scanner data-usage cache load/save and cache
snapshot persistence helper bounds away from full
Phase 8 Background Controller Tasks
BGC-001Inventory background services.- Acceptance:
background-services-inventory.mdrecords scanner, heal, lifecycle, replication, config reload, metrics, shutdown, cancellation, and side-effect surfaces before controller work. - Must preserve: no code behavior change and no new controller contract in this PR.
- Verification: docs-only architecture checks and diff hygiene.
- Acceptance:
BGC-002Define minimal controller contract.- Acceptance:
background-controller-contract.mddefines desired/current/status/reconcile vocabulary, status state semantics, service boundaries, and side-effect rules without starting workers or changing scheduling. - Must preserve: no Rust trait, scheduler, service registry, worker start/stop path, storage write, readiness change, peer signal, or runtime behavior change.
- Verification: docs-only architecture checks and diff hygiene.
- Acceptance:
Next PRs
dependency-migration: narrow scanner data-usage cache helper bounds away from fullStorageAPIwhere the helper only needsObjectIO.api-extraction: move only the pure server-config model into rustfs-config as CFG-003.api-extraction: keep the old rustfs_ecstore::config::* path with RUSTFS_COMPAT_TODO(CFG-004) and cleanup-register coverage.consumer-migration: migrate external consumers one group at a time only after the model path and compatibility shim are stable.security-change: make Local KMS unsafe defaults explicit development opt-ins or production failures in KMSD-002.security-change: make Vault unsafe defaults explicit development opt-ins or production failures in KMSD-003.
Pre-Push Review Log
| Expert | Status | Notes |
|---|---|---|
| Quality/architecture | pass | Confirmed the Rust diff only narrows scanner cache helper bounds from StorageAPI to ObjectIO; helper bodies, scanner orchestration, bucket/disk/lifecycle/replication paths, and storage hot paths are unchanged. |
| Migration preservation | pass | Confirmed ObjectIO covers the actual get_object_reader and put_object calls, while cache wire format, object paths, backup behavior, retry/timeouts, metrics, publish/update flow, scanner scheduling, concurrency, and bucket scanning remain unchanged. |
| Testing/verification | pass | Confirmed the focused compile, data_usage and scanner_io tests, migration guards, diff hygiene, and added-line risk scan are sufficient for this generic-bound-only slice, so full pre-commit can be skipped under the current larger-granularity instruction. |
Verification Notes
Passed:
cargo fmt --all.cargo check -p rustfs-scanner -p rustfs-ecstore -p rustfs --lib.cargo fmt --all --check.cargo test -p rustfs-scanner data_usage --lib; 21 passed.cargo test -p rustfs-scanner scanner_io --lib; 18 passed../scripts/check_architecture_migration_rules.sh../scripts/check_layer_dependencies.sh../scripts/check_metrics_migration_refs.sh../scripts/check_unsafe_code_allowances.sh.git diff --check.- Rust code-quality scan on changed
.rsfiles, plus added-line scan for unwrap/expect, numeric casts,Result<_, String>,Box<dyn Error>, println/eprintln, andOrdering::Relaxed; broad full-file matches are pre-existing touched-file patterns, and the added-line scan found no new risky code patterns.
Notes:
- Full pre-commit is intentionally skipped when the focused tests and guards pass, per the current instruction to increase PR granularity.
- This slice changes generic bounds and imports only; helper bodies, cache object paths, backup paths, retry/timeout behavior, metrics, and publish logic are unchanged.
- Scanner orchestration paths intentionally still require full
StorageAPIwhere they use bucket operations, disk inventory, or broader storage orchestration. - No temporary compatibility shim was added.
Handoff Notes
- Keep this API-011 slice as a
dependency-migrationPR that only narrows scanner data-usage cache helper generic bounds. - Do not remove
StorageAPIitself, object operation traits, ornew_ns_lockin this PR. - Do not move traits into
rustfs-storage-apior introduce new compatibility shims in this PR. - Do not alter data-usage cache wire format, cache object paths, backup paths, retry/timeout behavior, metrics, update publication, scanner cycle orchestration, bucket scanning, disk scan concurrency, heal object repair, object APIs, or storage hot-path consumers in this PR.
- Do not add temporary compatibility code unless a matching
RUSTFS_COMPAT_TODO(<task-id>)marker and cleanup-register entry are added.