From a7cf4358fd8b782fd2d622032ec97453c5fccd38 Mon Sep 17 00:00:00 2001 From: shilla-saebi Date: Tue, 3 Jun 2014 00:20:42 -0400 Subject: [PATCH] change to section_compute-configure-xen changed: Other functionalities such as host aggregates, do not work. changed bug Change-Id: If67a1a7fe54c60bd2a614a0faeda17f1cca29a7d --- .../compute/section_compute-configure-xen.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/config-reference/compute/section_compute-configure-xen.xml b/doc/config-reference/compute/section_compute-configure-xen.xml index 9890b1b65f..22dc48f1a2 100644 --- a/doc/config-reference/compute/section_compute-configure-xen.xml +++ b/doc/config-reference/compute/section_compute-configure-xen.xml @@ -24,7 +24,7 @@ xenapi_connection_password = your_password The xenapi_connection_url is generally the management 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 -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. It is possible to manage Xen using libvirt, though this is not well-tested or supported. To @@ -38,7 +38,7 @@ virt_type = xen Agent 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 agent_version_timeout +Generally a large timeout is required for Windows instances, but you may want to tweak agent_version_timeout.
Firewall