Elastic Bare Metal Management(Plus)

Overview

Elastic Baremetal Management provides dedicated physical servers for your applications to ensure high performance and stability. In addition, this feature allows elastic scaling. You can apply for and scale resources based on your needs. Elastic Baremetal Management integrates the benefits of hosts and VM instances. It delivers powerful and stable computing capacities of hosts and allows you to use primary storages, L3 networks, and other resources on the Cloud for your applications. This way, it avoids virtualization overheads and allows flexible use of cloud resources and physical resources, thus promoting the availability of cloud resources. You can use this feature to deploy applications for traditional non-virtualization scenarios.

The Elastic Baremetal Management feature is provided in a separate module. Before you can use this feature, you need to purchase the Plus License of Elastic Baremetal Management, in addition to the Base License.
A tenant can use an elastic baremetal offering shared by the admin to create an elastic baremetal instance.

Concepts

Provision network: A provision network is a dedicated network for PXE boot and image downloads while creating elastic baremetal instances.
- Before you can use Elastic Baremetal Management, you need to deploy an IPv4 provision network.
- Provision networks require high network performance. We recommend that you use at least 10 Gigabit NICs for your provision network.
- You can configure a gateway for your provision network. This way, the provision network can be connected to other networks. If you do not need to connect your provision network with other networks, you do not need to configure a gateway for your provision network.
Elastic baremetal cluster: An elastic baremetal cluster consists of elastic baremetal instances. You can manage elastic baremetal instances by managing an elastic baremetal cluster where the instances reside.
- You must attach a provision network to an elastic baremetal cluster to provide PXE services for baremetal nodes in the cluster.
- You can attach only one provision network to an elastic baremetal cluster. However, you can attach a provision network to multiple elastic baremetal clusters.
- You can attach an L2 network to an elastic baremetal cluster to provide an extended L2 business network for elastic baremetal instances in the cluster. Elastic baremetal instances and VM instances that share the same L2 network with the elastic baremetal instances can access each other without using the gateway. The L2 network that you can attach to an elastic baremetal cluster can be of the VLAN or NoVLAN type.
Gateway node: A gateway node is a node where the ingress and egress traffic of the Cloud and elastic baremetal instances is forwarded.
- You can attach multiple gateway nodes to an elastic baremetal cluster. However, you can attach only one gateway node to an elastic baremetal cluster.
- A gateway node is used to take over primary storages and assign storage space for elastic baremetal instances.
- A gateway node provides iPXE, DHCP, and other services. It is used to deliver configuration settings to elastic baremetal instances.
Baremetal node: A baremetal node is used to create a baremetal instance and is identified based on the BMC interface and IPMI configuration setting.
- The management node must be connected to the IPMI network to remotely manage baremetal nodes.
- Baremetal nodes must be configured with the BMC interface, IPMI address, port, username, and password, and be connected to the IPMI network.
- A baremetal node can be distributed to only one elastic baremetal instance and an elastic baremetal instance can only be assigned one baremetal node.
- You can provide compute resources for elastic baremetal instances based on the baremetal node or baremetal offering.
Elastic baremetal instance offering: An elastic baremetal offering defines the number of vCPU cores, memory size, CPU architecture, CPU model, and other configuration settings of elastic baremetal instances.
- After you obtain the hardware information of a baremetal node on the UI, you can obtain the corresponding elastic baremetal offering. The Cloud allows you to manage baremetal nodes of the same elastic baremetal offering in a unified way.
- You can use an elastic baremetal offering to create an elastic baremetal instance. You can also release the advanced settings of baremetal nodes to avoid resource idling.
- You can create a pricing list for elastic baremetal instances based on elastic baremetal offerings. Then bills are generated for the elastic baremetal instances based on their usage.
Elastic baremetal instance: An elastic baremetal instance has the same performance as physical servers and allows elastic scaling. You can apply for and scale resources based on your needs.
- The following two startup methods are supported for elastic baremetal instances:
  - Volume: Uses a volume as the system volume of the elastic baremetal instance to install and deploy the operating system.
  - Local Disk: Uses a local disk as the system disk of the elastic baremetal instance to install and deploy the operating system.
  - The Local Disk (Non Take-Over) and Local Disk (Take-Over) methods are supported:
    - Local Disk (Non Take-Over): When you use a baremetal node to create the elastic baremetal instance, the operating system is downloaded from the Cloud and installed on the elastic baremetal instance. This method will format the local system disk.
    - Local Disk (Take-Over): When you use a baremetal node to create the elastic baremetal instance, the original operating system on the local system disk is used as the operating system of the elastic baremetal instance.
