openstack-manuals/doc/config-reference/compute/section_compute-hypervisors.xml
Andreas Jaeger e77dbe04ac Remove extra xmlns lines
We do not need these namespaces like xmlns:svg and xmlns:html anywhere,
remove the declarations.

Change-Id: Ic6aa62c28b2b21092d1e1d5c6f431807519f59af
2014-05-02 08:24:52 +02:00

103 lines
5.2 KiB
XML

<section xml:id="section_compute-hypervisors"
xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:xi="http://www.w3.org/2001/XInclude"
version="5.0">
<title>Hypervisors</title>
<para>OpenStack Compute supports many hypervisors, which might
make it difficult for you to choose one. Most installations
use only one hypervisor. However you can use <xref
linkend="computefilter"/> and <xref
linkend="imagepropertiesfilter"/> to schedule to different
hypervisors within the same installation. The following links
help you choose a hypervisor. See <link
xlink:href="http://wiki.openstack.org/HypervisorSupportMatrix"
>http://wiki.openstack.org/HypervisorSupportMatrix</link>
for a detailed list of features and support across the
hypervisors.</para>
<para>The following hypervisors are supported:</para>
<itemizedlist>
<listitem>
<para><link
xlink:href="http://www.linux-kvm.org/page/Main_Page"
>KVM</link> - Kernel-based Virtual Machine. The
virtual disk formats that it supports is inherited from
QEMU since it uses a modified QEMU program to launch
the virtual machine. The supported formats include raw
images, the qcow2, and VMware formats.</para>
</listitem>
<listitem>
<para><link xlink:href="http://lxc.sourceforge.net/"
>LXC</link> - Linux Containers (through libvirt),
use to run Linux-based virtual machines.</para>
</listitem>
<listitem>
<para><link xlink:href="http://wiki.qemu.org/Manual"
>QEMU</link> - Quick EMUlator, generally only used
for development purposes.</para>
</listitem>
<listitem>
<para><link
xlink:href="http://user-mode-linux.sourceforge.net/"
>UML</link> - User Mode Linux, generally only used
for development purposes.</para>
</listitem>
<listitem>
<para><link xlink:href="http://www.vmware.com/products/vsphere-hypervisor/support.html"
>VMware vSphere</link> 4.1 update 1 and newer, runs VMware-based Linux and
Windows images through a connection with a vCenter server or directly with an ESXi
host.</para>
</listitem>
<listitem>
<para><link xlink:href="http://www.xen.org">Xen</link> -
XenServer, Xen Cloud Platform (XCP), use to run Linux
or Windows virtual machines. You must install the
<systemitem class="service"
>nova-compute</systemitem> service in a
para-virtualized VM.</para>
</listitem>
<listitem>
<para><link
xlink:href="http://www.microsoft.com/en-us/server-cloud/windows-server/server-virtualization-features.aspx"
> Hyper-V</link> - Server virtualization with
Microsoft's Hyper-V, use to run Windows, Linux, and
FreeBSD virtual machines. Runs <systemitem
class="service">nova-compute</systemitem> natively
on the Windows virtualization platform.</para>
</listitem>
<listitem>
<para><link
xlink:href="https://wiki.openstack.org/wiki/Baremetal"
> Bare Metal</link> - Not a hypervisor in the
traditional sense, this driver provisions physical
hardware through pluggable sub-drivers (for example, PXE for image
deployment, and IPMI for power management).</para>
</listitem>
</itemizedlist>
<section xml:id="hypervisor-configuration-basics">
<title>Hypervisor configuration basics</title>
<para>The node where the <systemitem class="service"
>nova-compute</systemitem> service is installed and
running is the machine that runs all the virtual machines,
referred to as the compute node in this guide.</para>
<para>By default, the selected hypervisor is KVM. To change to
another hypervisor, change the
<literal>libvirt_type</literal> option in
<filename>nova.conf</filename> and restart the
<systemitem class="service">nova-compute</systemitem>
service.</para>
<para>Here are the general <filename>nova.conf</filename>
options that are used to configure the compute node's
hypervisor: <xref linkend="config_table_nova_hypervisor"/>.</para>
<para>Specific options for particular hypervisors
can be found in following sections.</para>
</section>
<xi:include href="section_hypervisor_kvm.xml"/>
<xi:include href="section_hypervisor_qemu.xml"/>
<xi:include href="section_introduction-to-xen.xml"/>
<xi:include href="section_hypervisor_lxc.xml"/>
<xi:include href="section_hypervisor_vmware.xml"/>
<xi:include href="section_hypervisor_hyper-v.xml"/>
<xi:include href="section_hypervisor_baremetal.xml"/>
</section>