[nova][kolla][openstack-ansible][tripleo] Cells v2 upgrades
Hi,
At the recent kolla virtual PTG [1] we had a good discussion about adding support for multiple nova cells in kolla-ansible. We agreed a key requirement is to be able to perform operations on one or more cells without affecting the rest for damage limitation. This also seems like it would apply to upgrades. We're seeking input on ordering. Looking at the nova upgrade guide [2] I might propose something like this:
1. DB syncs 2. Upgrade API, super conductor
For each cell: 3a. Upgrade cell conductor 3b. Upgrade cell computes
4. SIGHUP all services 5. Run online migrations
At some point in here we also need to run the upgrade check. Presumably between steps 1 and 2?
It would be great to get feedback both from the nova team and anyone running cells Thanks, Mark
[1] https://etherpad.openstack.org/p/kolla-train-ptg [2] https://docs.openstack.org/nova/latest/user/upgrade.html
On Wed, Jun 5, 2019 at 5:16 AM Mark Goddard mark@stackhpc.com wrote:
Hi,
At the recent kolla virtual PTG [1] we had a good discussion about adding support for multiple nova cells in kolla-ansible. We agreed a key requirement is to be able to perform operations on one or more cells without affecting the rest for damage limitation. This also seems like it would apply to upgrades. We're seeking input on ordering. Looking at the nova upgrade guide [2] I might propose something like this:
- DB syncs
- Upgrade API, super conductor
For each cell: 3a. Upgrade cell conductor 3b. Upgrade cell computes
- SIGHUP all services
Unfortunately, this is a problem right now:
https://review.opendev.org/#/c/641907/
I sat down at the PTG to settle this down, I was going to finish this patch up but I didn't get around to it. That might be an action item to be able to do this successfully.
- Run online migrations
At some point in here we also need to run the upgrade check. Presumably between steps 1 and 2?
It would be great to get feedback both from the nova team and anyone running cells Thanks, Mark
[1] https://etherpad.openstack.org/p/kolla-train-ptg [2] https://docs.openstack.org/nova/latest/user/upgrade.html
On Fri, 7 Jun 2019 at 18:52, Mohammed Naser mnaser@vexxhost.com wrote:
On Wed, Jun 5, 2019 at 5:16 AM Mark Goddard mark@stackhpc.com wrote:
Hi,
At the recent kolla virtual PTG [1] we had a good discussion about adding support for multiple nova cells in kolla-ansible. We agreed a key requirement is to be able to perform operations on one or more cells without affecting the rest for damage limitation. This also seems like it would apply to upgrades. We're seeking input on ordering. Looking at the nova upgrade guide [2] I might propose something like this:
- DB syncs
- Upgrade API, super conductor
For each cell: 3a. Upgrade cell conductor 3b. Upgrade cell computes
- SIGHUP all services
Unfortunately, this is a problem right now:
https://review.opendev.org/#/c/641907/
I sat down at the PTG to settle this down, I was going to finish this patch up but I didn't get around to it. That might be an action item to be able to do this successfully.
Ah, that's true. Thanks for reminding me. s/SIGHUP/restart/,
- Run online migrations
At some point in here we also need to run the upgrade check. Presumably between steps 1 and 2?
It would be great to get feedback both from the nova team and anyone running cells Thanks, Mark
[1] https://etherpad.openstack.org/p/kolla-train-ptg [2] https://docs.openstack.org/nova/latest/user/upgrade.html
-- Mohammed Naser — vexxhost
D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser@vexxhost.com W. http://vexxhost.com
participants (2)
-
Mark Goddard
-
Mohammed Naser