openstack/openstack-manuals
Code Issues Proposed changes

Add evacuate instances to Cloud Admin Guide

Browse Source 
Clarify that evacuate method is preferred over manual for node recovery
Edit broken and obsolete external guide references
Remove gerunds in related files
Address request for stylistic edits from review
Address linking issues from review

Change-Id: Iccf188ad89a8cc277966cb9c0a530ba24613127b
Closes-Bug:#1222735
This commit is contained in:
nerminamiller 2013-10-03 11:36:12 -04:00
parent d82a85d081
commit ce4f54732f
3 changed files with 21 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
doc/admin-guide-cloud/ch_compute.xml
View File

@ -2010,9 +2010,8 @@ local0.error @@172.20.1.43:1024</programlisting></para>
<section xml:id="section_live-migration-usage"> <section xml:id="section_live-migration-usage">
<title>Migration</title> <title>Migration</title>
<para>Before starting migrations, review the <link xlink:href="http://docs.openstack.org/trunk/config-reference/content/configuring-openstack-compute-basics.html#section_configuring-compute-migrations" <para>Before starting migrations, review the <link xlink:href="http://docs.openstack.org/trunk/config-reference/content/configuring-openstack-compute-basics.html#section_configuring-compute-migrations">Configure migrations</link> section in <citetitle>OpenStack Configuration
>Configuring Migrations</link> section in the Reference</citetitle>.</para>
<citetitle>Configuration Reference Guide</citetitle>.</para>
<para>Migration provides a scheme to migrate running <para>Migration provides a scheme to migrate running
instances from one OpenStack Compute server to another instances from one OpenStack Compute server to another
OpenStack Compute server.</para> OpenStack Compute server.</para>
@ -2082,10 +2081,8 @@ HostC p2 5 10240 150
memory (MB)</para> memory (MB)</para>
</listitem> </listitem>
<listitem> <listitem>
<para><emphasis role="bold" <para><emphasis role="bold">hdd:</emphasis>total amount of space for
>hdd:</emphasis>total amount of NOVA-INST-DIR/instances (GB)</para>
space for
NOVA-INST-DIR/instances(GB)</para>
</listitem> </listitem>
<listitem> <listitem>
<para><emphasis role="bold">1st line shows <para><emphasis role="bold">1st line shows
@ -2127,23 +2124,25 @@ HostC p2 5 10240 150
<command>live-migration</command>, <command>live-migration</command>,
under the default Compute under the default Compute
configuration options the instances configuration options the instances
are suspended before migration.</para> are suspended before migration.</para>
</note><!--<para>See <para>See <link xlink:href="http://docs.openstack.org/trunk/config-reference/content/configuring-openstack-compute-basics.html#section_configuring-compute-migrations">Configure migrations</link> in <citetitle>OpenStack Configuration Reference</citetitle> for more details.</para>
the <link linkend="configuring-migrations">Configuring Migrations</link> </note>
section for more details.</para>--></para> </para>
</step> </step>
</procedure> </procedure>
</section> </section>
<section xml:id="section_nova-compute-node-down"> <section xml:id="section_nova-compute-node-down">
<title>Recover from a failed compute node</title> <title>Recover from a failed compute node</title>
<para>If you have deployed OpenStack Compute with a shared <para>If you have deployed Compute with a shared file system, you can quickly recover
file system, you can quickly recover from a failed from a failed compute node. Of the two methods covered in the following sections,
compute node.</para> the evacuate API is the preferred method even in the absence of shared storage. The
evacuate API provides many benefits over manual recovery, such as re-attachment of
volumes and floating IPs. </para>
<xi:include href="../common/section_nova_cli_evacuate.xml"/>
<section xml:id="nova-compute-node-down-manual-recovery"> <section xml:id="nova-compute-node-down-manual-recovery">
<title>Manual recovery</title> <title>Manual recovery</title>
<para>For KVM/libvirt compute node recovery refer to <para>For KVM/libvirt compute node recovery, see the previous section. Use the
section above, while the guide below may be following procedure for other hypervisors.</para>
applicable for other hypervisors.</para>
<procedure> <procedure>
<title>To work with host information</title> <title>To work with host information</title>
<step> <step>

4
doc/common/section_nova_cli_evacuate.xml
View File

@ -41,9 +41,7 @@
<step> <step>
<para>To preserve the user disk data on the evacuated <para>To preserve the user disk data on the evacuated
server, deploy OpenStack Compute with shared server, deploy OpenStack Compute with shared
filesystem. To configure your system, see <link filesystem. To configure your system, see <link xlink:href="http://docs.openstack.org/trunk/config-reference/content/configuring-openstack-compute-basics.html#section_configuring-compute-migrations">Configure migrations</link> in <citetitle>OpenStack Configuration Reference</citetitle>. In this
xlink:href="http://docs.openstack.org/trunk/config-reference/content/configuring-openstack-compute-basics.html#section_configuring-compute-migrations"
>Configure migrations section</link>. In this
example, the password remains unchanged.</para> example, the password remains unchanged.</para>
<screen><prompt>$</prompt> <userinput>nova evacuate <replaceable>evacuated_server_name</replaceable> <replaceable>host_b</replaceable> --on-shared-storage</userinput> </screen> <screen><prompt>$</prompt> <userinput>nova evacuate <replaceable>evacuated_server_name</replaceable> <replaceable>host_b</replaceable> --on-shared-storage</userinput> </screen>
</step> </step>

9
doc/config-reference/compute/section_compute-configure-migrations.xml
View File

@ -8,7 +8,7 @@
xmlns:ns="http://docbook.org/ns/docbook" xmlns:ns="http://docbook.org/ns/docbook"
version="5.0"> version="5.0">
<?dbhtml stop-chunking?> <?dbhtml stop-chunking?>
<title>Configuring Migrations</title> <title>Configure migrations</title>
<note> <note>
<para>This feature is for cloud administrators only. If your cloud is configured to use cells, <para>This feature is for cloud administrators only. If your cloud is configured to use cells,
you can perform live migration within a cell, but not between cells.</para> you can perform live migration within a cell, but not between cells.</para>
@ -67,10 +67,9 @@
</listitem> </listitem>
</itemizedlist> </itemizedlist>
<note> <note>
<para>Migrations done by the Compute service do not use libvirt's live migration <para>Because the Compute service does not use libvirt's live migration functionality by
functionality by default. Because of this, guests are suspended before migration and may default, guests are suspended before migration and may therefore experience several
therefore experience several minutes of downtime. See the section on True Migration for minutes of downtime. See the <xref linkend="true-live-migration-kvm-libvirt"/> section for more details.</para>
KVM and Libvirt in the OpenStack Compute Administration Guide for more details.</para>
</note> </note>
<note> <note>
<para>This guide assumes the default value for <literal>instances_path</literal> in your <para>This guide assumes the default value for <literal>instances_path</literal> in your