High Performance ComputingHigh Performance Computing

Compute
Elastic Cloud Server
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
Domain Name Service
VPC Endpoint
Cloud Connect
Enterprise Switch
Security & Compliance
Anti-DDoS
Web Application Firewall
Host Security Service
Data Encryption Workshop
Database Security Service
Advanced Anti-DDoS
Data Security Center
Container Guard Service
Situation Awareness
Managed Threat Detection
Compass
Cloud Certificate Manager
Anti-DDoS Service
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GaussDB NoSQL
GaussDB(for MySQL)
Distributed Database Middleware
GaussDB(for openGauss)
Developer Services
ServiceStage
Distributed Cache Service
Simple Message Notification
Application Performance Management
Application Operations Management
Blockchain Service
API Gateway
Cloud Performance Test Service
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
DevCloud
ProjectMan
CodeHub
CloudRelease
CloudPipeline
CloudBuild
CloudDeploy
Cloud Communications
Message & SMS
Cloud Ecosystem
Marketplace
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP License Service
Support Plans
Customer Operation Capabilities
Partner Support Plans
Professional Services
enterprise-collaboration
Meeting
IoT
IoT
Intelligent EdgeFabric
DeveloperTools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Updated at: May 09, 2022 GMT+08:00

Creating a BMS Cluster

Scenarios

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

Precautions

Dedicated physical resources

  • To make a BMS run on isolated physical hardware, apply for a Dedicated Cloud (DeC) and then create a BMS.

    For details about DeC and how to apply for DeC, see Dedicated Cloud User Guide.

  • If you want your BMS to exclusively use a storage device, apply for Dedicated Enterprise Storage Service (DESS) after you enable DeC and then create the BMS.

    For details about DESS, see Dedicated Enterprise Storage Service User Guide.

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.

    If you have obtained a DeC and want to deploy your BMS in your DeC, click Provision BMS in DeC.

  4. Confirm Region.

    If the region is incorrect, click in the upper left corner of the page for correction.

  5. 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.

  6. 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.

  7. 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 to Public image and select a desired one from the 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 to Private image and select a desired one from the drop-down list.

    • Shared image

      A shared image is a private image shared by another user.

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

  8. Select 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 the system license

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

    • Bring your own license (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.

    Disks are classified as EVS disks, DSS disks, and DESS disks based on whether the storage resources used by the disks are exclusive. Currently, you can only select one disk type.

    • EVS: provides secure, reliable, and scalable hard disk resources of various flavors to meet performance requirements in different scenarios.

      If you have not applied for an exclusive storage pool, click EVS and create EVS disks that use public storage resources.

    • DSS: provides exclusive storage resources, high availability and durability, and stable and low latency using multiple technologies, such as data redundancy and cache acceleration.

      If you have applied for a storage pool on the DSS page, click DSS and create disks in the obtained storage pool.

    • DESS: provides dedicated storage devices for enterprises to migrate key services (such as Oracle RAC and SAP HANA TDI) to the cloud.

      If you have enabled the Dedicated Enterprise Storage Service (DESS), click DESS and create disks in DESS.

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

    Windows BMSs cannot have disks attached.

    • 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 disk is shared. A shared disk can be attached to multiple BMSs.
    • 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 on-demand payment, and release.
  10. Configure automatic backup.

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

    1. Select Enable.
    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 have selected Enable, the system will use the default backup policy, as shown in Figure 1.

      Figure 1 Default backup policy

    For more information about BMS backup, see Cloud Server Backup Service User Guide.

  11. Set network parameters, including VPC, Security Group, and NIC.
    Table 1 Network parameters

    Parameter

    Description

    VPC

    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 192.168.1.0/24 and the subnet gateway is 192.168.1.1. 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 applying for a BMS.

    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

    NIC

    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 number of two high-speed NICs. You can configure the IP address to be used by the high-speed NIC.

    NOTE:

    If you use a high-speed NIC, you cannot create BMSs in batches.

    EIP

    An elastic IP address (EIP) is a fixed (static) IP address that you have bound to a BMS. The elastic IP address enables resources in a VPC to provide services using a fixed IP address.

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

    • Not required: BMSs cannot communicate with the Internet and are used only as a service deployed in the private network or used in the cluster.
    • Automatically assign: The system automatically assigns an EIP that uses exclusive bandwidth to the BMS. The bandwidth size is configurable.
    • Use existing: An existing elastic IP address is assigned to the BMS.
      NOTE:

      If you use an existing EIP, you cannot create BMSs in batches.

    Specifications

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

    • Dynamic BGP: When changes occur on a network using dynamic BGP, routing protocols provide automatic, real-time optimization of network configurations, 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.

    Billed By

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

    Bandwidth: You specify a maximum bandwidth and pay for the amount of time you use the bandwidth.

    Bandwidth

    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 Create Key Pair and create a desired one.

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

    • Password

      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.

      You cannot select this login mode for Windows BMSs.

      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. (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.

  14. Set BMS Name.

    If you want to buy multiple BMSs at a time, the system automatically sequences these BMSs by adding suffixes to them.

  15. 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: 1 to 24
      • If the quota is sufficient, you can buy a maximum of 24 BMSs. If the quota is less than 24, you can buy a maximum of all available BMSs.
      • 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.
  16. Click Buy Now.

    On the confirmation page, confirm the BMS information and click Pay Now.

    If you have any question about the price, click Pricing details.

  17. Pay the fees as prompted and click OK.

    The BMS console is displayed.

  18. After you pay the order, the system will 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 in about five minutes.

Did you find this page helpful?

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel