openstack/cinder
Code Issues Proposed changes

Fix minor typos in the migration devref

Browse Source 
Noticed a few trivial typos while looking through the migration
devref that could be fixed up. Some larger rewording might help
clarify some things, but this just fixes some specific instances.

Change-Id: I24c59f8b1725c8c5c93101983e7a3c4dc2a91065
This commit is contained in:
Sean McGinnis
2016-04-17 16:38:15 -05:00
parent 2596004a54
commit 8b24dc676e
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/devref/migration.rst
View File

@@ -105,7 +105,7 @@ they must refer to different back-ends.
Configurations Configurations
-------------- --------------
To set up a an environment to try the volume migration, we need to To set up an environment to try the volume migration, we need to
configure at least two different back-ends on the same node of cinder configure at least two different back-ends on the same node of cinder
volume service, c-vol node or two back-ends on two different volume volume service, c-vol node or two back-ends on two different volume
nodes of cinder volume service, c-vol nodes. Which command to use, nodes of cinder volume service, c-vol nodes. Which command to use,
@@ -135,9 +135,9 @@ For Node 2:
... ...
If a volume with a predefined volume type is going to migrate, If a volume with a predefined volume type is going to migrate,
the back-end drivers from Node 1 and Node2 should have the same the back-end drivers from Node 1 and Node 2 should have the same
value for volume_backend_name, which means <driver-backend> should be value for volume_backend_name, which means <driver-backend> should be
the same for Noe 1 and Node 2. The volume type can be created the same for Node 1 and Node 2. The volume type can be created
with the extra specs {volume_backend_name: driver-biz}. with the extra specs {volume_backend_name: driver-biz}.
If we are going to migrate a volume with a volume type of none, it If we are going to migrate a volume with a volume type of none, it
@@ -181,7 +181,7 @@ contains the following entries:
volume_backend_name=driver-net volume_backend_name=driver-net
... ...
Two volume type needs to be created. One is with the extra specs: Two volume types need to be created. One is with the extra specs:
{volume_backend_name: driver-biz}. The other is with the extra specs: {volume_backend_name: driver-biz}. The other is with the extra specs:
{volume_backend_name: driver-net}. {volume_backend_name: driver-net}.