...
- Install the first node; either by resintaling it with the victoria modules/tags, or follow this list:
- Run puppet with victoria modules/tags
- Run
apt-get purge placement-api placement-common python3-placement && apt-get autoremove && apt-get dist-upgrade
- Run puppet again
- Run
placement-manage db sync; placement-manage db
online_data_migrations
on the new node. - upgrade the rest of the nodes, skipping step 2.
Nova
To upgrade nova without any downtime, follow this procedure
Preperations
Before the upgrades can be started it is important that all data from previous nova-releases are migrated to stein's release. This is done like so:
- Run
nova-manage db online_data_migrations
on an API node. Ensure that it reports that nothing more needs to be done.- Make sure there is no errors. Particulary anything related to "virtual interface table". See https://bugs.launchpad.net/nova/+bug/182443
- Make sure that none of the following schedule-filters are used:
- Aggregatefilter
- AggregateRAMFilter
- AggregateDiskFilter
- RetryFilter
Nova API
- In the node-specific hiera, disable the services at the first node you would like to upgrade with the keys
apache::service_ensure: 'stopped'
- Do one of:
- Run puppet with the victoria modules/tags, Run
apt dist-upgrade && apt-get autoremove
- Reinstall the node with victoria modules/tags
- Run puppet with the victoria modules/tags, Run
- Run
nova-manage api_db sync
- Run
nova-manage db sync
- Re-enable placement API on the upgraded node:
- Remove
apache::service_ensure: 'stopped'
from the upgraded node's hiera file
- Remove
- Upgrade the rest of the nodes (basically run step 2)
Nova-services
- Run puppet with the ussuri modules/tags
- Run
apt dist-upgrade &&
apt-get autoremove
- Run puppet and restart services