small edit to section_compute-configure-migrations

mount to plural - mounts it
changed , to .
added be before migrated
Split into separate sentences for clarity

Change-Id: Ic8f1ea2c0ae99a9a5ce007ce42db7ed48a37ea76
This commit is contained in:
shilla-saebi 2014-05-20 22:35:57 -04:00
parent 8543c8789a
commit 4286a69582

View File

@ -127,9 +127,9 @@
<listitem> <listitem>
<para>In this example, <literal>HostA</literal> is the NFSv4 <para>In this example, <literal>HostA</literal> is the NFSv4
server that exports server that exports
<filename><replaceable>NOVA-INST-DIR</replaceable>/instances</filename>, <filename><replaceable>NOVA-INST-DIR</replaceable>/instances</filename> directory.
and <literal>HostB</literal> and <literal>HostC</literal> <literal>HostB</literal> and <literal>HostC</literal>
mount it.</para> are NFSv4 clients that mount it.</para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
<procedure> <procedure>
@ -205,7 +205,7 @@ none 16502856 0 16502856 0% /lib/init/rw
HostA: 921515008 101921792 772783104 12% /var/lib/nova/instances ( &lt;--- this line is important.)</computeroutput></screen> HostA: 921515008 101921792 772783104 12% /var/lib/nova/instances ( &lt;--- this line is important.)</computeroutput></screen>
</step> </step>
<step> <step>
<para>Update the libvirt configurations so that the calls can be made securely. These methods enable remote access over TCP and are not documented here, please consult your network administrator for assistance in deciding how to configure access.</para> <para>Update the libvirt configurations so that the calls can be made securely. These methods enable remote access over TCP and are not documented here. Please consult your network administrator for assistance in deciding how to configure access.</para>
<para> <para>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
@ -251,7 +251,7 @@ HostA: 921515008 101921792 772783104 12% /var/lib/nova/instances ( &lt;
<para>The Compute service does not use libvirt's live migration <para>The Compute service does not use libvirt's live migration
by default because there is a risk that the migration process by default because there is a risk that the migration process
never ends. This can happen if the guest operating system never ends. This can happen if the guest operating system
dirties blocks on the disk faster than they can dirties blocks on the disk faster than they can be
migrated.</para> migrated.</para>
</section> </section>
</section> </section>