Merge "Remove nova-baremetal"

This commit is contained in:
Jenkins 2015-04-17 07:39:36 +00:00 committed by Gerrit Code Review
commit bd3b1a5d60
4 changed files with 0 additions and 184 deletions

View File

@ -1,130 +0,0 @@
<?xml version='1.0' encoding='UTF-8'?>
<para xmlns="http://docbook.org/ns/docbook" version="5.0">
<!-- Warning: Do not edit this file. It is automatically
generated and your changes will be overwritten.
The tool to do so lives in openstack-doc-tools repository. -->
<table rules="all" xml:id="config_table_nova_baremetal">
<caption>Description of baremetal configuration options</caption>
<col width="50%"/>
<col width="50%"/>
<thead>
<tr>
<th>Configuration option = Default value</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<th colspan="2">[baremetal]</th>
</tr>
<tr>
<td>db_backend = sqlalchemy</td>
<td>(StrOpt) The backend to use for bare-metal database</td>
</tr>
<tr>
<td>deploy_kernel = None</td>
<td>(StrOpt) Default kernel image ID used in deployment phase</td>
</tr>
<tr>
<td>deploy_ramdisk = None</td>
<td>(StrOpt) Default ramdisk image ID used in deployment phase</td>
</tr>
<tr>
<td>driver = nova.virt.baremetal.pxe.PXE</td>
<td>(StrOpt) Baremetal driver back-end (pxe or tilera)</td>
</tr>
<tr>
<td>flavor_extra_specs = </td>
<td>(ListOpt) A list of additional capabilities corresponding to flavor_extra_specs for this compute host to advertise. Valid entries are name=value, pairs For example, "key1:val1, key2:val2"</td>
</tr>
<tr>
<td>ipmi_power_retry = 10</td>
<td>(IntOpt) Maximal number of retries for IPMI operations</td>
</tr>
<tr>
<td>net_config_template = $pybasedir/nova/virt/baremetal/net-dhcp.ubuntu.template</td>
<td>(StrOpt) Template file for injected network config</td>
</tr>
<tr>
<td>power_manager = nova.virt.baremetal.ipmi.IPMI</td>
<td>(StrOpt) Baremetal power management method</td>
</tr>
<tr>
<td>pxe_append_params = nofb nomodeset vga=normal</td>
<td>(StrOpt) Additional append parameters for baremetal PXE boot</td>
</tr>
<tr>
<td>pxe_bootfile_name = pxelinux.0</td>
<td>(StrOpt) This gets passed to Neutron as the bootfile dhcp parameter.</td>
</tr>
<tr>
<td>pxe_config_template = $pybasedir/nova/virt/baremetal/pxe_config.template</td>
<td>(StrOpt) Template file for PXE configuration</td>
</tr>
<tr>
<td>pxe_deploy_timeout = 0</td>
<td>(IntOpt) Timeout for PXE deployments. Default: 0 (unlimited)</td>
</tr>
<tr>
<td>pxe_network_config = False</td>
<td>(BoolOpt) If set, pass the network configuration details to the initramfs via cmdline.</td>
</tr>
<tr>
<td>sql_connection = sqlite:///$state_path/baremetal_nova.sqlite</td>
<td>(StrOpt) The SQLAlchemy connection string used to connect to the bare-metal database</td>
</tr>
<tr>
<td>terminal = shellinaboxd</td>
<td>(StrOpt) Path to baremetal terminal program</td>
</tr>
<tr>
<td>terminal_cert_dir = None</td>
<td>(StrOpt) Path to baremetal terminal SSL cert(PEM)</td>
</tr>
<tr>
<td>terminal_pid_dir = $state_path/baremetal/console</td>
<td>(StrOpt) Path to directory stores pidfiles of baremetal_terminal</td>
</tr>
<tr>
<td>tftp_root = /tftpboot</td>
<td>(StrOpt) Baremetal compute node's tftp root path</td>
</tr>
<tr>
<td>use_file_injection = False</td>
<td>(BoolOpt) If True, enable file injection for network info, files and admin password</td>
</tr>
<tr>
<td>use_unsafe_iscsi = False</td>
<td>(BoolOpt) Do not set this out of dev/test environments. If a node does not have a fixed PXE IP address, volumes are exported with globally opened ACL</td>
</tr>
<tr>
<td>vif_driver = nova.virt.baremetal.vif_driver.BareMetalVIFDriver</td>
<td>(StrOpt) Baremetal VIF driver.</td>
</tr>
<tr>
<td>virtual_power_host_key = None</td>
<td>(StrOpt) The ssh key for virtual power host_user</td>
</tr>
<tr>
<td>virtual_power_host_pass = </td>
<td>(StrOpt) Password for virtual power host_user</td>
</tr>
<tr>
<td>virtual_power_host_user = </td>
<td>(StrOpt) User to execute virtual power commands as</td>
</tr>
<tr>
<td>virtual_power_ssh_host = </td>
<td>(StrOpt) IP or name to virtual power host</td>
</tr>
<tr>
<td>virtual_power_ssh_port = 22</td>
<td>(IntOpt) Port to use for ssh to virtual power host</td>
</tr>
<tr>
<td>virtual_power_type = virsh</td>
<td>(StrOpt) Base command to use for virtual power(vbox, virsh)</td>
</tr>
</tbody>
</table>
</para>

View File

@ -65,14 +65,6 @@
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>
@ -96,5 +88,4 @@
<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>

View File

@ -13,7 +13,6 @@
<xi:include href="../../common/tables/nova-authentication.xml"/>
<xi:include href="../../common/tables/nova-auth_token.xml"/>
<xi:include href="../../common/tables/nova-availabilityzones.xml"/>
<xi:include href="../../common/tables/nova-baremetal.xml"/>
<xi:include href="../../common/tables/nova-ca.xml"/>
<xi:include href="../../common/tables/nova-cells.xml"/>
<xi:include href="../../common/tables/nova-common.xml"/>

View File

@ -1,44 +0,0 @@
<?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>Baremetal driver</title>
<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 through the OpenStack APIs, using pluggable sub-drivers to deliver
machine imaging (PXE) and power control (IPMI). With this, provisioning
and management of physical hardware is accomplished by using common cloud
APIs and tools, such as the Orchestration module (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.</para>
<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>Many configuration options are specific to the
Baremetal driver. Also, some additional steps are
required, such as building the baremetal deploy ramdisk. See
the <link
xlink:href="https://wiki.openstack.org/wiki/Baremetal">main wiki page</link> for details and implementation suggestions.
</para>
<para>To customize the Baremetal driver, use the configuration option
settings documented in <xref
linkend="config_table_nova_baremetal"/>.</para>
</section>