Page History

...

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. Run puppet with the wallaby modules/tags, run apt-get dist-upgrade, and run puppet again
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 for the rest of the cinder nodes
6. Delete cinderv2-resources from keystone

   1. openstack endpoint delete $(openstack endpoint list --service cinder -f value -c ID)openstack endpoint delete $(openstack endpoint list --service cinderv2 -f value -c ID)

   2. openstack service list, and delete the services cinder and cinderv2

...

1. Pick the first node, and run puppet with the wallaby modules/tags, Run apt apt-get autoremove && apt-get dist-upgrade && apt-get autoremove

2. Run neutron-db-manage upgrade --expand
3. Restart neutron-server.service and rerun puppet
4. Upgrade the rest of the API-nodes (repeating step 1, and 3)
5. Stop all neutron-server processes for a moment, and run:
   
   1. neutron-db-manage upgrade --contract
6. Re-start the neutron-server processes

...

1. Stop all barbican-services by adding the following keys to node-specific hiera, and then make sure to run puppet on the barbican hosts:

   1. barbican::worker::enabled: false

   2. apache::service_ensure: 'stopped'

2. Run puppet with the wallaby modules/tags

3. Run apt dist-upgrade && apt-get autoremove

4. Run barbican-db-manage upgrade

5. Remove barbican::api::max_allowed_secret_in_bytes: 20000 and barbican::api::max_allowed_request_size_in_bytes: 25000 from hiera. The defaults in W is OK, and this is no longer needed.

6. Re-start barbican services by removing the keys added in step 1 and re-run puppet.

...

1. Run puppet with the wallaby modules/tags
2. Run yum Run apt dist-upgrade && yum apt autoremove
3. Run puppet again
4. Restart openstack services and openvswitch-services

...