...
- This documents expects that your cloud is deployed with the latest newton tag(vP.0.0) of the ntnuopenstack repository.
- Your cloud is designed with one of the two architectures:
- 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: 'pike'
VM-based architecture
If you use the VM based infrastructure you have the luxury of upgrading one service at a time and test that the upgrade works before doing the next service. This allows for ~zero downtime. If the services are redundantly deployed it is also very easy to do a rollback.
...
- Run puppet with the queens modules/tags
- Run apt-get dist-upgrade
- restart neutron services
Nova
On the API node:
- Run puppet with the pike modules/tags
- Run apt-get dist-upgrade
- Migrate the databases
nova-manage api_db sync
nova-manage db sync
- Restart services
On the services node:
- Run puppet with the pike modules/tags
- Run apt-get dist-upgrade
- Restart services
Heat
On the API node:
- Run puppet with the pike modules/tags
- Run apt-get dist-upgrade
- heat-manage db_sync
- restart heat services
On the engine node:
- Run puppet with the pike modules/tags
- Run apt-get dist-upgrade
- Restart heat-engine