278f3d826b
Add dedicated OpenStack upgrade migration path pages to make it clearer for upgraders. Doing so also removes non-relevant text from the general upgrade-issues page. Add a redirect to account for the deleted placement charm special procedure page. Closes-Bug: #1970272 Change-Id: Ibd09e9e0d66a6f9e152f37c6ac675eed35c97bde
1.9 KiB
- orphan
Upgrade: Newton to Ocata
This page contains notes specific to the Newton to Ocata upgrade
path. See the main upgrade-openstack page for full coverage.
cinder/ceph topology change
If cinder is directly related to ceph-mon rather than via cinder-ceph then upgrading from Newton to Ocata will result in the loss of some block storage functionality, specifically live migration and snapshotting. To remedy this situation the deployment should migrate to using the cinder-ceph charm. This can be done after the upgrade to Ocata.
Warning
Do not attempt to migrate a deployment with existing volumes to use the cinder-ceph charm prior to Ocata.
The intervention is detailed in the below three steps.
Step 0: Check existing configuration
Confirm existing volumes are in an RBD pool called 'cinder':
juju run --unit cinder/0 "rbd --name client.cinder -p cinder ls"Sample output:
volume-b45066d3-931d-406e-a43e-ad4eca12cf34
volume-dd733b26-2c56-4355-a8fc-347a964d5d55Step 1: Deploy new topology
Deploy the cinder-ceph charm and set the 'rbd-pool-name'
to match the pool that any existing volumes are in (see above):
juju deploy --config rbd-pool-name=cinder cinder-ceph
juju add-relation cinder cinder-ceph
juju add-relation cinder-ceph ceph-mon
juju remove-relation cinder ceph-mon
juju add-relation cinder-ceph nova-computeStep 2: Update volume configuration
The existing volumes now need to be updated to associate them with the newly defined cinder-ceph backend:
juju run-action cinder/0 rename-volume-host currenthost='cinder' \
newhost='cinder@cinder-ceph#cinder.volume.drivers.rbd.RBDDriver'