Features of the Bare Metal Server Management Framework
The BMS management framework provides the following features:
BMS Image management—Provides a list of available bootable images available to the Tenant users to boot their server instances or BMS. The BMS framework uses Glance, which is an OpenStack service used for Image Management.
BMS Flavor management—Provides a list of available flavors of the BMS available in the inventory. The flavors represent the capacity or class of the BMS, such as disk size, memory size, number of cores or the manufacturer of BMS. The BMS framework creates pools of BMS based on their capability, class, or both, and then makes them available to the Tenant users. The BMS framework uses Nova, which is an OpenStack service used to provision computing instances or virtual servers. Nova can be used to create virtual machines and bare metal servers using Ironic. Flavors are used in OpenStack to define the compute, memory, and storage capacity of the Nova computing instances.
BMS Life Cycle Management—Includes the following:
Bringing powered off servers online in a secure manner—As soon as a BMS is powered off, it is disconnected from the Tenant user network and connected to a cleaning network for clean up of the server. A server is connected to a cleaning network for cleaning operations when it is not being used. If the server is deployed, it is connected to the provisioning network.
Reclaiming the provisioned servers and instances after they are decommissioned by the Tenant users—After cleaning up, the BMS is added to the pool of available server ready to be deployed as a new BMS. The boot up process is performed on a secure network to prevent the possibility of snooping in a multi-tenant cloud. The cleaning process ensures that the BMS is ready to be deployed with the same or different image when needed.
The BMS framework uses Ironic, which is an OpenStack service used to launch bare metal machines. Ironic integrates with the bare metal driver in Nova to maintain BMS lifecycle management efficiently.
BMS Inventory Management— Maintains an inventory of all the servers under the BMS framework. The inventory includes the deployed instances and servers as well as those available for deployment.
BMS IPAM management— Ensures that the IP address management is consistent between the virtual and physical instances. IPAM is managed by the Contrail controller.
BMS Network Security management— The boot cycle and/or cleaning of bare metal servers are extensive and lengthy processes, which makes provisioning and cleaning phases susceptible for snooping by hackers in multi-tenant cloud environments. Hence, the BMS framework uses private networks for the provisioning and cleaning phases of the servers. Once the servers are ready for deployment, the BMS framework deploys the servers in the Tenant user network.
Tenant Network management— Manages connectivity between the bare metal servers and Tenant user networks or provisioning and cleaning networks depending on the deployment state of the server.
BMS discovery and onboarding— The BMS framework supports both the discovery of new servers as well as onboarding of the brownfield servers.
A deployed server must be unprovisioned and made available before it can be deleted from BMS node list.