From 46465d5df5f798e83427f06315b1d24371a25586 Mon Sep 17 00:00:00 2001 From: lisali Date: Thu, 28 May 2015 01:02:48 +0800 Subject: [PATCH] Update description about back-ends in volume migration. Change-Id: I02104cfda88269cbdd2fe3c82d837c8ae588ea0b Closes-Bug: #1436031 --- .../blockstorage/section_volume-migration.xml | 25 ++++++++++++++++--- 1 file changed, 21 insertions(+), 4 deletions(-) diff --git a/doc/admin-guide-cloud/blockstorage/section_volume-migration.xml b/doc/admin-guide-cloud/blockstorage/section_volume-migration.xml index e3aae28eca..b46e0f31ee 100644 --- a/doc/admin-guide-cloud/blockstorage/section_volume-migration.xml +++ b/doc/admin-guide-cloud/blockstorage/section_volume-migration.xml @@ -5,8 +5,8 @@ version="5.0" xml:id="volume-migration"> Migrate volumes - OpenStack has the ability to - migrate volumes between back-ends. Migrating a volume + OpenStack has the ability to migrate volumes between + back-ends which support its volume-type. Migrating a volume transparently moves its data from the current back-end for the volume to a new one. This is an administrator function, and can be used for functions including storage evacuation (for @@ -47,9 +47,26 @@ migrates an attached volume from one to the other. This scenario uses the third migration flow. First, list the available back-ends: + # cinder get-pools ++----------+----------------------------------------------------+ +| Property | Value | ++----------+----------------------------------------------------+ +| name | server1@lvmstorage-1#lvmstorage-1 | ++----------+----------------------------------------------------+ ++----------+----------------------------------------------------+ +| Property | Value | ++----------+----------------------------------------------------+ +| name | server2@lvmstorage-2#lvmstorage-2 | ++----------+----------------------------------------------------+ + + + Only Block Storage V2 API supports get-pools. + + You can also get available back-ends like following: # cinder-manage host list server1@lvmstorage-1 zone1 server2@lvmstorage-2 zone1 + But it needs to add pool name in the end. For example, server1@lvmstorage-1#zone1. Next, as the admin user, you can see the current status of the volume (replace the example ID with your own): $ cinder show 6088f80a-f116-4331-ad48-9afb0dfb196c @@ -64,7 +81,7 @@ server2@lvmstorage-2 zone1 | display_name | test | | id | 6088f80a-f116-4331-ad48-9afb0dfb196c | | metadata | {} | -| os-vol-host-attr:host | server1@lvmstorage-1 | +| os-vol-host-attr:host | server1@lvmstorage-1#lvmstorage-1 | | os-vol-mig-status-attr:migstat | None | | os-vol-mig-status-attr:name_id | None | | os-vol-tenant-attr:tenant_id | 6bdd8f41203e4149b5d559769307365e | @@ -141,7 +158,7 @@ server2@lvmstorage-2 zone1 | display_name | test | | id | 6088f80a-f116-4331-ad48-9afb0dfb196c | | metadata | {} | -| os-vol-host-attr:host | server2@lvmstorage-2 | +| os-vol-host-attr:host | server2@lvmstorage-2#lvmstorage-2 | | os-vol-mig-status-attr:migstat | None | | os-vol-mig-status-attr:name_id | 133d1f56-9ffc-4f57-8798-d5217d851862 | | os-vol-tenant-attr:tenant_id | 6bdd8f41203e4149b5d559769307365e |