...

1. Select which glance-server to upgrade first.
   1. In the node-specific hiera for this host you should set: glance::api::enabled: false followed by a puppet-run. This would stop the glance-api service on the host.
2. Do one of these two alternatives:
   1. Run puppet with the victoria modules/tags, run apt-get dist-upgrade, and run puppet again
   2. Reinstall the node with the victoria modules/tags
3. Run glance-manage db expand
4. Run glance-manage db migrate
5. 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.
6. Upgrade the rest of the glance hosts (ie; step 2 for each of the remaining glance hosts)
7. Run glance-manage db contract on one of the glance-nodes.

Cinder

To upgrade cinder without any downtime, follow this procedure

1. Add the following three lines to the node-file of the first node you would like to upgrade:
   

   1. apache::service_ensure: 'stopped'

   2. cinder::scheduler::enabled: false

   3. cinder::volume::enabled: false

2. Do one of these two alternatives:
   1. Run puppet with the victoria modules/tags, run apt-get dist-upgrade, and run puppet again
   2. Reinstall the node with the victoria modules/tags
3. Run cinder-manage db sync && cinder-manage db online_data_migrations
4. Remove the lines added at step 1, re-run puppet, and test that the upgraded cinder version works.
5. Perfom step 2-5 for the rest of the cinder nodes