- The following describes the resources supplied to elastic baremetal instances of different startup methods:
  - For elastic baremetal instances of both the volume startup method and local disk startup method, baremetal nodes provide compute resources and L3 networks on the Cloud are used as the business networks.
  - For elastic baremetal instances of the volume startup method, SharedBlock or Ceph primary storages on the Cloud provide storage resources and the provision network provides support for PXE boot.
  - For elastic baremetal instances of local disk startup method, the local disks of the instances provide storage resources. If you attach data volumes to the instances, SharedBlock or Ceph primary storages on the Cloud also provides storage resources
- We recommend that you create an elastic baremetal instance by using an image that has installed the agent. Otherwise, you cannot open the console of the elastic baremetal instance, modify the password of the instance, attach a volume to or detach a volume from the instance, or attach a network to or detach a network from the instance.
- By default, the supported BIOS mode of the image used to create an elastic baremetal instance is UEFI. To use an image whose BIOS mode is Legacy, contact the official technical support.
- You can configure business networks for elastic baremetal instances. If you attach an L2 network to the cluster where your baremetal nodes reside, elastic baremetal instances and VM instances that share the same L2 network with the elastic baremetal instances can access each other without using the gateway.
- Elastic baremetal instances of the volume startup method allow you to release the associated baremetal node upon instance power-off. If you enable this feature, when an elastic baremetal instance of the volume startup method is powered off, the associated baremetal node is automatically released and can be used by another elastic baremetal instance. This mechanism avoids resource idling.

Scenarios

Scenarios that require high security and strict monitoring:
The financial and insurance industries have high requirements over business deployment compliance and data security. In these scenarios, you can use Baremetal Management to secure dedicated resources, data isolation, easy management, and operation-tracking. This way, you can ensure the reliability and security compliance of your key business system and data.
High-performance computing scenarios:
In supercomputing, genome sequencing, and other high-performance computing scenarios, the requirements over the computing performance, stability, and timeliness of the server are very high. The Baremetal Management feature is fitting for these scenarios. In addition, the feature can be used for scenarios that require high throughput or high computing performance that can accommodate changing access requests and scenarios. Virtualization and hyperthreading may compromise some performance. Deploying a reasonable number of baremetal clusters can meet the high-performance computing requirements.
Key database scenarios:
To meet business requirements, you may not want to deploy some key databases on VM instances while want to deploy the databases on physical servers that feature dedicated resources, network isolation, and guaranteed performance. In these scenarios, you can use Baremetal Management to provide dedicated high-performance physical servers for your applications.

Considerations

When you use the Elastic Baremetal Management feature, note that:

The server that you use as a baremetal node must have at least one PXE boot NIC used for network management. Make sure the first port of the first NIC of the server is used as the provision NIC.
You can use x86 servers and Kunpeng and other China localized mainstream ARM servers as baremetal nodes.
You can use x86 servers as gateway nodes. If you use an ARM server as a baremetal node, you need to add ARM repos for gateway nodes.
Physical network environments include management network, storage network, provision network, IPMI network, and business network. The provision network requires high performance. We recommend that you configure a 10-Gigabit network.
To avoid DHCP conflict, make sure that you do not configure an additional DHCP service.
You can use a flat network, public network, and VPC network as a business network.
Windows-based elastic baremetal instances only support L2 networks of the NoVLAN type.
You need to install the agent or relevant dependency packages on the elastic baremetal image. Otherwise, some features of elastic baremetal instances cannot work as expected.
You can use a Shared Block primary storage and Ceph Enterprise primary storage for elastic baremetal instances. Note that the version of Ceph Enterprise must be later than 4.2.0.300.
If you use a Ceph Enterprise primary storage, you need to login to the Ceph Enterprise management node, choose Setting > Access Token, and obtain an access token generated by using the admin account. Then you need to add the access token when you add a Ceph primary storage.
Note: Make sure that the license of the Ceph Enterprise storage is valid.

