Merge "Added instance evacuation using compute API to the server recovery section."

This commit is contained in:
Jenkins 2013-04-23 15:57:26 +00:00 committed by Gerrit Code Review
commit 05949245ee
1 changed files with 10 additions and 4 deletions

View File

@ -404,7 +404,7 @@ HostC p2 5 10240 150
]]></programlisting>
<itemizedlist>
<listitem>
<para><emphasis role="bold">cpu:</emphasis>the nuber of cpu</para>
<para><emphasis role="bold">cpu:</emphasis>the number of cpu</para>
</listitem>
<listitem>
<para><emphasis role="bold">mem(mb):</emphasis>total amount of memory (MB)</para>
@ -442,13 +442,18 @@ HostC p2 5 10240 150
section for more details.</para></note></para>
</listitem>
</itemizedlist>
</section>
<section xml:id="nova-compute-node-down">
<title>Recovering from a failed compute node</title>
<para>If you have deployed OpenStack Compute with a shared filesystem,
you can quickly recover from a failed compute node. </para>
<section xml:id="nova-compute-node-down-evacuate-api">
<title>Using the evacuate API for KVM/libvirt</title>
<para>Refer to <link linkend="nova_cli_evacuate">Evacuate API Reference</link> section for more details.</para>
</section>
<section xml:id="nova-compute-node-down-manual-recovery">
<title>Manual recovery</title>
<para>For KVM/libvirt compute node recovery refer to section above, while the guide below may be applicable for other hypervisors.</para>
<simplesect>
<title>Working with host information</title>
<para>
@ -515,7 +520,8 @@ network filter configuration using <literal>virsh</literal>, restarting the
nova services or updating the <literal>vm_state</literal> and
<literal>power_state</literal> in the nova database.</para>
</simplesect>
</section>
</section>
</section>
<section xml:id="nova-uid-mismatch">
<title>Recovering from a UID/GID mismatch</title>
<para>When running OpenStack compute, using a shared filesystem or