• Bare Metal Server

  1. Help Center
  2. Bare Metal Server
  3. User Guide
  4. Getting Started
  5. Allocating a BMS

Allocating a BMS


This section describes how to allocate a BMS so that you can deploy your services on it.


  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Computing, click Bare Metal Server.

    The BMS console is displayed.

  4. Click Allocate BMS.
  5. Select the region.

    You are advised to select the region closest to your customer to reduce the access delay and improve the download speed.

  6. Set AZ.

    An AZ is a physical region where power and networks are physically isolated. AZs in the same region can communicate with each other over an intranet. It is recommended that you apply for BMSs in different AZs to ensure high availability of applications running on the BMSs.

  7. Set Flavor.

    The flavor contains the CPU, memory, local disks, and extended configuration of the BMS. After you select a flavor, the name, networking, and use scenarios of the flavor are displayed under the flavor list.


    Configuration in the flavor, such as memory and local disks, cannot be changed.

  8. Set Image.
    • Public Image

      A public image is a standard, widely used image. It contains an OS and preinstalled public applications and is available to all users.

      To select a public image, set Image Type to Public Image and choose a desired one from the Image drop-down lists.

    • Private Image

      A private image is an image available only to the user who created it using an external image. It contains an OS, SDI card driver, bms-network-config network configuration program, Cloud-Init, and users' private applications.

      To select a private image, set Image Type to Private Image and choose a desired one from the Image drop-down list.

    • Shared Image

      A shared image is an image shared by other users and can be used as your own private images.

      To select a shared image, click the Shared Image tab and select a desired one from the Image drop-down list.

  9. Select License Type.

    Specifies a license type for using an OS or software on the cloud platform. If the image you selected is free of charge, this parameter is unavailable. If the image you selected is charged, this parameter is available.

    • Use the license from the system

      Allows you to use the license provided by the public cloud platform. Obtaining the authorization of such a license is charged.

    • Bring your own licenses (BYOL)

      Allows you to use your existing OS license. In such a case, you do not need to apply for a license again.

  10. Set Storage.

    A disk can be a system or data disk. You can add multiple data disks to a BMS and customize the system disk size.

    • System disk

      If you select a flavor that supports quick provisioning, the system disk is available. You can set the disk type and size as needed.

    • Data disk

      You can add multiple data disks to a BMS and configure sharing for each data disk.

      • Currently, BMSs only support SCSI disks.
      • Share: indicates that the EVS disk is shared. A shared disk can be attached to multiple BMSs.
  11. Set network parameters, including VPC, Security Group, and NIC.
    Table 1 Network parameters




    If you do not have a VPC configured when creating a BMS for the first time, the system creates the default VPC, subnet, and security group for you. The default subnet segment is and the subnet gateway is Dynamic Host Configuration Protocol (DHCP) is enabled for the subnet.

    If the default VPC cannot meet your network requirements, click View VPC to create a VPC.

    Security Group

    A security group implements access control for BMSs within a security group and between different security groups. You can define different access control rules for a security group, and these rules take effect for all BMSs added to this security group. When allocating a BMS, you can select the security group to which it belongs. You can select only one security group when creating a BMS.

    Security group rules determine BMS access and usage. For instructions about how to configure a security group rule, see section Configuring the Security Group.


    Before initializing a BMS, ensure that security group rules in the outbound direction meet the following requirements:

    • Protocol: TCP
    • Port Range: 80
    • Remote End:

    If you use the default outbound security group rule, the preceding requirements are met, and the BMS can be initialized. The default outbound security group rule is as follows:

    • Protocol: Any
    • Port Range: Any
    • Remote End:


    Specifies the BMS NIC. The system provides a primary NIC by default. You can specify the IP address to use for the primary NIC in your VPC. You can add extended NICs to the BMS.

    High-Speed NIC

    Specifies the NIC that is assigned an IP address from the high-speed network segment. A high-speed NIC provides higher bandwidth for a BMS. A BMS can have a maximum of two high-speed NICs. You can configure the IP address to be used by the high-speed NIC.


    Specifies the EIP. You can bind an EIP to a BMS so that the BMS can provide services through this IP address.

    You can select one of the following three options for EIP as required:

    • Do Not Use: BMSs cannot communicate with the Internet and can be used only on a private network for deploying services or used to deploy a cluster.
    • Automatically Assign: The system automatically assigns an EIP that uses a dedicated bandwidth to the BMS. The bandwidth is configurable.
    • Specify: An existing EIP is assigned to the BMS.


    This parameter is mandatory when EIP is set to Automatically Assign.

    Specifies the bandwidth size in Mbit/s.

  12. Set the BMS login mode.

    Key pair: A key pair is used for BMS login authentication. You can select an existing key pair, or click View Key Pair and create a desired one.


    If you use an existing key pair, ensure that you have saved the key file locally. Otherwise, logging in to the BMS will fail.

  13. (Optional) Configure Advanced Settings.

    To use functions listed in Advanced Settings, select Configure now. Otherwise, select Do not configure.

    • User Data Injection

      This configuration is optional and enables the BMS to automatically inject user data when the BMS starts for the first time. After this function is enabled, the BMS automatically injects the user data upon its first startup. For detailed operations, see section (Optional) Injecting User Data into BMSs.

    • Agency Name

      This parameter is optional. An agency is created by the tenant administrator in IAM and provides a temporary credential for a BMS to access cloud services. If you have created an agency in IAM, you can select the agency name from the drop-down list and obtain specified operation permissions.

  14. Set BMS Name.

    The name can be customized but can contain only letters, digits, underscores (_), hyphens (-), and periods (.).

    If you want to allocate multiple BMSs at a time, the system automatically adds suffixes to these BMSs in sequence.

  15. Set Quantity. You can allocate a maximum of 24 BMSs at a time.

    If the quota is sufficient, you can allocate a maximum of 24 BMSs at a time. If the remaining quota is less than 24, you can allocate BMSs of the remaining quota at a time.

    If you manually set IP addresses for NICs, including the primary NIC, extension NIC, and high-performance NIC, or manually specify an EIP, you can allocate only one BMS at a time.

  16. Click Allocate Now.
  17. On the displayed page, confirm the specifications and click Submit.

The BMS status changes to Running after about 30 minutes.


If you select a flavor that supports quick provisioning, you can obtain a BMS in about five minutes.

After the requested BMS is provisioned, you can change the password validity period by following the instructions in section How Do I Set the Password Validity Period? to prevent any convenience that may rise due to password expiry.