Constraints

Updated on 2024-05-20 GMT+08:00

View PDF

The following are constraints and limitations of CloudPond and its functions. For details about restrictions on parameter settings, see corresponding sections in the CloudPond User Guide.

General Constraints

Management mode: You can use only the CloudPond console to manage locations, edge sites, and cloud resources used at edge sites.
Hardware restrictions: User devices cannot be installed in CloudPond racks.
O&M and monitoring: O&M and monitoring are completed by the Huawei Cloud O&M team. You can use Cloud Eye to monitor cloud resources but cannot access the O&M and monitoring platforms.
Hardware types and resource usage restrictions: Hardware devices used to provide EVS services at an edge site include converged models (converged nodes provide EVS services and cloud platform O&M management and control component services) and storage models (storage nodes provide EVS services for you). Up to four converged nodes can be deployed at an edge site.
Hardware devices used to provide ECS services at an edge site include virtualization models and bare metal models based on ECS flavors. Except for necessary management overheads, all resources on the hardware devices are provided for service running.

Compute and storage resources are separated. You can expand compute or storage resources as needed (except for local disks provided by D/I series ECSs)

Core Cloud Services

Table 1 describes the constraints on running ECS, EVS, VPC, and EIP at an edge site.

**Table 1** Constraints on core cloud services at edge sites
Cloud Service	Constraint
ECS	ECSs do not support Virtual Network Console (VNC) login. Log in to the ECSs using SSH (Linux) or mstsc (Windows). An annual license is required for each graphics card used by a GPU-accelerated PI2 ECS. ECSs cannot be encrypted, backed up, or used for creating full-ECS images, and their billing modes cannot be changed. To run commercial OSs on an ECS, such as Windows and Red Hat, you need to acquire the license. ECS supports the UEFI secure boot of local VMs. By default, this feature can be enabled for C7n compute instances in CloudPond. Other resources are not supported.
EVS	Only high I/O and ultra-high I/O EVS disks are available. Currently, high I/O EVS disks use HDDs, and ultra-high I/O EVS disks use NVMe SSDs. You cannot customize the media type and size. Currently, EVS disks are deployed in three-copy redundancy. EVS disks cannot be backed up or encrypted. Currently, block storage snapshots of the EVS service can be stored only at the edge.
VPC	If two edge sites are in different VPCs, VPC peering cannot be used to connect the two VPCs. If two edge sites are in the same VPC, the subnet used by each edge site cannot communicate with each other.
EIP	An EIP in a central AZ cannot be bound to an ECS in an edge AZ, or vice versa. An EIP used at an edge site cannot be bound to the ECS that is running at another edge site. An EIP used at an edge site cannot be added to a shared bandwidth in a central AZ, and vice versa.
CloudPond encryption mode	By default, the commercial encryption solution is used. In specific configuration and feature scenarios, SM series cryptographic algorithms can be used (evaluated based on projects).

Previous topic: ECS Specifications for

Next topic: Pricing

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot