Merge "change to section_compute-configure-xen"

This commit is contained in:
Jenkins 2014-06-03 23:47:51 +00:00 committed by Gerrit Code Review
commit 9c5161336d

View File

@ -24,7 +24,7 @@ xenapi_connection_password = your_password</programlisting>
The <literal>xenapi_connection_url</literal> is generally the management The <literal>xenapi_connection_url</literal> is generally the management
network IP address of the XenServer. Though it is possible to use the network IP address of the XenServer. Though it is possible to use the
internal network IP Address (169.250.0.1) to contact XenAPI, this does not internal network IP Address (169.250.0.1) to contact XenAPI, this does not
allow live migration between hosts, and other functionalities like host aggregates allow live migration between hosts. Other functionalities such as host aggregates,
do not work. do not work.
</para></note> </para></note>
<para>It is possible to manage Xen using libvirt, though this is not well-tested or supported. To <para>It is possible to manage Xen using libvirt, though this is not well-tested or supported. To
@ -38,7 +38,7 @@ virt_type = xen</programlisting></para>
<title>Agent</title> <title>Agent</title>
<para> <para>
If you don't have the guest agent on your VMs, it takes a long time for nova to decide the VM has successfully started. If you don't have the guest agent on your VMs, it takes a long time for nova to decide the VM has successfully started.
Generally a large timeout is required for Windows instances, bug you may want to tweak <literal>agent_version_timeout</literal> Generally a large timeout is required for Windows instances, but you may want to tweak <literal>agent_version_timeout</literal>.
</para></section> </para></section>
<section xml:id="xen-firewall"> <section xml:id="xen-firewall">
<title>Firewall</title> <title>Firewall</title>