...

1. Run puppet with the ussuri modules/tags
2. Run apt dist-upgrade && apt-get autoremove
3. Run puppet and restart services

Heat

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

Step 4 is only for the API-nodes, so the routine should be run on the API-nodes first

1. Set heat::api::enabled: false and heat::engine::enabled: false and heat::api_cfn::enabled: false in hiera to stop all services
2. Run puppet with ussuri modules/tags
3. Run apt-get update && apt-get dist-upgrade && apt-get autoremove

4. Run heat-manage db_sync on one of the api-nodes.

5. Remove the hiera keys that disabled the services and re-run puppet

Barbican

Barbican must be stopped for upgrades, and can thus be performed on all barbican hosts at the same time. It might be an idea to keep one set of hosts stopped at old code in case of the need for a sudden roll-back.

1. Stop all barbican-services by adding the following keys to node-specific hiera, and then make sure to run puppet on the barbican hosts:

   1. barbican::worker::enabled: false

   2. apache::service_ensure: 'stopped'

2. Run puppet with the ussuri modules/tags

3. Run apt dist-upgrade && apt-get autoremove

4. Run barbican-db-manage upgrade

5. Re-start barbican services by removing the keys added in step 1 and re-run puppet.

Magnum

Magnum must be stopped for upgrades, and can thus be performed on all magnum-hosts at the same time. It might be an idea to keep one set of hosts stopped at old code in case of the need for a sudden roll-back.

1. Stop all magnum-services by adding the following keys to node-specific hiera, and then make sure to run puppet on the magnum hosts:

   1. magnum::conductor::enabled: false

   2. apache::service_ensure: 'stopped'

2. Run puppet with the ussuri modules/tags

3. Run yum upgrade

4. Run su -s /bin/sh -c "magnum-db-manage upgrade" magnum

5. Re-start magnum services by removing the keys added in step 1 and re-run puppet.

Octavia

Octavia must be stopped for upgrades, and can thus be performed on all octavia-hosts at the same time. It might be an idea to keep one set of hosts stopped at old code in case of the need for a sudden roll-back.

1. Stop all magnum-services by adding the following keys to node-specific hiera, and then make sure to run puppet on the magnum hosts:

   1. octavia::housekeeping::enabled: false

   2. octavia::health_manager::enabled: false

   3. octavia::api::enabled: false

   4. octavia::worker::enabled: false

2. Run puppet with the ussuri modules/tags

3. Run apt-get dist-upgrade && apt-get autoremove

4. Run puppet

5. Run octavia-db-manage upgrade head


6. Re-start octavia services by removing the keys added in step 1 and re-run puppet.

7. Build a train-based octavia-image and upload to glance. Tag it and make octavia start to replace the amphora.

Horizon

1. Run puppet with the ussuri modules/tags
2. run yum upgrade

3. Run puppet again
4. restart httpd

Compute-nodes

When all APIs etc. are upgraded, it is time to do the same on the compute-nodes. Compute nodes are simple to upgrade:

1. Run puppet with the ussuri modules/tags
2. Run apt-get purge python-cinderclient && apt dist-upgrade && apt-get autoremove
3. Run puppet again
4. Restart openstack services and openvswitch-services
   1. No downtime: systemctl restart nova-compute.service neutron-openvswitch-agent.service
   2. At a later point: reboot

GPU-nodes

1. Run puppet with the ussuri modules/tags
2. Run yum upgrade && yum autoremove
3. Run puppet again
4. Restart openstack services and openvswitch-services

Finalizing

• Run nova-manage db online_data_migrations on a nova API node. Ensure that it reports that nothing more needs to be done.