• Bare Metal Server

bms
  1. Help Center
  2. Bare Metal Server
  3. User Guide
  4. Instance
  5. Creating a BMS
  6. Creating a BMS

Creating a BMS

Scenarios

This section describes how to create a BMS to deploy your services.

Prerequisites

Procedure

  1. Log in to the management console.
  2. Under Computing, click Bare Metal Server.

    The BMS console is displayed.

  3. Click Allocate BMS.
  4. Select a region.

    ECSs in different regions cannot communicate with each other over an intranet. You are advised to select the region closest to your services to lower the network delay and improve the access speed. Note that after a BMS is obtained, its region cannot be changed.

  5. Select an AZ.

    An AZ is a physical region where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network.

    • It is recommended that you apply for BMSs in different AZs to ensure high availability of applications running on the BMSs.
    • To lower the network delay, create BMSs in the same AZ.
  6. Set Flavor.

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

    Extended Configuration provides the NIC information of the selected flavor. For example, 2 x 2*10GE indicates that a 10GE NIC with two ports connects to the VPC network and a 10GE extended NIC with two ports supports high-speed interconnection between BMSs.

    NOTE:
    • Configuration in the flavor, such as CPUs, memory, and local disks, cannot be changed.
    • The bandwidth of different BMS flavors varies. Choose a flavor that meets your requirements.
    • Some flavors support quick BMS provisioning. If you select a flavor of this type, parameter System Disk is displayed under Disk. The OS of this type of BMS is installed on an EVS disk.
  7. Set Image.
    • Public Image

      A public image is a common standard OS image that is available to all users. It contains an OS and pre-installed public applications, such as the SDI iNIC driver, bms-network-config (a network configuration program), and Cloud-Init (an initialization tool). You can configure the applications and software in a public image as needed.

    • Private Image

      A private image is an image available only to the user who created it using an external image file or a BMS. It contains an OS, preinstalled public applications, and the user's private applications. Using a private image to create BMSs removes the need to configure multiple BMSs repeatedly.

    • Shared Image

      A shared image is a private image shared by another public cloud user with you.

  8. Set License Type.

    Set a license type for using an OS or software on the cloud platform. This parameter is available only if the image you selected is charged.

    • Use license from the system

      Allows you to use the license provided by the 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.

  9. Set Disk.

    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 enable sharing for each data disk.

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

    When you use VPC for the first time, the system automatically creates a VPC for you, including the security group and NIC. The default subnet segment is 192.168.1.0/24 and the subnet gateway is 192.168.1.1. Dynamic Host Configuration Protocol (DHCP) is enabled for the subnet.

    Table 1 Network parameters

    Parameter

    Description

    VPC

    You can select an existing VPC or create one.

    NIC

    Includes primary and extension NICs. You can add an extension NIC to a BMS and specify an IP address for it (including primary NIC).

    NOTICE:
    • The active NIC cannot be deleted because it is used to provide the default route.
    • If you choose to assign an IP address automatically, do not change the private IP address of the BMS after the BMS is provisioned. Otherwise, the IP address may conflict with that of another BMS.
    • If a fixed IP address is assigned to a NIC, you cannot create BMSs in a batch.

    High-Speed NIC

    The high-speed NIC provides high-speed network ports for communication between BMSs. It provides high bandwidth.

    You cannot configure the same high-speed network for multiple high-speed NICs of a BMS.

    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 creating a BMS, you can select only one security group. After a BMS is created, you can associate it with multiple security groups. For details, see Changing a Security Group.

    NOTE:

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

    • Protocol: TCP
    • Port Range: 80
    • Remote End: 169.254.0.0/16

    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: 0.0.0.0/16

    EIP

    An EIP is a static public IP address bound to a BMS in a VPC. Using the EIP, the BMS provides services externally.

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

    • Do not use: The BMS 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 with a dedicated bandwidth to the BMS. The bandwidth is configurable.
    • Specify: An existing EIP is assigned to the BMS.
    NOTE:

    If you select Specify, you can buy only one BMS at a time.

    Bandwidth

    This parameter is required when you select Automatically assign for EIP.

    Specifies the bandwidth size in Mbit/s.

  11. 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 one.

    NOTE:

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

  12. (Optional) Configure Advanced Settings.

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

    • User Data Injection 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.

      This parameter is available only when Key pair is selected for Login Mode. For detailed operations, see Injecting User Data into BMSs.

    • Tag

      Tags a BMS. This configuration is optional. Adding tags to BMSs helps you better identify and manage your BMSs. You can add up to nine tags to a BMS.

      For detailed operations on tags, see section Adding Tags.

    • Agency

      An agency provides BMSs with temporary security credentials for accessing other cloud services. The agency is created by the tenant administrator on the IAM console.

      If you have created an agency in IAM, you can select the agency from the drop-down list and obtain specified operation permissions. Currently, agencies are mainly used for server monitoring. For more information, see Installing and Configuring Agent.

  13. Set BMS Name.

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

    If you create multiple BMSs at a time, suffixes will be added to the BMSs in sequence, such as bms-0001 and bms-0002. If you create multiple BMSs again, the values in the new BMS names increase from the existing maximum value. For example, the existing BMS with the maximum number in name is bms-0010. If you enter bms, the names of the new BMSs will be bms-0011, bms-0012, .... When the value reaches 9999, it will start from 0001 again.

  14. Set your desired number of BMSs, which can be 24 at most.

    After the configuration, click Price Calculator to view the BMS configuration fee.

    NOTE:
    • If the quota is sufficient, you can create a maximum of 24 BMSs. If the quota is less than 24, you can create a maximum of all available BMSs.
    • If you manually set an IP address for the user-defined NICs or high-speed NIC, or specify an EIP, you can create only one BMS at a time.
  15. Click Allocate Now.
  16. 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.

    NOTE:

    You can view the BMS creation status. For details, see Viewing BMS Creation Statuses.

Follow-up Operations