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
This commit is contained in:
Mate Lakat
parent
01814b406f
commit
c044c1b184
@ -5,95 +5,77 @@
|
|||||||
xml:id="section_compute-configure-xen">
|
xml:id="section_compute-configure-xen">
|
||||||
<title>Xen configuration reference</title>
|
<title>Xen configuration reference</title>
|
||||||
<para>
|
<para>
|
||||||
The following section discusses some commonly changed options in
|
The following section discusses some commonly changed options when
|
||||||
XenServer. The table below provides a complete reference of all
|
using the XenAPI driver. The table below provides a complete reference
|
||||||
configuration options available for configuring Xen with OpenStack.
|
of all configuration options available for configuring XAPI with
|
||||||
|
OpenStack.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
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
|
driver. To enable the XenAPI driver, add the following configuration
|
||||||
options <filename>/etc/nova/nova.conf</filename> and restart the
|
options to <filename>/etc/nova/nova.conf</filename> and restart
|
||||||
<systemitem class="service">nova-compute</systemitem> service:
|
<systemitem class="service">OpenStack Compute</systemitem>:
|
||||||
</para>
|
</para>
|
||||||
<programlisting language="ini">compute_driver = xenapi.XenAPIDriver
|
<programlisting language="ini">compute_driver = xenapi.XenAPIDriver
|
||||||
xenapi_connection_url = http://your_xenapi_management_ip_address
|
[xenserver]
|
||||||
xenapi_connection_username = root
|
connection_url = http://<replaceable>your_xenapi_management_ip_address</replaceable>
|
||||||
xenapi_connection_password = your_password</programlisting>
|
connection_username = root
|
||||||
|
connection_password = <replaceable>your_password</replaceable></programlisting>
|
||||||
<para>
|
<para>
|
||||||
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
|
contact your hypervisor and are the same details you use to connect
|
||||||
XenCenter, the XenServer management console, to your XenServer or XCP
|
XenCenter, the XenServer management console, to your XenServer node.
|
||||||
box.
|
|
||||||
</para>
|
</para>
|
||||||
<note>
|
<note>
|
||||||
<para>
|
<para>
|
||||||
The <literal>xenapi_connection_url</literal> is generally the
|
The <literal>connection_url</literal> is generally the
|
||||||
management network IP address of the XenServer. Though it is
|
management network IP address of the XenServer.
|
||||||
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.
|
|
||||||
</para>
|
</para>
|
||||||
</note>
|
</note>
|
||||||
<para>
|
|
||||||
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
|
|
||||||
<filename>/etc/nova/nova.conf</filename>:
|
|
||||||
<programlisting language="ini">compute_driver = libvirt.LibvirtDriver
|
|
||||||
|
|
||||||
[libvirt]
|
|
||||||
virt_type = xen</programlisting>
|
|
||||||
</para>
|
|
||||||
<section xml:id="xen-agent">
|
<section xml:id="xen-agent">
|
||||||
<title>Agent</title>
|
<title>Agent</title>
|
||||||
<para>
|
<para>
|
||||||
If you don't have the guest agent on your VMs, it takes a long time
|
The agent is a piece of software that runs on the instances, and
|
||||||
for nova to decide the VM has successfully started. Generally a
|
communicates with OpenStack. In case of the XenAPI driver, the
|
||||||
large timeout is required for Windows instances, but you may want
|
agent communicates with OpenStack through XenStore (see
|
||||||
to tweak <literal>agent_version_timeout</literal>.
|
<link xlink:href="http://wiki.xen.org/wiki/XenStore">the Xen Wiki</link>
|
||||||
|
for more information on XenStore).
|
||||||
</para>
|
</para>
|
||||||
</section>
|
|
||||||
<section xml:id="xen-firewall">
|
|
||||||
<title>Firewall</title>
|
|
||||||
<para>
|
<para>
|
||||||
If using nova-network, iptables is supported:
|
If you don't have the guest agent on your VMs, it takes a long time
|
||||||
<programlisting language="ini">firewall_driver = nova.virt.firewall.IptablesFirewallDriver</programlisting>
|
for OpenStack Compute to detect that the VM has successfully
|
||||||
Alternately, doing the isolation in Dom0:
|
started. Generally a large timeout is required for Windows
|
||||||
<programlisting language="ini">firewall_driver = nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver</programlisting>
|
instances, but you may want to adjust:
|
||||||
|
<literal>agent_version_timeout</literal> within the
|
||||||
|
<literal>[xenserver]</literal> section.
|
||||||
</para>
|
</para>
|
||||||
</section>
|
</section>
|
||||||
<section xml:id="xen-vnc">
|
<section xml:id="xen-vnc">
|
||||||
<title>VNC proxy address</title>
|
<title>VNC proxy address</title>
|
||||||
<para>
|
<para>
|
||||||
Assuming you are talking to XenAPI through the host local
|
Assuming you are talking to XAPI through a management network, and
|
||||||
management network, and XenServer is on the address: 169.254.0.1,
|
XenServer is on the address: 10.10.1.34 specify the same address
|
||||||
you can use the following:
|
for the vnc proxy address:
|
||||||
<literal>vncserver_proxyclient_address=169.254.0.1</literal>
|
<literal>vncserver_proxyclient_address=<replaceable>10.10.1.34</replaceable></literal>
|
||||||
</para>
|
</para>
|
||||||
</section>
|
</section>
|
||||||
<section xml:id="xen-storage">
|
<section xml:id="xen-storage">
|
||||||
<title>Storage</title>
|
<title>Storage</title>
|
||||||
<para>
|
<para>
|
||||||
You can specify which Storage Repository to use with nova by
|
You can specify which Storage Repository to use with nova by
|
||||||
looking at the following flag. The default is to use the
|
editing the following flag. To use the local-storage setup by the
|
||||||
local-storage setup by the default installer:
|
default installer:
|
||||||
<programlisting language="ini">sr_matching_filter = "other-config:i18n-key=local-storage"</programlisting>
|
<programlisting language="ini">sr_matching_filter = "other-config:i18n-key=local-storage"</programlisting>
|
||||||
Another good alternative is to use the "default" storage (for
|
Another alternative is to use the "default" storage (for example if
|
||||||
example if you have attached NFS or any other shared storage):
|
you have attached NFS or any other shared storage):
|
||||||
<programlisting language="ini">sr_matching_filter = "default-sr:true"</programlisting>
|
<programlisting language="ini">sr_matching_filter = "default-sr:true"</programlisting>
|
||||||
<note>
|
|
||||||
<para>
|
|
||||||
To use a XenServer pool, you must create the pool by using
|
|
||||||
the Host Aggregates feature.
|
|
||||||
</para>
|
|
||||||
</note>
|
|
||||||
</para>
|
</para>
|
||||||
</section>
|
</section>
|
||||||
<section xml:id="xen-config-reference-table">
|
<section xml:id="xen-config-reference-table">
|
||||||
<title>Xen configuration reference</title>
|
<title>XenAPI configuration reference</title>
|
||||||
<para>
|
<para>
|
||||||
To customize the Xen driver, use the configuration option settings
|
To customize the XenAPI driver, use the configuration option
|
||||||
documented in <xref linkend="config_table_nova_xen"/>.
|
settings documented in <xref linkend="config_table_nova_xen"/>.
|
||||||
</para>
|
</para>
|
||||||
</section>
|
</section>
|
||||||
</section>
|
</section>
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user