...

• Run nova-manage db online_data_migrations on an API node. Ensure that it reports that nothing more needs to be done.
• Add nova db-settings to hiera:
  • nova::db::api_database_connection: "mysql+pymysql://nova_api:%{lookup('ntnuopenstack::nova::mysql::password')}@%{lookup('ntnuopenstack::nova::mysql::ip')}/nova_api"
  • nova::db::database_connection: "mysql+pymysql://nova:%{lookup('ntnuopenstack::nova::mysql::password')}@%{lookup('ntnuopenstack::nova::mysql::ip')}/nova"

Nova API

1. In the node-specific hiera, disable the services at the first node you would like to upgrade with the keys

   1. apache::service_ensure: 'stopped'

2. Do one of:
   1. Run puppet with the wallaby modules/tags, Run apt dist-upgrade && apt-get autoremove
   2. Reinstall the node with wallaby modules/tags
3. Run nova-manage api_db sync
4. Run nova-manage db sync
5. Re-enable placement API on the upgraded node:
   
   1. Remove apache::service_ensure: 'stopped' from the upgraded node's hiera file
6. Upgrade the rest of the nodes (basically run step 2)

...

1. Set heat::api::enabled: false and heat::engine::enabled: false and heat::api_cfn::enabled: false in hiera to stop all services
2. Do one of:
   1. Run puppet with wallaby modules/tags, Run apt-get update && apt-get dist-upgrade && apt-get autoremove
   2. Reinstall the nodes with wallaby modules/tags
3. Run heat-manage db_sync on one of the api-nodes.

4. 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 wallaby 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.

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 octavia-services by adding the following keys to hiera, and then make sure to run puppet on the octavia hosts:

   1. octavia::housekeeping::enabled: false

   2. octavia::health_manager::enabled: false

   3. octavia::api::enabled: false

   4. octavia::worker::enabled: false

2. Do one of:

   1. Reinstall the node with wallaby modules/tags

   2. Run puppet with the wallaby modules/tags, Run apt-get dist-upgrade && apt-get autoremove, Run puppet

3. Run octavia-db-manage upgrade head


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

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

Horizon

1. Run puppet with the wallaby modules/tags
2. run dnf upgrade

3. Yes this is weird: Login to all memcached servers, and run systemctl restart memcached
   1. This is only necessary when upgrading the first horizon server
4. Run puppet again
5. restart httpd