Figure 1. Obtain Access Token

Figure 2. Add Ceph Enterprise Primary Storage

The following table describes the limits on the primary storage that you can attach to an elastic baremetal cluster.

Table 1. Relationship of Elastic Baremetal Cluster and Primary Storage
Primary Storage	Elastic Baremetal Cluster
Ceph	You can attach only one Ceph primary storage to an elastic baremetal cluster.
Shared Block	You can attach one or more Shared Block primary storage to an elastic baremetal cluster.
Ceph + Shared Block	You can attach one Ceph primary storage (excluding Ceph Enterprise) and one or more Shared Block primary storage to an elastic baremetal cluster.

You can install mainstream x86 operating systems (OSs) and some ARM OSs on elastic baremetal instances.

Table 2. Operating Systems
CPU Architecture	OS Type	OS
x86	Windows	Windows 2012 Windows 2016 Windows 2019
x86	Linux	CentOS 7 CentOS 8 Ubuntu 18LTS Ubuntu 20LTS
ARM	Linux	CentOS 7 Kylin V10

Inventory

BareMetal2Chassis inventory

Name	Description	Optional	Starting Version
uuid	The UUID of the bare metal chassis.		4.0.0
name	The name of the bare metal chassis.		4.0.0
description	The detailed description of the bare metal chassis.		4.0.0
zoneUuid	The zone UUID.		4.0.0
clusterUuid	The cluster UUID.		4.0.0
chassisOfferingUuid	The chassis offering UUID.		4.0.0
type	The type of the chassis.		4.0.0
state	The state of the chassis.		4.0.0
status	The distribution state of the chassis.		4.0.0
groupBy			4.0.0
createDate	The time when the chassis was created.		4.0.0
lastOpDate	The time when the chassis was last modified.		4.0.0
chassisNics			4.0.0
chassisDisks			4.0.0
userTags	The user tags. For more information, see CreateUserTag.	Yes	4.0.0
systemTags	The system tags. For more information, see CreateSystemTag.	Yes	4.0.0

Sample

