This documents expects that your cloud is deployed with the latest stein tag(at LEAST vS.6.2) of the ntnuopenstack repository.
Your cloud is designed with our common openstack architecture where each openstack project have their own VM(s) for their services
You have a recent mysql backup in case things go south.
If you want to do a rolling upgrade, the following key should be set in hiera long enough in advance that all hosts have had an puppet-run to apply it:
- nova::upgrade_level_compute: 'auto'stein'
- When the upgrade is finished - set this key to 'train'
- NOTE: There is a bug, which will cause live migrations (and possibly other things?) to break in train if this is set to auto..

The recommended order to upgrade the services are listed below:

...

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:

Run puppet with the train modules/tags
Run apt-get purge python-cinderclient && apt dist-upgrade && apt-get autoremove
Run puppet again
Restart openstack services and openvswitch-services

GPU-nodes

...