[ 
https://issues.apache.org/jira/browse/HDDS-17527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anurag Parvatikar reassigned HDDS-17527:
----------------------------------------

    Assignee: Anurag Parvatikar

> Migrate Storage Policy to the post-ZDU OM component-version framework
> ---------------------------------------------------------------------
>
>                 Key: HDDS-17527
>                 URL: https://issues.apache.org/jira/browse/HDDS-17527
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: Ozone Manager
>            Reporter: Devesh Kumar Singh
>            Assignee: Anurag Parvatikar
>            Priority: Major
>
> After merging upstream ZDU into HDDS-11233, remove the feature-specific 
> BUCKET_STORAGE_POLICY_SUPPORT(12) registration from legacy OMLayoutFeature 
> and introduce it at the next available, nonconflicting OzoneManagerVersion 
> value. Migrate callers, upgrade actions, initialization and tests to the 
> post-ZDU version manager. Audit persisted VERSION and DB apparent-version 
> handling for feature-branch environments that may have finalized legacy 
> layout 12; document whether migration or test-cluster reinitialization is 
> required. Preserve historic layout IDs and upstream version sequencing.
> *Why a gate is needed:* The OM apparent version is the server-side authority 
> for whether new policy metadata may be persisted. A wrong enum sequence can 
> enable the feature early, make startup fail, or break downgrade safety.
> *Acceptance criteria:* Correct new enum and ordering; no stale 
> feature-specific layout references; old supported apparent versions load; 
> version-12 compatibility decision recorded; tests cover nextVersion, 
> isAllowed, finalization, persistence and restart. Source anchors: 
> OzoneManagerVersion, OMVersionManager, OMLayoutFeature.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to