{
    "inventories": [
        {
            "chassisDisks": [
                {
                    "chassisUuid": "8c946b89af8349b4bdadebb4ebb717c1",
                    "createDate": "Dec 3, 2020 2:32:17 PM",
                    "diskSize": 2000398934016,
                    "lastOpDate": "Dec 3, 2020 2:32:17 PM",
                    "type": "HDD",
                    "uuid": "a7013135c6b84f6097773a08a04f8180"
                },
                {
                    "chassisUuid": "8c946b89af8349b4bdadebb4ebb717c1",
                    "createDate": "Dec 3, 2020 2:32:17 PM",
                    "diskSize": 250059350016,
                    "lastOpDate": "Dec 3, 2020 2:32:17 PM",
                    "type": "SSD",
                    "uuid": "cdc8f86613c247719c1ed4118b5bfb7f"
                }
            ],
            "chassisNics": [
                {
                    "chassisUuid": "8c946b89af8349b4bdadebb4ebb717c1",
                    "createDate": "Dec 3, 2020 2:32:17 PM",
                    "isProvisionNic": true,
                    "lastOpDate": "Dec 3, 2020 2:32:17 PM",
                    "mac": "ac:1f:6b:e4:65:58",
                    "speed": "1000Mb/s",
                    "uuid": "dee0fbca929f4c749b54e0c78c98d858"
                },
                {
                    "chassisUuid": "8c946b89af8349b4bdadebb4ebb717c1",
                    "createDate": "Dec 3, 2020 2:32:17 PM",
                    "isProvisionNic": false,
                    "lastOpDate": "Dec 3, 2020 2:32:17 PM",
                    "mac": "ac:1f:6b:e4:65:59",
                    "speed": "1000Mb/s",
                    "uuid": "e00ac88d4e2846738311a3211a771e68"
                }
            ],
            "chassisOffering": {
                "architecture": "x86_64",
                "cpuModelName": "Intel(R) Xeon(R) Silver 4208 CPU @ 2.10GHz",
                "cpuNum": 16,
                "createDate": "Dec 1, 2020 8:46:17 PM",
                "lastOpDate": "Dec 1, 2020 8:46:17 PM",
                "memorySize": 67132342272,
                "name": "Intel(R) Xeon(R) Silver 4208 CPU @ 2.10GHz",
                "state": "Enabled",
                "uuid": "9d83b93efc564a4193a7917f35956b59"
            },
            "chassisOfferingUuid": "9d83b93efc564a4193a7917f35956b59",
            "clusterUuid": "d746f7256a734a34b9c85cc83b02e2a2",
            "createDate": "Dec 1, 2020 8:35:23 PM",
            "ipmiAddress": "172.19.40.11",
            "ipmiPort": 623,
            "ipmiUsername": "admin",
            "lastOpDate": "Dec 7, 2020 7:50:37 AM",
            "name": "BM",
            "powerStatus": "POWER_ON",
            "state": "Enabled",
            "status": "Allocated",
            "type": "IPMI",
            "uuid": "8c946b89af8349b4bdadebb4ebb717c1",
            "zoneUuid": "9ebbda92b5264a38b3d992a45fa14818"
        }
    ],
    "success": true
}

BareMetal2ChassisOffering inventory

Name	Description	Optional	Starting Version
uuid	The UUID of the bare metal chassis offering.		4.0.0
name	The name of the bare metal chassis offering.		4.0.0
description	The detailed description of the bare metal chassis offering.		4.0.0
groupBy			4.0.0
architecture	The CPU architecture.		4.0.0
cpuModelName	The CPU model name.		4.0.0
cpuNum	The number of CPU cores.		4.0.0
memorySize	The memory size.		4.0.0
bootMode	The boot mode.		4.0.0
state	The state of the chassis offering.		4.0.0
createDate	The time when the chassis offering was created.		4.0.0
lastOpDate	The time when the chassis offering was last modified.		4.0.0
userTags	The user tags. For more information, see CreateUserTag.	Yes	4.0.0
systemTags	The system tags. For more information, see CreateSystemTag.	Yes	4.0.0

Sample

{
  "inventories": [
    {
      "uuid": "f64db447a42a4673a5b2a6aa6476725e",
      "name": "BM-8C-8G",
      "description": "This is bare metal instance offering.",
      "architecture": "x86_64",
      "cpuModelName": "Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz",
      "cpuNum": 8.0,
      "memorySize": 8.589934592E9,
      "bootMode": "UEFI",
      "state": "Enabled",
      "createDate": "Nov 14, 2017 10:20:57 PM",
      "lastOpDate": "Nov 14, 2017 10:20:57 PM"
    }
  ]
}

BareMetal2ChassisGateway Inventory

Name	Description	Optional	Starting Version
attachedClusterUuids	The attached cluster UUIDs.		4.0.0
username	The username of the gateway.		4.0.0
sshPort	The SSH port.		4.0.0
zoneUuid	The zone UUID.		4.0.0
name	The name of the gateway.		4.0.0
uuid	The UUID of the gateway.		4.0.0
clusterUuid	The cluster UUID.		4.0.0
description	The detailed description of the gateway.		4.0.0
managementIp	The IP address of the management node.		4.0.0
hypervisorType	The virtualization type.		4.0.0
state	The state of the gateway.		4.0.0
status	The connection status of the gateway.		4.0.0
totalCpuCapacity	The total processing capacity of CPU.		4.0.0
availableCpuCapacity	The available processing capacity of CPU.		4.0.0
cpuSockets			4.0.0
totalMemoryCapacity	The total memory size.		4.0.0
availableMemoryCapacity	The available memory size.		4.0.0
cpuNum	The number of CPU cores.		4.0.0
createDate	The time when the gateway was created.		4.0.0
lastOpDate	The time when the was gateway last modified.		4.0.0
provisionNic			4.0.0
userTags	The user tags. For more information, see CreateUserTag	Yes	4.0.0
systemTags	The system tags. For more information, see CreateSystemTag	Yes	4.0.0

