检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
For details about how to expand the disk capacity, see Expansion Overview in Elastic Volume Service User Guide. The system disk capacity of a Windows BMS that is quickly provisioned cannot be expanded. If you need to expand the capacity, contact technical support.
For the native OpenStack APIs not provided in this document (such as the API used to attach EVS disks to a BMS), use the native OpenStack APIs of ECS. For details, see Elastic Cloud Server API Reference. To support function extension, Nova APIs can be distinguished by version.
Upload the CentOS 7.5 kernel file downloaded from the official website to the BMS and run the following command to update the kernel: yum install kernel-3.10.0-862.el7.x86_64.rpm If you have configured automatic EVS disk attaching to the BMS in /etc/fstab, comment out the corresponding
SDI iNIC frontend driver plug-in This plug-in is installed in the image so that EVS disks can be attached to BMSs. In this way, BMSs can be booted from EVS disks, facilitating quick BMS provisioning.
A BMS can boot from a local disk or an EVS disk. Quickly provisioned BMSs boot from an EVS disk.
How Do I Handle a Network Failure After Services Are Switched from a Windows BMS Booted from an EVS Disk to an HA BMS?
A task involves several sub-tasks, such as creating a BMS resource, binding an EIP, and attaching an EVS disk. The task status may be either Creating or Failed: Processing: The system is processing the task. Failed: The system has failed to process the task.
Public services, such as Elastic Cloud Server (ECS), Elastic Volume Service (EVS), Object Storage Service (OBS), Virtual Private Cloud (VPC), Elastic IP (EIP), and Image Management Service (IMS), are shared within the same region.
OS official websites 2 SDI driver With the SDI driver, EVS disks can be attached to BMSs. The EVS disks can be used as system disks from which the BMSs are booted. This facilitates quick BMS provisioning.
Monitor resource usage and evaluate whether the current configuration is more than you need, for example, you can monitor the usage of CPUs, memory, EVS disks, and bandwidth. Detect idle resources to avoid waste, for example, there may be unattached EVS disks or unbound EIPs.
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.
For details, see Expanding the Capacity of an EVS Disk. After the disk capacity has been expanded, the additional disk space needs to be allocated to an existing partition or a new partition.
To increase the partition size to 140 GB, perform the following operations: On the EVS console, add 100 GB capacity to the disk. After the capacity expansion, check that the size of system disk /dev/sdf has been increased from 40 GB to 140 GB.
LocalDisk: local disk Volume: EVS disk (quick provisioning) capabilities:board_type String Specifies the type of a BMS flavor in the format of flavor abbreviation.
Resource identifier Regional Each resource identifier (such as instance ID, EVS disk ID, and VPC ID) is associated with a region and can be used only in the region where the resource is created.
Otherwise, resources, such as CPUs, memory, and EVS disks, will be automatically released, and data will be lost and cannot be restored. If you renew the BMS before it expires, resources will be retained and you can continue using the BMS.
Setting the Same Renewal Day for Yearly/Monthly Resources If the BMSs have different expiry dates or the BMSs and attached EVS disks have different expiry dates, you can set the same renewal day, for example, the first day of each month, to make it easier to manage renewals.
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.
If the BMS uses SDI storage cards (neither SDI 2.2 nor SDI 3.0), the SDI driver needs to be installed on the VM so that EVS disks can be attached to the BMS. In other cases, skip this section. Currently, ARM 64 VMs do not support SDI cards.
Constraints Currently, only a BMS that supports quick provisioning (the OS is installed on an EVS disk) can be used to create a private image. Data disks of a BMS cannot be exported as images. The BMS must be stopped.
