What is the BM on-line automation process？

Fancy Wang 0512 2022

BM online automation process

BM provides users with exclusive physical servers, providing excellent computing performance, and meeting the requirements of core applications for high performance, high stability, and high security. The issued BM can communicate with the VM network, and can flexibly cooperate with other cloud products such as VPC.

BM is mainly used in scenarios where some applications still need to be deployed on physical machines in the process of cloud transformation,

• including databases that are not suitable for deployment in VMs (such as Oracle RAC);
• computing clusters with high performance requirements, such as big data clusters, Distributed databases, etc.;
• application nodes require special peripherals, which are not suitable for virtualized servers;
• use separate servers according to the security requirements of application nodes.

The SDN controller realizes the automatic management of BM by connecting to the cloud platform Ironic module. The Ironic component is the BM management component of the OpenStack cloud platform, which can automatically power on and off the physical host, install or uninstall the operating system, etc. The SDN controller is linked with the OpenStack cloud platform to sense the online and offline and location information of the physical host, and automatically activate the network. The BM NIC supports load balancing, active/standby mode, and LACP three binding modes.

As shown in the figure, the automated process of BM management is divided into four stages: the inspector stage, the main purpose of which is to collect BM information for OpenStack Ironic components for subsequent BM service provisioning, and add BM to the BM pool; the deployment stage, BM is added to the deployment In the network, load and deploy the image file; in the tenant phase, the BM joins the service network to deploy computing services; in the release phase, the BM is released and the BM is returned to the BM pool.

The online process of BM is as follows:

• During project implementation, you need to configure the port where the BM is connected to the TOR, and configure LLDP packets to only be sent but not received.
• In the inspector phase, the host operating system needs to accept the LLDP packets sent by the TOR, and query the LLDP information, MAC address, and host UUID (Universally Unique Identifer) of the network port.
• When registering the interface information of the BM through the Web UI, you need to register the LLDP information and MAC information one by one network port, and register the UUID to the BM node.

• When a tenant applies for a BM instance, an interface is created through NovaCompute, and the Host_ID and LLDP information are set to empty. At this time, the network controller configures the interface to be invalid. When Ironic deploys BM, it will first switch the network to the installation network. After the OS installation is complete, it will update the Host_ID of the tenant network interface to the UUID of the corresponding host by updating the interface, and update the file information of the interface (using the LLDP of the network port). information, if it is a trunk interface, carry the LLDP information of the two physical interfaces of the trunk)
• The network controller completes the TOR configuration according to the interface attributes.
• If the BM is not used temporarily or the network port is resumed, the Ironic component creates or deletes the Neutron interface whose admin_state_up is false, and the network controller completes the operation of changing the state of the interface corresponding to the TOR according to the interface attributes.

We are a 100G switch with Nos, 100G module/network card factory in Shenzhen, China. We can provide you with one-stop service on products, transportation, customs clearance, and tariffs.