This article summarizes the steps required to upgrade from the newton pike release to the queens release of openstack.
...
- This documents expects that your cloud is deployed with the latest newton pike 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'
...
- Run puppet with the queens modules/tags
- Purge the keystone package
- Run apt-get dist-upgrade (Which will fail)
- Purge the keystone package
- Run puppet again
- Perform the DB sync
- keystone-manage db_sync
- Restart apache2
...
When controllers etc. are upgraded, it is time to do the same on the comute-nodes. Compute nodes are simple to upgrade:
- Stop nova-compute (systemctl stop nova-compute)
- The queens r10k env will update the home directory of the nova user. This can not be done while nova-compute is running
- Run puppet with the pike modules/tags
- Perform a dist-upgrade
- Run puppet again
- Restart openstack services