Sample

{
    "inventories": [
        {
            "attachedClusterUuids": [
                "d746f7256a734a34b9c85cc83b02e2a2"
            ],
            "availableCpuCapacity": 160,
            "availableMemoryCapacity": 66960363520,
            "clusterUuid": "d746f7256a734a34b9c85cc83b02e2a2",
            "cpuNum": 16,
            "cpuSockets": 1,
            "createDate": "Dec 1, 2020 11:27:52 AM",
            "hypervisorType": "baremetal2",
            "lastOpDate": "Dec 7, 2020 2:21:08 PM",
            "managementIp": "172.25.12.75",
            "name": "Gateway",
            "provisionNic": {
                "createDate": "Dec 3, 2020 8:02:51 PM",
                "interfaceName": "zsn0",
                "ip": "10.99.0.1",
                "lastOpDate": "Dec 3, 2020 8:02:51 PM",
                "netmask": "255.255.0.0",
                "networkUuid": "ed0549b43dd442dfaf03102cfb12ac44",
                "uuid": "fec68c7c6cb64f83880a6e775b9bfd4d"
            },
            "sshPort": 22,
            "state": "Enabled",
            "status": "Connected",
            "totalCpuCapacity": 160,
            "totalMemoryCapacity": 66960363520,
            "username": "root",
            "uuid": "fec68c7c6cb64f83880a6e775b9bfd4d",
            "zoneUuid": "9ebbda92b5264a38b3d992a45fa14818"
        }
    ],
    "success": true
}

BareMetal2Instance inventory

Name	Description	Optional	Starting Version
uuid	The bare metal instance UUID.		4.0.0
name	The bare metal instance name.		4.0.0
description	The detailed description of the bare metal instance.	Yes	4.0.0
zoneUuid	The zone UUID.		4.0.0
clusterUuid	The cluster UUID.		4.0.0
chassisUuid	The bare metal chassis UUID.		4.0.0
imageUuid	The image UUID.		4.0.0
platform	The system platform.		4.0.0
state			4.0.0
status			4.0.0
groupBy		Yes	4.0.0
createDate	The time when the bare metal instance was created.		4.0.0
lastOpDate	The time when the bare metal instance was last modified.		4.0.0
userTags	The user tags. For more information, see CreateUserTag	Yes	4.0.0
systemTags	The system tags. For more information, see CreateSystemTag	Yes	4.0.0

Sample

