Help Center/ Bare Metal Server/ User Guide/ Instance/ Creating a BMS/ Creating a Common BMS
Updated on 2024-10-11 GMT+08:00
View PDF
Share

Creating a Common 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 Buy BMS.

    The page for you to purchase a BMS is displayed.

  4. In the Current Configuration area on the right pane, confirm the billing mode. Currently, only the Yearly/Monthly billing mode is supported.

    Yearly/Monthly is a prepaid billing mode in which your BMS is billed based on the service duration. This cost-effective mode is ideal when the duration of BMS usage is predictable.

  5. Confirm Region.

    If the region is incorrect, click in the upper left corner of the page to correct it.

  6. 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 create 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.
  7. Select a flavor.

    Flavor contains the 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 the BMS has two 10GE NICs, each with two ports. One NIC is used for the BMS to connect to a VPC and the other is used for the BMS to communicate with other BMSs in a high-speed network.

    • Configuration in the flavor, such as the CPU, 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 will be installed on the EVS disk attached to the BMS.
  8. Set Image.
    • Public Image

      A public image is a standard OS image provided by the system and 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). If you need other applications or software, configure them on the new BMSs.

    • Private Image

      A private image is created from an external image file or a BMS and is available only to the user who created it. It contains an OS, preinstalled public applications, and the user's private applications.

    • Shared Image

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

  9. Set Disk.

    Disks are classified as EVS disks and DSS disks based on whether the disks use dedicated storage resources. DSS disks provide dedicated storage resources.

    • If you have applied for a storage pool on the DSS console and have obtained the pool, click the DSS tab and create disks in the storage pool.
    • If you have not obtained a dedicated storage pool, click the EVS tab and create EVS disks that use public storage resources.
    • When you use DSS resources to create a disk, the disk type must be the same as that of the requested storage pool. For example, both are of the high I/O type.
    • For details about different disk types, see Disk Types.

    A BMS has one system disk and one or more data disks. You can add multiple data disks for a BMS and customize the system disk size.

    • System disk

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

    • Data disk

      You can add multiple data disks for 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.
    • After a system disk is detached from a BMS charged in yearly/monthly mode, the disk can only be used as a system disk and can only be attached to this BMS.
    • If you detach a non-shared data disk purchased when you buy a BMS charged in yearly/monthly mode and want to attach it again, you can only attach it to the original BMS as a data disk.
    • The non-shared data disk purchased when you buy a BMS charged in yearly/monthly mode does not support separate renewal, unsubscription, automatic service renewal, conversion to pay-per-use payment, or release.
  10. Configure automatic backup.

    After automatic backup is enabled, the system automatically backs up the BMS based on the preset backup policy.

    The automatic backup function applies only to BMSs that support quick provisioning. To enable this function, you must select a flavor that supports quick provisioning in step 7.

    1. Select Enable auto backup.
    2. Configure Backup Policy.

      In the drop-down list, select a backup policy. Alternatively, you can click Manage Backup Policy and set the backup policy on the Cloud Server Backup Service (CSBS) page. If you have not created any backup policy but select Enable auto backup, the system will use the default backup policy shown in Figure 1.

      Figure 1 Default backup policy

    For details about CSBS, see Cloud Backup and Recovery Overview.

  11. 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 for a BMS and specify IP addresses for the primary and extension NICs.

    CAUTION:
    • The primary 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

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

    Each high-speed NIC of a BMS must be in a different high-speed network.

    NOTE:

    In some regions, high-speed networks have been upgraded to enhanced high-speed networks with higher performance.

    Enhanced High-Speed NIC

    A BMS has a maximum of two enhanced high-speed NICs and depends on the total bandwidth of the extension NICs. For example, if the total bandwidth allowed for the extension NICs is 2 x 10GE and the bandwidth of the first enhanced high-speed NIC is 2 x 10GE, you cannot add another enhanced high-speed NIC.

    NOTE:

    You can view the total bandwidth of extension NICs in Extended Configuration.

    • If a flavor's Extended Configuration contains 2*10GE (for example, the Extended Configuration of flavor physical.h2.large is 1*100G IB + 2*10GE), BMSs of this flavor has only one NIC without extension NIC, and the total bandwidth of extension NICs is 0.
    • If a flavor's Extended Configuration contains 2 x 2*10GE (for example, the Extended Configuration of flavor physical.s3.large is 2 x 2*10GE), BMSs of this flavor has two NICs, of which one is an extension NIC, and the total bandwidth of extension NICs is 2*10GE.

    Security Group

    Security groups are used to control access to BMSs. 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.

    Security group rules determine BMS access and usage. For instructions about how to configure a security group rule, see Adding Security Group Rules. Enable the following common protocols and ports as needed:

    • Port 80: used to view web pages by default through HTTP.
    • Port 443: used to view web pages through HTTPS.
    • ICMP: pings BMSs to check their communication statuses.
    • Port 22: reserved for logging in to a Linux BMS using SSH.
    • Port 3389: reserved for logging in to a Windows BMS using SSH.
    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 can access the Internet.

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

    • Automatically assign: The system automatically assigns an EIP with a dedicated bandwidth to the BMS. The bandwidth is configurable.
    • Use existing: An existing EIP is assigned to the BMS.
    • Not required: The BMS cannot communicate with the Internet and can only be used to deploy services or clusters in a private network.
    NOTE:

    If you select Use existing, you can create only one BMS at a time.

    Specifications

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

    • Dynamic BGP: When changes occur on a network using dynamic BGP, network configurations can be promptly adjusted using the specified routing protocol, ensuring network stability and optimal user experience.
    • Static BGP: When changes occur on a network using static BGP, carriers cannot adjust network configurations in real time to ensure optimal user experience.

    Bandwidth Type

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

    • Dedicated: The bandwidth can be used by only one EIP.
    • Shared: The bandwidth can be used by multiple EIPs.
      NOTE:
      • A bandwidth can be shared between a limited number of EIPs. If the number of EIPs cannot meet service requirements, switch to a higher shared bandwidth or apply to expand the EIP quota of the existing bandwidth.
      • EIPs that are charged yearly/monthly do not support shared bandwidths.
      • When a shared bandwidth that is charged yearly/monthly expires, the system automatically deletes the bandwidth and creates an exclusive bandwidth charged by traffic for the EIPs sharing the deleted bandwidth.

    Billed By

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

    • Bandwidth: You specify a maximum bandwidth and pay for the time you use the bandwidth.
    • Traffic: You are charged based on the actual traffic you have used.

    Bandwidth

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

    Specifies the bandwidth size in Mbit/s.
  12. Set the BMS login mode.

    Key pair is recommended because it features higher security than Password. If you select Password, ensure that the password meets complexity requirements described in Table 2 to prevent malicious attacks.

    • Key pair

      A key pair is used for BMS login authentication. You can select an existing key pair, or click Create Key Pair to create one.

      If you use an existing key pair, ensure that you have one.

    • Password

      In this mode, the initial password is used for authentication. You can log in to the BMS using the username and its initial password.

      If the BMS runs Linux, you can use username root and its initial password to log in to the BMS. If the BMS runs Windows, you can use username Administrator and its initial password to log in to the BMS. The passwords must meet the requirements described in Table 2.

      Table 2 Password requirements

      Parameter

      Requirements

      Example Value

      Password
      • Consists of 8 to 26 characters.
      • Must contain at least three of the following character types:
        • Uppercase letters
        • Lowercase letters
        • Digits
        • Special characters !@$%^-_=+[]{}:,./?
      • Cannot contain the username or the username spelled backwards.
      • Cannot contain more than two characters in the same sequence as they appear in the username. (This requirement applies only to Windows BMSs.)

      Test12$@
  13. Configure Enterprise Project.

    This parameter is available only if you have enabled enterprise projects or your account is an enterprise account. To enable this function, contact your customer manager.

    An enterprise project is a cloud resource management mode, in which cloud resources and members are centrally managed by project. The default project is default.

    Select an enterprise project from the drop-down list. For details about enterprise projects, see Enterprise Management User Guide.

  14. (Optional) Configure Advanced Settings.

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

    • (Optional) Tag

      Tagging BMSs helps you better identify and manage your BMSs. You can add up to nine tags to a BMS.

      If your organization has configured tag policies for BMS, you need to add tags to your BMSs based on the tag policies. If you do not follow the policies, BMSs may fail to be created. Contact your organization administrator to learn more about tag policies.

      For detailed operations on tags, see 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. If you have no agency, click Create Agency to create one. Currently, agencies are mainly used for server monitoring. For more information, see Overview.

  15. Set BMS Name.

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

    If you purchase multiple BMSs at a time, suffixes will be added to the BMSs in sequence, such as bms-0001, bms-0002, ... If you purchase 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.

  16. Set Required Duration and Quantity.
    • Required Duration: Set the service duration if you select the Yearly/Monthly billing mode. The service duration ranges from one month to one year.

      BMSs charged in yearly/monthly mode cannot be deleted. They support only resource unsubscription. If you no longer need a BMS, you can unsubscribe from it using either of the following methods:

      • Locate the row that contains the BMS, click More in the Operation column, and select Unsubscribe from the drop-down list. On the Unsubscribe page, select a reason and click Confirm.
      • Choose Billing Center > Orders > Unsubscriptions. Locate the row that contains the BMS and click Unsubscribe from Resource in the Operation column.
    • Quantity: You can purchase BMSs of the remaining quota at a time.

      If you manually set an IP address when configuring NIC or High-Speed NIC or select Use existing when configuring EIP, you can create only one BMS at a time.

  17. Click Buy Now. If you have any question about the price, click Pricing details.

    Confirm the BMS information and click Pay Now.

  18. Pay the fees as prompted and click OK.

    The BMS console is displayed.

  19. Wait for the system to create your requested BMSs.

    The BMS status changes to Running after about 30 minutes. If you select a flavor that supports quick provisioning, you can obtain a BMS within about five minutes.

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

Follow-up Operations

Parent topic: Creating a BMS