Function Overview

An instance is a purchased BMS. Different instance types provide varied computing capabilities, storage space, and network performance. You can select a type that meets your service requirements. After you purchase a BMS, you can perform operations such as starting, stopping, and in-band monitoring.

You can:

• Creating a Common BMS
• Creating a BMS Supporting Quick Provisioning
• Creating a Dedicated BMS
• Creating a BMS from a Private Image

BMS network types include:

• EIP
• VPC
  

Billing Items
The billing items include BMS, EVS disk (optional), and EIP (optional).

Billing Modes
BMSs are billed on a yearly/monthly basis and cannot be billed on a pay-per-use basis. You can buy 10 months and get two free. If you intend to use BMSs for a long term, you can save more by specifying a longer duration.

Billing Involved in Specifications Changes
If you require additional storage space, you can either expand the capacity of EVS disks that are attached to a BMS or attach more EVS disks to the BMS. The additional storage space will be billed in a pay-per-use or yearly/monthly basis depending on the billing modes you specified for the EVS disks.

An image is a template of the BMS running environment. It contains an OS and runtime environment, and some pre-installed applications. An image file is equivalent to a copy file that contains all data in the system disk.Images can be classified into public images, private images, and shared images.

Public Images
Public images are provided by HUAWEI CLOUD. These images are available to all users, compatible with BMSs and most mainstream OSs, and are pre-installed with necessary plug-ins.

Private Images
A private image contains an OS, preinstalled public applications, and a user's private applications. You can use a private image to create BMSs without having to repeatedly configure them.

Shared Images
A shared image is a private image other users share with you.

EVS offers scalable block storage for BMSs. EVS disks feature high reliability, high performance, and rich specifications, and are ideal for distributed file systems, development and test environments, data warehouse applications, and high-performance computing (HPC) scenarios.The key indicators of EVS disk performance include read/write latency, IOPS, and throughput.

IOPS: number of read/write operations performed by an EVS disk per second.

Throughput: amount of data successfully transmitted by an EVS disk per second, that is, the amount of data read from and written into an EVS disk.

Read/write latency: minimum interval between two consecutive read/write operations of an EVS disk.

To ensure system security, you are advised to use the key authentication mode to authorize the user who attempts to log in to a BMS. Therefore, you must use an existing key pair or create a new one for remote login authentication.

Creating a Key Pair
If no key pair is available, create one that contains a public and a private key used for login authentication. You can use either of the following methods:

Create a key pair using the management console. After the creation, the public key is automatically stored in the system, and the private key is manually stored in a local directory. For details, see Create a Key Pair on the Management Console.
Use PuTTYgen to create a key pair, and save both the public and private keys to the local host. For details, see Create a Key Pair Using PuTTYgen. After the creation, import the key pair by following the instructions provided in Import a Key Pair. Then, the key pair can be used.

Using an existing key pair
If a key pair is available locally, for example, generated using PuTTYgen, you can import the public key on the management console so that the system maintains the public key file. For details, see Import a Key Pair.

Quotas are enforced for service resources on the platform to prevent unforeseen spikes in resource usage. Quotas can limit the number or amount of resources available to users, such as the maximum number of BMSs or EVS disks that can be created.

If the existing resource quota cannot meet your service requirements, you can apply for a higher quota.

Tags are used to identify cloud resources, such as instances, images, and disks. If you have multiple types of cloud resources which are associated with each other, you can add tags to the resources to classify and manage them easily. For more information, see Overview.

You can add tags to a BMS in either of the following ways:

• Add Tags During BMS Creation
• Add Tags on the BMS Details Page

Server monitoring provided by Cloud Eye includes basic monitoring and OS monitoring. Basic monitoring refers to monitoring of ECS metrics automatically reported (BMS does not support basic monitoring). OS monitoring provides system-wide, active, and fine-grained (10-second interval) monitoring for BMSs, on which Agent is installed. Agent occupies less than 1.5% CPU and less than 50 MB memory of the OS.

To meet the basic monitoring and O&M requirements for servers, Server Monitoring monitors more than 40 metrics, such as CPU, memory, disk, and network metrics.

ou can apply for a higher quota.

Native OpenStack APIs and BMS APIs are provided.

A combination of the two types of APIs allows you to use all functions provided by the BMS service. For example, you can create a BMS using a native OpenStack API or a BMS API.