{
    "inventories": [
        {
            "allVolumes": [
                {
                    "actualSize": 43037753344,
                    "createDate": "Dec 3, 2020 2:09:49 PM",
                    "description": "DataVolume-37c7740bc6964b7f88ddb6dfe437dbc1",
                    "deviceId": 1,
                    "diskOfferingUuid": "0ba949fc7cb64ea3a33450b6eeedc268",
                    "format": "qcow2",
                    "installPath": "sharedblock://b1b722a00d9740f6b262ba16a2fd63dd/b3da61e4a1774e428fabae9b64518aa5",
                    "isShareable": false,
                    "lastOpDate": "Dec 4, 2020 10:19:21 AM",
                    "name": "DATA-for-33",
                    "primaryStorageUuid": "b1b722a00d9740f6b262ba16a2fd63dd",
                    "size": 21474836480,
                    "state": "Enabled",
                    "status": "Ready",
                    "type": "Data",
                    "uuid": "2a0f008a60bf460fb6926eea764ccdbd",
                    "vmInstanceUuid": "37c7740bc6964b7f88ddb6dfe437dbc1",
                    "volumeQos": "total=10485760"
                },
                {
                    "actualSize": 252379660288,
                    "createDate": "Dec 3, 2020 2:09:49 PM",
                    "description": "Root volume for VM[uuid:37c7740bc6964b7f88ddb6dfe437dbc1]",
                    "deviceId": 0,
                    "format": "qcow2",
                    "installPath": "sharedblock://b1b722a00d9740f6b262ba16a2fd63dd/476eb00220434c6bb6e04e5f92410b8c",
                    "isShareable": false,
                    "lastOpDate": "Dec 4, 2020 2:44:11 PM",
                    "name": "ROOT-for-33",
                    "primaryStorageUuid": "b1b722a00d9740f6b262ba16a2fd63dd",
                    "rootImageUuid": "3ae080d4a88d4bf796be57c4f78ad26a",
                    "size": 250059350016,
                    "state": "Enabled",
                    "status": "Ready",
                    "type": "Root",
                    "uuid": "f2492b817c294eff829d837552337b89",
                    "vmInstanceUuid": "37c7740bc6964b7f88ddb6dfe437dbc1"
                }
            ],
            "chassisUuid": "8c946b89af8349b4bdadebb4ebb717c1",
            "clusterUuid": "d746f7256a734a34b9c85cc83b02e2a2",
            "cpuNum": 16,
            "cpuSpeed": 0,
            "createDate": "Dec 3, 2020 2:09:49 PM",
            "gatewayAllocatorStrategy": "DefaultGatewayAllocatorStrategy",
            "gatewayUuid": "fec68c7c6cb64f83880a6e775b9bfd4d",
            "hypervisorType": "baremetal2",
            "imageUuid": "3ae080d4a88d4bf796be57c4f78ad26a",
            "lastChassisUuid": "8c946b89af8349b4bdadebb4ebb717c1",
            "lastGatewayUuid": "fec68c7c6cb64f83880a6e775b9bfd4d",
            "lastOpDate": "Dec 7, 2020 2:21:51 PM",
            "memorySize": 67132342272,
            "name": "33",
            "platform": "Linux",
            "provisionNic": {
                "createDate": "Dec 3, 2020 2:11:21 PM",
                "ip": "10.99.0.2",
                "lastOpDate": "Dec 3, 2020 2:11:21 PM",
                "mac": "ac:1f:6b:e4:65:58",
                "netmask": "255.255.0.0",
                "networkUuid": "ed0549b43dd442dfaf03102cfb12ac44",
                "uuid": "37c7740bc6964b7f88ddb6dfe437dbc1"
            },
            "rootVolumeUuid": "f2492b817c294eff829d837552337b89",
            "state": "Running",
            "status": "Connected",
            "type": "baremetal2",
            "uuid": "37c7740bc6964b7f88ddb6dfe437dbc1",
            "vmCdRoms": [],
            "vmNics": [],
            "zoneUuid": "9ebbda92b5264a38b3d992a45fa14818"
        }
    ],
    "success": true
}

allVolumes inventory

Name	Description	Optional	Starting Version
uuid	The resource UUID.		4.0.0
name	The resource name.		4.0.0
description	The resource description.		4.0.0
primaryStorageUuid	The primary storage UUID.		4.0.0
vmInstanceUuid	The VM UUID.		4.0.0
diskOfferingUuid	The disk offering UUID.		4.0.0
rootImageUuid	The root volume image UUID.		4.0.0
installPath	The installation path of the volume on the primary storage.		4.0.0
type	The volume type.		4.0.0
format	The volume format.		4.0.0
size	The volume size.	Yes	4.0.0
actualSize	The actual size of the volume.		4.0.0
deviceId			4.0.0
state	The state of the volume.		4.0.0
status	The status of the volume.		4.0.0
createDate	The creation time.		4.0.0
lastOpDate	The last update time.		4.0.0
isShareable	Indicates whether the volume is sharable.		4.0.0
volumeQos	The volume QoS.		4.0.0

