diff --git a/doc/admin-guide-cloud/section_volume-migration.xml b/doc/admin-guide-cloud/section_volume-migration.xml index d2ae99bb2d..85bfb3254b 100644 --- a/doc/admin-guide-cloud/section_volume-migration.xml +++ b/doc/admin-guide-cloud/section_volume-migration.xml @@ -103,6 +103,22 @@ server2@lvmstorage-2 zone1 attribute. + + If you plan to decommission a block storage node, you must + stop the cinder volume + service on the node after performing the migration. + On nodes that run + CentOS, Fedora, openSUSE, RedHat Enterprise Linux, or SUSE Linux + Enterprise, run: + # service openstack-cinder-volume stop +# chkconfig openstack-cinder-volume off + On nodes that run Ubuntu or Debian, run: + + # service cinder-volume stop +# chkconfig cinder-volume off + Stopping the cinder volume service + will prevent volumes from being allocated to the node. + Migrate this volume to the second LVM back-end: $ cinder migrate 6088f80a-f116-4331-ad48-9afb0dfb196c server2@lvmstorage-2 You can use the cinder show command to @@ -140,7 +156,7 @@ server2@lvmstorage-2 zone1 host is the new host, and name_id holds the ID of the volume created by the migration. If you look at the second LVM - back-end, you find the logical volume + back end, you find the logical volume volume-133d1f56-9ffc-4f57-8798-d5217d851862. The migration is not visible to non-admin users (for