Understanding Bare Metal service¶
Why Provision Bare Metal¶
Here are a few use-cases for bare metal (physical server) provisioning in cloud; there are doubtless many more interesting ones:
High-performance computing clusters
Computing tasks that require access to hardware devices which can’t be virtualized
Database hosting (some databases run poorly in a hypervisor)
Single tenant, dedicated hardware for performance, security, dependability and other regulatory requirements
Or, rapidly deploying a cloud infrastructure
The following diagram shows the relationships and how all services come into play during the provisioning of a physical server. (Note that Ceilometer and Swift can be used with Ironic, but are missing from this diagram.)
Key Technologies for Bare Metal Hosting¶
Preboot Execution Environment (PXE)¶
PXE is part of the Wired for Management (WfM) specification developed by Intel and Microsoft. The PXE enables system’s BIOS and network interface card (NIC) to bootstrap a computer from the network in place of a disk. Bootstrapping is the process by which a system loads the OS into local memory so that it can be executed by the processor. This capability of allowing a system to boot over a network simplifies server deployment and server management for administrators.
Dynamic Host Configuration Protocol (DHCP)¶
DHCP is a standardized networking protocol used on Internet Protocol (IP) networks for dynamically distributing network configuration parameters, such as IP addresses for interfaces and services. Using PXE, the BIOS uses DHCP to obtain an IP address for the network interface and to locate the server that stores the network bootstrap program (NBP).
Network Bootstrap Program (NBP)¶
NBP is equivalent to GRUB (GRand Unified Bootloader) or LILO (LInux LOader) - loaders which are traditionally used in local booting. Like the boot program in a hard drive environment, the NBP is responsible for loading the OS kernel into memory so that the OS can be bootstrapped over a network.
Trivial File Transfer Protocol (TFTP)¶
TFTP is a simple file transfer protocol that is generally used for automated transfer of configuration or boot files between machines in a local environment. In a PXE environment, TFTP is used to download NBP over the network using information from the DHCP server.
Intelligent Platform Management Interface (IPMI)¶
IPMI is a standardized computer system interface used by system administrators for out-of-band management of computer systems and monitoring of their operation. It is a method to manage systems that may be unresponsive or powered off by using only a network connection to the hardware rather than to an operating system.
Understanding Bare Metal Deployment¶
What happens when a boot instance request comes in? The below diagram walks through the steps involved during the provisioning of a bare metal instance.
These pre-requisites must be met before the deployment process:
Dependent packages to be configured on the Bare Metal service node(s) where ironic-conductor is running like tftp-server, ipmi, grub/ipxe, etc for bare metal provisioning.
Nova must be configured to make use of the bare metal service endpoint and compute driver should be configured to use ironic driver on the Nova compute node(s).
Flavors to be created for the available hardware. Nova must know the flavor to boot from.
Images to be made available in Glance. Listed below are some image types required for successful bare metal deployment:
Hardware to be enrolled via the bare metal API service.
This describes a typical bare metal node deployment within OpenStack using PXE to boot the ramdisk. Depending on the ironic driver interfaces used, some of the steps might be marginally different, however the majority of them will remain the same.
A boot instance request comes in via the Nova API, through the message queue to the Nova scheduler.
Nova scheduler applies filters and finds the eligible hypervisor. The nova scheduler also uses the flavor’s
extra_specs, such as
cpu_arch, to match the target physical node.
Nova compute manager claims the resources of the selected hypervisor.
Nova compute manager creates (unbound) tenant virtual interfaces (VIFs) in the Networking service according to the network interfaces requested in the nova boot request. A caveat here is, the MACs of the ports are going to be randomly generated, and will be updated when the VIF is attached to some node to correspond to the node network interface card’s (or bond’s) MAC.
A spawn task is created by the nova compute which contains all the information such as which image to boot from etc. It invokes the
driver.spawnfrom the virt layer of Nova compute. During the spawn process, the virt driver does the following:
Updates the target ironic node with the information about deploy image, instance UUID, requested capabilities and various flavor properties.
Validates node’s power and deploy interfaces, by calling the ironic API.
Attaches the previously created VIFs to the node. Each neutron port can be attached to any ironic port or port group, with port groups having higher priority than ports. On ironic side, this work is done by the network interface. Attachment here means saving the VIF identifier into ironic port or port group and updating VIF MAC to match the port’s or port group’s MAC, as described in bullet point 4.
Generates config drive, if requested.
Nova’s ironic virt driver issues a deploy request via the Ironic API to the Ironic conductor servicing the bare metal node.
Virtual interfaces are plugged in and Neutron API updates DHCP port to set PXE/TFTP options. In case of using
neutronnetwork interface, ironic creates separate provisioning ports in the Networking service, while in case of
flatnetwork interface, the ports created by nova are used both for provisioning and for deployed instance networking.
The ironic node’s boot interface prepares (i)PXE configuration and caches deploy kernel and ramdisk.
The ironic node’s management interface issues commands to enable network boot of a node.
The ironic node’s deploy interface caches the instance image (normal deployment), kernel and ramdisk (
ramdiskdeploy) or ISO (
ramdiskdeploy with virtual media).
The ironic node’s power interface instructs the node to power on.
The node boots the deploy ramdisk.
Depending on the exact driver used, the deploy ramdisk downloads the image from a URL (Direct deploy) or the conductor uses SSH to execute commands (Ansible deploy). The URL can be generated by Swift API-compatible object stores, for example Swift itself or RadosGW, or provided by a user.
The image deployment is done.
The node’s boot interface switches pxe config to refer to instance images (or, in case of local boot, sets boot device to disk), and asks the ramdisk agent to soft power off the node. If the soft power off by the ramdisk agent fails, the bare metal node is powered off via IPMI/BMC call.
The deploy interface triggers the network interface to remove provisioning ports if they were created, and binds the tenant ports to the node if not already bound. Then the node is powered on.
There are 2 power cycles during bare metal deployment; the first time the node is powered-on when ramdisk is booted, the second time after the image is deployed.
The bare metal node’s provisioning state is updated to
Below is the diagram that describes the above process.
The following two examples describe what ironic is doing in more detail, leaving out the actions performed by nova and some of the more advanced options.
Example: PXE Boot and Direct Deploy Process¶
This process is how Direct deploy works.