Description of problem: For fast forward upgrades, we have some very specific needs for telcos. Specially, it is very important to consider the maintenance window. We have a limit of 4 hours per window. In this window we need to do several tasks: - take backup - start the upgrade task - test - rollback if something went wrong This needs to be considered for all the parts of the process. Specifically, we have an important need in terms of upgrading the computes. Computes need to be upgraded in batch, and also we need the ability to control the order of the upgrades and reboots.
More requirements: - data plane needs to be 100% up - add the ability to control the order of reboots in the minor update step - add the ability to provide hooks, after minor updates, to be able to deal with ovs version upgrade problems
Hey Maria, I'm assigning this to you for further discussion.
*** This bug has been marked as a duplicate of bug 1485418 ***
Hi Anjali AFAIK, this BZ is on Dev, why is it on QA?
Verified FFU was manually done from 10z10 (puddle ID - 2019-01-03.2) to 13z5 (puddle ID - 2019-02-15.1) Constraints were that default roles for compute were used.