64b6c9261e
Current folder name New folder name Book title ---------------------------------------------------------- basic-install DELETE cli-guide DELETE common common NEW admin-guide-cloud Cloud Administrators Guide docbkx-example DELETE openstack-block-storage-admin DELETE openstack-compute-admin DELETE openstack-config config-reference OpenStack Configuration Reference openstack-ha high-availability-guide OpenStack High Availabilty Guide openstack-image image-guide OpenStack Virtual Machine Image Guide openstack-install install-guide OpenStack Installation Guide openstack-network-connectivity-admin admin-guide-network OpenStack Networking Administration Guide openstack-object-storage-admin DELETE openstack-security security-guide OpenStack Security Guide openstack-training training-guide OpenStack Training Guide openstack-user user-guide OpenStack End User Guide openstack-user-admin user-guide-admin OpenStack Admin User Guide glossary NEW OpenStack Glossary bug: #1220407 Change-Id: Id5ffc774b966ba7b9a591743a877aa10ab3094c7 author: diane fleming
52 lines
2.5 KiB
XML
52 lines
2.5 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<section xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
|
|
xml:id="baremetal">
|
|
<title>Bare Metal Driver</title>
|
|
<para>
|
|
</para>
|
|
<para>
|
|
The baremetal driver is a hypervisor driver for OpenStack Nova
|
|
Compute. Within the OpenStack framework, it has the same role
|
|
as the drivers for other hypervisors (libvirt, xen, etc), and
|
|
yet it is presently unique in that the hardware is not
|
|
virtualized - there is no hypervisor between the tenants and
|
|
the physical hardware. It exposes hardware via OpenStack's
|
|
API, using pluggable sub-drivers to deliver machine imaging
|
|
(PXE) and power control (IPMI). With this, provisioning and
|
|
management of physical hardware is accomplished using common
|
|
cloud APIs and tools, such as Heat or salt-cloud. However, due
|
|
to this unique situation, using the baremetal driver requires
|
|
some additional preparation of its environment, the details of
|
|
which are beyond the scope of this guide.
|
|
</para>
|
|
<note><para>
|
|
Some OpenStack Compute features are not implemented by
|
|
the baremetal hypervisor driver. See the <link
|
|
xlink:href="http://wiki.openstack.org/HypervisorSupportMatrix">
|
|
hypervisor support matrix</link> for details.
|
|
</para></note>
|
|
<para>
|
|
For the Baremetal driver to be loaded and function properly,
|
|
ensure that the following options are set in
|
|
<filename>/etc/nova/nova.conf</filename> on your <systemitem
|
|
class="service">nova-compute</systemitem> hosts.
|
|
<programlisting language="ini">[default]
|
|
compute_driver=nova.virt.baremetal.driver.BareMetalDriver
|
|
firewall_driver = nova.virt.firewall.NoopFirewallDriver
|
|
scheduler_host_manager=nova.scheduler.baremetal_host_manager.BaremetalHostManager
|
|
ram_allocation_ratio=1.0
|
|
reserved_host_memory_mb=0</programlisting>
|
|
</para>
|
|
<para>
|
|
There are many configuration options specific to the
|
|
Baremetal driver. Also, some additional steps will be
|
|
required, such as building the baremetal deploy ramdisk. See
|
|
the <link
|
|
xlink:href="https://wiki.openstack.org/wiki/GeneralBareMetalProvisioningFramework">
|
|
main wiki page</link> for details and implementation suggestions.
|
|
</para>
|
|
<xi:include href="tables/nova-baremetal.xml"/>
|
|
</section>
|