About bare metal service
Bare metal service provides physical devices as resources for users. Users can use the bare metal service to fast deploy physical servers or incorporate physical servers into the system for unified management.
Benefits
High performance—Provides exclusive physical resources for users, avoiding performance degradation caused by virtualization.
Unified management—Supports cloud-managed servers with their systems retained.
Application scenarios
High-performance computing—Bare metal service is applicable to high-performance computing scenarios because it avoids performance degradation and delay caused by virtualization.
Database—Bare metal service allows key databases to be deployed on exclusive physical servers.
Concepts
Bare metal compute node
A bare metal compute node provides computing capabilities for the bare metal service. You must deploy a compute node for the bare metal service as you deploy the system. For more information, see "Deploy a bare metal compute node."
Bare metal node
A bare metal node is a physical server, which you can add to the system for management.
Bare metal instance
After a bare metal node is discovered, deployed, and incorporated to the system, it provides computing service to the system as a bare metal instance. One bare metal node is mapped to one bare metal instance.
Ironic
Bare metal service is a kind of physical server management service based on OpenStack Ironic. This system allows users to operate a physical server and deploy images to that physical server. Ironic service allows you to add, delete, install, and deploy bare metal servers and manage power. Ironic allows vendors to add specific expansion drivers for their own servers.
Ironic includes the following components:
Ironic-API—RESTful API service. Administrators and other services use API to interact with Ironic.
Ironic-Conductor—Calls features by interacting with Ironic-API.
Drivers—Manage different servers.
Message queue—Used for communication between components.
Database—Stores resource information.
Restrictions and guidelines
Server and bare metal service compatibility
For the physical servers compatible with bare metal service, see Software and Hardware Compatibility.
|
|
|
Networking schemes
The following networking schemes are available:
VLAN VPC
VXLAN network overlay VPC
Miscellaneous
You cannot edit image tools.
Incorporated bare metal nodes can only be deployed on the Resources > Bare Metal page. The Cloud Services > Compute > Bare Metal page only displays information about bare metal nodes that are not incorporated.
After you configure a bare metal node, do not delete the network, image, or tenancy, or use the IP addresses specified in node configuration.
To avoid network information errors, create only one bare metal AZ alias.
The egress name of a bare metal compute node must be unique on CloudOS.
You can create only one bare metal management network in a CloudOS environment.
The physical NIC of bare metal does not support security group rule assignment.
You cannot bare metal storage AZs to the system, because bare metal compute nodes lack dependencies and the deployed storage service does not have heartbeat messages. To mount storage volumes on a bare metal instance, you must install the agent service on that bare metal instance.
To mount disks for a bare metal node added before upgrade, delete the node and discover it again.
Before you start a bare metal instance, verify that the power supply is normal and the server has exited maintenance mode.
The To Be Reclaimed state is an intermediate state, which identifies a deployed bare metal node. After a bare metal node is deployed, it does not enter Installing state immediately. As a result, the available bare metal nodes are incorrect when you create a bare metal instance. The To Be Reclaimed state resolves such an issue.