Since I do not see any objections to the DISCUSS thread, moving this to VOTE thread.
On Mon, Apr 19, 2021 at 10:04 AM Aravindan Vijayan <avija...@cloudera.com> wrote: > Hello all, > > I would like to propose merging the work done for supporting non rolling > upgrades in Ozone (HDDS-3698-nonrolling-upgrade) into the Ozone master > branch. > > As part of the upgrade framework, the following have been added > > - Ability to create layout features & versions > - Ability to finalize and upgrade an Ozone cluster, as well as > downgrade before finalization. > - Ability to add custom actions to be executed as upgrade hooks in > different phases. > - Ability to 'prepare' an Ozone manager quorum for upgrade. > > We believe that the branch is ready for merge due to the following reasons > > - We have resolved around 60 JIRAs (including 6 Apache Ratis fixes). > There are about 3-4 remaining JIRAs that are currently in progress (or > under review) which are not blockers and are close to completion. > - The merge checklist has been looked at and filled in at > > https://cwiki.apache.org/confluence/display/OZONE/Non-Rolling+Upgrade+Framework+Merge+Checklist > . > - A broad range of test cases have been added including unit tests, > integration tests to perform finalization & upgrade, failure injection > testing in HDDS layer finalization and acceptance tests to perform a > prepare operation and a docker based upgrade flow from the last released > version to current. > - Sufficient documentation has been added for the design (here > > <https://issues.apache.org/jira/secure/attachment/13023446/Ozone%20Non-Rolling%20Upgrades%20Doc%20v1.2%20%28Implemented%20Design%29.pdf> > & here > > <https://issues.apache.org/jira/secure/attachment/13015490/OM%20Prepare%20Upgrade.pdf>), > usage (here > > <https://github.com/apache/ozone/blob/HDDS-3698-nonrolling-upgrade/hadoop-hdds/docs/content/feature/how-to-do-a-nonrolling-upgrade.md>) > and developer primer (here > > <https://github.com/apache/ozone/blob/HDDS-3698-nonrolling-upgrade/hadoop-hdds/docs/content/design/upgrade-dev-primer.md> > ). > > There is some work needed to onboard the work done for HDDS-2939 into the > upgrade branch. If that branch is merged first, then the onboarding can be > done before the upgrade branch merge through a single patch. > > Please provide your feedback. If there are no objections, I will proceed > with starting a vote thread for merging. > > -- > Thanks & Regards, > Aravindan > -- Thanks & Regards, Aravindan
