openstack/openstack-manuals
Code Issues Proposed changes

Minor edit on volumes migration section

Browse Source 
Apply conventions

Use a <note> section instead of a 'Note:' description in a paragraph.

Change-Id: Iabf665b61676186c9ac20521c672c7f55559957c
This commit is contained in:
Gauvain Pocentek 2014-02-20 21:16:50 +01:00
parent cdcb564c19
commit 3e6b91939d
1 changed files with 15 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
doc/admin-guide-cloud/section_volume-migration.xml
View File

@ -25,13 +25,15 @@
<listitem> <listitem>
<para>If the volume is not attached, the Block Storage <para>If the volume is not attached, the Block Storage
Service creates a volume and copies the data from the Service creates a volume and copies the data from the
original to the new volume. Note: While most original to the new volume.</para>
back-ends support this function, not all do. See <note>
driver documentation in the <link <para>While most back-ends support this function, not all do.
xlink:href="http://docs.openstack.org/havana/config-reference/content/" See the driver documentation in the <link
xlink:href="http://docs.openstack.org/havana/config-reference/content/"
><citetitle>OpenStack Configuration ><citetitle>OpenStack Configuration
Reference</citetitle></link> for more Reference</citetitle></link> for more
details.</para> details.</para>
</note>
</listitem> </listitem>
<listitem> <listitem>
<para>If the volume is attached to a VM instance, the <para>If the volume is attached to a VM instance, the
@ -45,7 +47,7 @@
migrates an attached volume from one to the other. This migrates an attached volume from one to the other. This
scenario uses the third migration flow.</para> scenario uses the third migration flow.</para>
<para>First, list the available back-ends:</para> <para>First, list the available back-ends:</para>
<screen><prompt>$</prompt> <userinput>cinder-manage host list</userinput> <screen><prompt>#</prompt> <userinput>cinder-manage host list</userinput>
<computeroutput>server1@lvmstorage-1 zone1 <computeroutput>server1@lvmstorage-1 zone1
server2@lvmstorage-2 zone1</computeroutput></screen> server2@lvmstorage-2 zone1</computeroutput></screen>
<para>Next, as the admin user, you can see the current status of <para>Next, as the admin user, you can see the current status of
@ -80,19 +82,19 @@ server2@lvmstorage-2 zone1</computeroutput></screen>
</listitem> </listitem>
<listitem> <listitem>
<para><literal>os-vol-mig-status-attr:migstat</literal> - <para><literal>os-vol-mig-status-attr:migstat</literal> -
the status of this volume's migration ('None' means the status of this volume's migration (<literal>None</literal>
that a migration is not currently in progress).</para> means that a migration is not currently in progress).</para>
</listitem> </listitem>
<listitem> <listitem>
<para><literal>os-vol-mig-status-attr:name_id</literal> - <para><literal>os-vol-mig-status-attr:name_id</literal> -
the volume ID that this volume's name on the back-end the volume ID that this volume's name on the back-end
is based on. Before a volume is ever migrated, its is based on. Before a volume is ever migrated, its
name on the back-end storage may be based on the name on the back-end storage may be based on the
volume's ID (see the volume_name_template volume's ID (see the <option>volume_name_template</option>
configuration parameter). For example, if configuration parameter). For example, if
volume_name_template is kept as the default value <option>volume_name_template</option> is kept as the default
(volume-%s), your first LVM back-end has a logical value (<literal>volume-%s</literal>), your first LVM back-end
volume named has a logical volume named
<literal>volume-6088f80a-f116-4331-ad48-9afb0dfb196c</literal>. <literal>volume-6088f80a-f116-4331-ad48-9afb0dfb196c</literal>.
During the course of a migration, if you create a During the course of a migration, if you create a
volume and copy over the data, the volume get the new name but keeps its volume and copy over the data, the volume get the new name but keeps its