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."
A bare metal node is a physical server, which you can add to the system for management.
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.
A bare metal service is a physical server management service based on the OpenStack Ironic project. You can operate the physical server and deploy images to the physical bare metal server. Ironic enables you to add, delete, install, deploy bare metal servers, and manage power for bare metal servers. It allows vendors to add specific extension drivers to their servers to support most physical servers.
The Ironic service contains the following components:
Ironic-API—A RESTful API service, by which administrators and other services interact with the managed bare metal servers.
Ironic-Conductor—Its functionality is exposed via the API service. The Conductor and API services communicate via RPC.
Drivers—Drivers that support heterogeneous hardware.
Message queue—Enables communication between components.
Database— Stores information about the resources.
High performance—Provides exclusive physical resources for users, avoiding performance degradation caused by virtualization.
Unified management—Supports cloud-managed servers with their systems retained.
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.
The physical servers compatible with bare metal service are not restricted to Table-1.
Table-1 Server and bare metal service compatibility
|
Vendor |
Model |
|
H3C |
H3C FlexServer R390 |
|
H3C UIS R390 G2 |
|
|
H3C UIS R390X |
|
|
H3C UIS R390X G2 |
|
|
H3C UniServer R4900 G3 |
|
|
HPE |
HP ProLiant DL380 Gen7 |
|
HP ProLiant DL380p Gen8 |
|
|
HP ProLiant DL380 Gen9 |
|
|
HP ProLiant DL380 Gen10 |
|
|
HUAWEI |
Tecal RH2288 V3 |
|
Tecal RH2288H V3 |
|
|
FusionServer Pro RH2288H V5 |
|
|
FusionServer Pro RH2488H V5 |
|
|
Inspur |
NF5270M3 |
|
NF8460M3 |
|
|
NF5270M4 |
|
|
NF5280M4 |
|
|
NF5460M4 |
|
|
Sugon |
Sugon I620-G20 |
|
DELL |
PowerEdge R730 |
|
PowerEdge R810 |
|
|
Lenovo |
IBM X3650M5 |
|
ZTE |
ZXCLOUD R5300 G3 |
You cannot edit settings for a bare metal image tool.
The bare metal service is unavailable in multi-tenant scenarios.
An incorporated bare metal node can be deployed only on the bare metal resource pool management page. The bare metal creation or request page displays only information about non-incorporated bare metal nodes.
After you configure a bare metal node, do not delete the network, image, tenancy set for that node, and do not use the IP addresses specified for that node.
As a best practice to avoid network information error, create only one alias for a bare metal compute AZ.
Make sure the egress name for a bare metal compute node is different from any egress name on the UIS platform.
You can create only one bare metal management network on the platform.
A deployed bare metal compute node cannot be used as a storage AZ in the UIS platform, because it does not have required dependencies.
Before you can enable a bare metal instance, make sure the bare metal node is powered on and is not in maintenance mode.