Minor upgrade Overcloud nodes one by one
Issue
-
We are planning to perform next week a RHOSP 13 minor upgrade from RHOSP 13.0.5 to latest.
-
We are planning to perform the below upgrade in regards to our OVS-DPDK COmputes :
- Evacuate VM’s from a specific Compute
- Run update targeted on that compute
- Reboot
- Health Checks
- Migrate VM’s back to that compute.
- Restart procedure for next compute.
- The above procedure is documented in upstrem openstack documentation:
openstack overcloud update run
The update run command utilizes the previously generated Heat stack outputs. It downloads the playbook yamls and their included task list yaml via the config-download mechanisms, and executes the update steps playbook.
The command accepts --nodes or --roles argument to limit which nodes will be targeted during a particular update run execution. Even if the limit matches multiple nodes (e.g. all nodes within one role), the play is executed with serial: 1, meaning that all actions are finished on one node before starting the update on another.
usage: openstack overcloud update run [-h] --nodes NODES [--playbook PLAYBOOK]
[--ssh-user SSH_USER]
[--static-inventory STATIC_INVENTORY]
[--stack STACK]
-
But not on Red Hat openstack documentation , where we have only the posibility of indicating the overcloud role (and not an overcloud specific node).
-
Could you please mention if the targeted node update is supported and maybe you could update the RHOSP documentation to reflect that .
Environment
- Red Hat OpenStack Platform 13.0 (RHOSP)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.