errose28 opened a new pull request, #11039:
URL: https://github.com/apache/ozone/pull/11039

   ## What changes were proposed in this pull request?
   
   Acceptance tests on the ZDU branch are currently doing a rolling restart 
within the same version, since Ozone must be upgraded to the first ZDU 
compatible version before starting a ZDU. On master, we will need to switch 
back to doing a non-rolling upgrade from the last release to latest master.
   
   This change splits the old and new finalization CLIs into two different sets 
of robot files stored under `non-rolling` and `rolling` upgrade subdirectories. 
This leaves the new CLIs reserved for the rolling upgrade flow and old CLIs for 
the non-rolling flow. This avoids adding a new split using the new CLIs for the 
non-rolling flow. Since new clients are backwards compatible with the old CLIs, 
we can continue to run non-rolling upgrade to the latest version using the old 
CLIs.
   
   This implementation requires HDDS-16025. Even though the clients are not 
old, they are using the old CLIs which are currently broken with the latest 
server. This also adds coverage for backwards compatibility with the old CLIs, 
which we currently don't have.
   
   ## What is the link to the Apache JIRA
   
   HDDS-16020
   
   ## How was this patch tested?
   
   This change is currently running both the rolling and non-rolling upgrade 
flows to make sure they both work. Once both are green on my fork we can 
comment out the rolling upgrade (currently just a restart) until the first 
release with ZDU support goes out.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to