Hello, everyone!
Today I will share with you the Bare Metal Server basic concepts.
Basic Concepts
Table 1 Key term lists key terms related to the BMS service.
Table1 Key terms | |
Term | Description |
AZ | An availability zone (AZ) is a physical location where resources use independent power supply and networks within a region. An AZ is insulated from failures in other AZs and provides inexpensive, low-latency network connectivity to other AZs in the same region. A region can have more than one AZ. AZs are physically isolated but interconnected through an internal network. To enhance the availability of the BMS service, deploy the service in different AZs. |
Image | An image must contain an operating system (OS) and can also contain desired software and software configuration. An image is a template for applying for a BMS. Images can be public or private. Public images are provided by the system by default, and private images are manually created by users. You can use images to quickly create BMSs. Currently, you can only use public images to create BMSs. |
Disk | EVS disks can be attached to BMSs. The EVS disks attached to BMSs can be shared disks. If a shared disk is attached to a BMS, the BMS shares this disk with other BMSs. BMSs can use the following types of EVS disks: · Ultra-high I/O Indicates EVS disks that use solid-state disk (SSD) storage. These EVS disks provide ultra-high I/O and low latency and support relational database, NoSQL database, and data warehouse applications. · High I/O Indicates EVS disks that use serial attached SCSI (SAS) storage. These EVS disks provide high I/O and low latency and support relational databases, NoSQL databases, data warehouses, and file system applications. · Common I/O Indicates EVS disks that use Serial Advanced Technology Attachment (SATA) storage. These EVS disks provide reliable block storage and can be used to run key applications. NOTE: The EVS disks attached to BMSs are virtual block storage. The physical hard disks in BMS flavors are local disks. |
VPC | A VPC provides you with a logically isolated network environment for BMSs. You can create virtual networks in a VPC. You can also create security groups and VPNs, configure IP address segments, and specify bandwidth sizes in your VPC. With a VPC, you can manage and configure internal networks and change network configurations, simplifying network management. You can also customize access rules to control ECS access within a security group and across different security groups to enhance BMS security. |
High-speed network | A high-speed network is an internal network among BMSs and provides unlimited bandwidth for connecting BMSs in the same AZ. If you want to deploy services requiring high throughput and low latency, you can create high-speed networks. Currently, the BMS service supports high-speed networks with a maximum bandwidth of 10 Gbit/s. |
EIP | An elastic IP address (EIP) is an independent public IP address. You can bind an EIP to a BMS to enable BMSs in your VPC to be accessible from the Internet through a fixed public IP address. |
Key pair | The local private key file and the public key file stored on the server are used to authenticate BMS login requests. |
Access and Use
The cloud platform provides a web-based ServiceCenter tenant portal and HTTPS-based APIs through which you can access BMS.
· The ServiceCenter tenant portal is a web-based management console for you access and manage BMS.
You can access BMS on this portal. If you are a CloudOpera ServiceCenter resource administrator or have the BMS operation rights, you can directly log in to the ServiceCenter tenant portal and choose Bare Metal Server under the Product or Console menu.
· Accessing BMS through APIs
If you want to integrate BMS into a third-party system for secondary development, you can access BMS using APIs. For details, see section FusionSphere Service API Reference > Bare Metal Server API Reference in the FusionCloud V100R006C10 API ReferenceBare Metal Server API Reference.
That's all, thanks!