BareMetal2ProvisionNetwork inventory

Name	Description	Optional	Starting Version
uuid	The deployment network UUID.		4.0.0
zoneUuid	The zone UUID.		4.0.0
name	The deployment network name.		4.0.0
description	The detailed description of the deployment network.		4.0.0
dhcpRangeStartIp	The starting IP address that DHCP assigns to a bare metal instance.		4.0.0
dhcpRangeEndIp	The ending IP address that DHCP assigns to a bare metal instance.		4.0.0
dhcpRangeNetmask	The netmask of the IP range from which the DHCP server assigns an IP address to a bare metal instance.		4.0.0
dhcpRangeGateway	The gateway IP address.		4.0.0
dhcpRangeNetworkCidr	The CIDR block.		4.0.0
state	The state of the deployment network.		4.0.0
attachedClusterUuids			4.0.0
createDate	The time when the deployment network was created.		4.0.0
lastOpDate	The time when the deployment network was last modified.		4.0.0
userTags	The user tags. For more information, see CreateUserTag.	Yes	4.0.0
systemTags	The system tags. For more information, see CreateSystemTag.	Yes	4.0.0

Sample

{
    "inventories": [
        {
            "attachedClusterUuids": [
                "d746f7256a734a34b9c85cc83b02e2a2"
            ],
            "createDate": "Dec 1, 2020 11:03:45 AM",
            "dhcpInterface": "zsn0",
            "dhcpRangeEndIp": "10.99.255.254",
            "dhcpRangeNetmask": "255.255.0.0",
            "dhcpRangeNetworkCidr": "10.99.0.1/16",
            "dhcpRangeStartIp": "10.99.0.1",
            "lastOpDate": "Dec 1, 2020 11:03:45 AM",
            "name": "provision-net",
            "state": "Enabled",
            "uuid": "ed0549b43dd442dfaf03102cfb12ac44",
            "zoneUuid": "9ebbda92b5264a38b3d992a45fa14818"
        }
    ],
    "success": true
}

BareMetal2Gateway inventory

Name	Description	Optional	Starting Version
username	The username of the gateway.		4.0.0
password	The password of the gateway.		4.0.0
sshPort	The SSH port of the gateway.	Yes	4.0.0
name	The name of the gateway.		4.0.0
description	The detailed description of the gateway.	Yes	4.0.0
managementIp	The IP address of the management node.		4.0.0
clusterUuid	The cluster UUID.		4.0.0
resourceUuid	The UUID of the gateway.	Yes	4.0.0
tagUuids	The tag UUIDs.	Yes	4.0.0
userTags	The user tags. For more information, see CreateUserTag.	Yes	4.0.0
systemTags	The system tags. For more information, see CreateSystemTag.	Yes	4.0.0
timeout		Yes

Sample

{
    "inventories": [
        {
            "attachedClusterUuids": [
                "c12275b4a10e48f8ae922eccd8c0a879"
            ],
            "availableCpuCapacity": 160,
            "availableMemoryCapacity": 66960363520,
            "clusterUuid": "c12275b4a10e48f8ae922eccd8c0a879",
            "cpuNum": 16,
            "cpuSockets": 1,
            "createDate": "Dec 31, 2020 10:45:28 AM",
            "description": "172.25.15.81",
            "hypervisorType": "baremetal2",
            "lastOpDate": "Jan 8, 2021 11:24:06 AM",
            "managementIp": "172.25.15.81",
            "name": "172.25.15.81",
            "sshPort": 22,
            "state": "Enabled",
            "status": "Connected",
            "totalCpuCapacity": 160,
            "totalMemoryCapacity": 66960363520,
            "username": "root",
            "uuid": "cd2ac02c1aa948ecbc1f0388f3db0a83",
            "zoneUuid": "8cb18c3afe5242d68dba74d5b65590cb"
        }
    ],
    "success": true
}