Page History

...

• This documents expects that your cloud is deployed with a recent ussuri tag of the ntnuopenstack repository.
• 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: 'trainussuri'

  • When the upgrade is finished - set this key to 'ussurivictoria'

The recommended order to upgrade the services are listed below:

...

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

...

1. Pick the first node, and do one of the following:
   1. run puppet with the victoria modules/tags, Run apt-get autoremove && apt-get dist-upgrade
   2. Reinstall the node with victoria modules/tags.
2. Run neutron-db-manage upgrade --expandRun neutron-db-manage --subproject neutron-fwaas upgrade head
3. Restart neutron-server.service and rerun puppet
4. Upgrade the rest of the API-nodes (repeating step 1, and 43)
5. Stop all neutron-server processes for a moment, and run:
   
   1. neutron-db-manage upgrade --contract
6. Re-start the neutron-server processes

...

• Run nova-manage db online_data_migrations on a nova API node. Ensure that it reports that nothing more needs to be done.
• Rotate octavia images.