检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
SATA: common I/O EVS disk SAS: high I/O EVS disk GPSSD: general-purpose SSD EVS disk SSD: ultra-high I/O EVS disk ESSD: Extreme SSD GPSSD2.storage: General-purpose SSD V2 storage GPSSD2.iops: General-purpose SSD V2 iops GPSSD2.throughput: General-purpose SSD V2 throughput region
Apply for a valid token or check the project ID in the URL. 400 Ecs.0025 EVS is not authorized to obtain KMS keys for encrypting EVS disks. EVS is not authorized to obtain KMS keys for encrypting EVS disks.
Allowed creation of subdirectories for PVs that are dynamically provisioned from SFS Turbo file systems. - Fixed some security issues. v1.27.8-r0 v1.27.4 Supported EVS volumes. Allowed namespaces or workloads to have security groups and subnets bound.
Allowed creation of subdirectories for PVs that are dynamically provisioned from SFS Turbo file systems. - Fixed some security issues. v1.27.8-r0 v1.27.4 Supported EVS volumes. Allowed namespaces or workloads to have security groups and subnets bound.
Constraints EVS volumes created using flexVolume can only be deleted when the pods are in the Terminated state. When the pod status is Completed, the EVS volumes created using this field will not be deleted.
After a data disk image is imported, you can use it to create EVS disks. The following figure shows the process of importing a data disk image.
evs:types:get Project-level service VPC vpc:ports:create vpc:ports:update vpc:securityGroups:get vpc:publicIps:list vpc:ports:get vpc:subnets:get vpc:vpcs:list √ √ Binding an EIP POST /v1.0/{project_id}/graphs/{graph_id}/action?
Optimizing costs Medium evs:::volume N/A RGC-GR_CONFIG_VOLUME_UNUSED_CHECK Checks whether an EVS disk is attached to a cloud server. This policy is non-compliant if the disk is not attached.
The cloud storage type can be EVS or SFS. If no cloud storage is available, click Create PVC. If you select EVS, the AZ of the EVS disk must be the same as that of the node.
CCE does not support EVS disks of the ReadWriteMany type. If resources of this type exist in the source cluster, change the storage type to ReadWriteOnce.
You have attached the EVS disk to the BMS and the additional disk space remains to be allocated. Context The OS used in the following example is Windows Server 2008 R2 Enterprise. The following example is for reference only.
Pay-per-Use Resources If a pay-per-use cluster that contains pay-per-use public network bandwidth and EVS disks is no longer required, delete the cluster. The unsubscription procedure is as follows: Log in to the CSS management console.
You have attached the EVS disk to the BMS and the additional disk space remains to be allocated. Context The OS used in the following example is Windows Server 2008 R2 Enterprise. The following example is for reference only.
Changing the Billing Mode of a Node The billing modes of resources like EVS disks and EIPs used by pay-per-use nodes cannot be changed simultaneously. For details, see Pay-per-Use to Yearly/Monthly.
Pod Storage Space If no EVS disk or other cloud storage is mounted, the application data is stored in the physical disks of the container. Each pod can be allocated with a maximum of 20 GB disk space (both the CPU host and the GPU host).
Such resources, which are created either manually or automatically during cluster creation, include ECSs, EVS disks, EIPs, bandwidth, and load balancers. For more pricing details, see Product Pricing Details.
Such resources, which are created either manually or automatically during cluster creation, include ECSs, EVS disks, EIPs, bandwidth, and load balancers. For more pricing details, see Product Pricing Details.
deleteServerV2 deleteServerV21 deleteVmByNative Starting an ECS ecs startServer Restarting an ECS ecs rebootServer Stopping an ECS ecs stopServer Adding an ECS NIC ecs addNic Deleting an ECS NIC ecs deleteNic delNic Attaching a disk ecs attachVolume attachVolumeV2 Attaching a disk (on the EVS
If the instance has an EVS disk attached, the storage space will still be billed. Deleting an Instance Delete the notebook instances that are not needed. Log in to the ModelArts console. In the navigation pane on the left, choose Development Workspace > Notebook.
In addition, EVS requires that disk capacity be expanded in increments of 1 GB. Therefore, the paired target server disk must be at least 1 GB larger than the source GPT disk.