From c044c1b1840de9499806ec577a73239db50f08e7 Mon Sep 17 00:00:00 2001 From: Mate Lakat Date: Wed, 10 Dec 2014 11:47:29 +0100 Subject: [PATCH] XenAPI: Cleanup configuration section * Remove references to Host Internal Management Network, as they are confusing. * Remove Xen+libvirt instructions. * Remove host aggregate related notes. Change-Id: I321bcfce193d63e5768327359ecf9991a4b407f2 --- .../compute/section_compute-configure-xen.xml | 92 ++++++++----------- 1 file changed, 37 insertions(+), 55 deletions(-) diff --git a/doc/config-reference/compute/section_compute-configure-xen.xml b/doc/config-reference/compute/section_compute-configure-xen.xml index 9bde0dbd3e..5b8f083222 100644 --- a/doc/config-reference/compute/section_compute-configure-xen.xml +++ b/doc/config-reference/compute/section_compute-configure-xen.xml @@ -5,95 +5,77 @@ xml:id="section_compute-configure-xen"> Xen configuration reference - The following section discusses some commonly changed options in - XenServer. The table below provides a complete reference of all - configuration options available for configuring Xen with OpenStack. + The following section discusses some commonly changed options when + using the XenAPI driver. The table below provides a complete reference + of all configuration options available for configuring XAPI with + OpenStack. - The recommended way to use Xen with OpenStack is through the XenAPI + The recommended way to use XAPI with OpenStack is through the XenAPI driver. To enable the XenAPI driver, add the following configuration - options /etc/nova/nova.conf and restart the - nova-compute service: + options to /etc/nova/nova.conf and restart + OpenStack Compute: compute_driver = xenapi.XenAPIDriver -xenapi_connection_url = http://your_xenapi_management_ip_address -xenapi_connection_username = root -xenapi_connection_password = your_password +[xenserver] +connection_url = http://your_xenapi_management_ip_address +connection_username = root +connection_password = your_password - These connection details are used by the OpenStack Compute service to + These connection details are used by OpenStack Compute service to contact your hypervisor and are the same details you use to connect - XenCenter, the XenServer management console, to your XenServer or XCP - box. + XenCenter, the XenServer management console, to your XenServer node. - 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. - Other functionalities such as host aggregates, do not work. + The connection_url is generally the + management network IP address of the XenServer. - - It is possible to manage Xen using libvirt, though this is not - well-tested or supported. To experiment using Xen through libvirt add - the following configuration options - /etc/nova/nova.conf: - compute_driver = libvirt.LibvirtDriver - -[libvirt] -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, but you may want - to tweak agent_version_timeout. + The agent is a piece of software that runs on the instances, and + communicates with OpenStack. In case of the XenAPI driver, the + agent communicates with OpenStack through XenStore (see + the Xen Wiki + for more information on XenStore). -
-
- Firewall - If using nova-network, iptables is supported: - firewall_driver = nova.virt.firewall.IptablesFirewallDriver - Alternately, doing the isolation in Dom0: - firewall_driver = nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver + If you don't have the guest agent on your VMs, it takes a long time + for OpenStack Compute to detect that the VM has successfully + started. Generally a large timeout is required for Windows + instances, but you may want to adjust: + agent_version_timeout within the + [xenserver] section.
VNC proxy address - Assuming you are talking to XenAPI through the host local - management network, and XenServer is on the address: 169.254.0.1, - you can use the following: - vncserver_proxyclient_address=169.254.0.1 + Assuming you are talking to XAPI through a management network, and + XenServer is on the address: 10.10.1.34 specify the same address + for the vnc proxy address: + vncserver_proxyclient_address=10.10.1.34
Storage You can specify which Storage Repository to use with nova by - looking at the following flag. The default is to use the - local-storage setup by the default installer: + editing the following flag. To use the local-storage setup by the + default installer: sr_matching_filter = "other-config:i18n-key=local-storage" - Another good alternative is to use the "default" storage (for - example if you have attached NFS or any other shared storage): + Another alternative is to use the "default" storage (for example if + you have attached NFS or any other shared storage): sr_matching_filter = "default-sr:true" - - - To use a XenServer pool, you must create the pool by using - the Host Aggregates feature. - -
- Xen configuration reference + XenAPI configuration reference - To customize the Xen driver, use the configuration option settings - documented in . + To customize the XenAPI driver, use the configuration option + settings documented in .