Page History

...

1. Set glance::sync_db: false in a global hiera-file
2. Select which glance-server to upgrade first.
   1. In the node-specific hiera for this host you should set: glance::api::enable: false followed by a puppet-run. This would stop the glance-api service on the host.
3. Run puppet on the first host with the rocky modules/tags
4. Run apt dist-upgrade
5. Run glance-manage db expand
6. Run glance-manage db migrate
7. Remove the glance::api::enable: false from the node-specific hiera, and run puppet again. This would re-start the glance api-server on this host.
   1. Test that this api-server works.
8. Upgrade the rest of the glance hosts (ie; step 3 + 4 for each of the remaining glance hosts)
9. Run glance-manage dbcontract
10. Remove glance::sync_db: false in a global hiera-file

Heat

The rolling upgrade procedure for heat includes a step where you are supposed to create a new rabbot vhost. I don't want that. Therefore, this is the cold upgrade steps

1. Set heat::api::enabled: false and heat::engine::enabled: false and heat::api_cfn: false in hiera to stop all services
2. Run puppet with rocky modules/tags
3. Run apt-dist-upgrade
4. Run heat-manage db_sync
5. Remove the hiera keys that disabled the services and re-run puppet