检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Table 1 Resource quotas involved in ModelArts Lite Service Resource Type ECS resource type ECS instances CPU cores RAM capacity (MB) EIP resources Bandwidth scaling policies EVS and SFS resources Disks Disk capacity (GB) Snapshots SFS resources Capacity limit
Ensure that an EIP has been bound to the ECS and the security group configuration is correct (the inbound traffic from TCP port 3000 and all outbound traffic are allowed). Configuration process: Click the ECS name to go to the ECS details page.
Ensure that an EIP has been bound to the ECS and the security group configuration is correct (the inbound traffic from TCP port 3000 and all outbound traffic are allowed). Configuration process: Click the ECS name to go to the ECS details page.
For details, see Creating a Custom Image on an ECS and Using It in Notebook. Parent topic: Using Custom Images in Notebook Instances
Enums: BMS: BMS ECS: ECS HPS: supernode server hps_id String Resource ID of the supernode to which the server belongs.
If the server type is ECS, you can mount a disk on the ECS details page. For details, see Attaching a Disk to an ECS. After an EVS data disk is attached, it needs to be initialized. For details, see Initialization Overview. Parent topic: Configuring Lite Server Resources
Log in to the ECS as user root and enter the login command. Figure 1 Login command executed on the ECS Step 2 Upload Images to SWR This section describes how to upload an image to SWR. Log in to SWR and tag the image to be uploaded.
Enums: BMS: BMS ECS: ECS HPS: supernode server hps_id String Resource ID of the supernode to which the server belongs.
Enums: BMS: BMS ECS: ECS HPS: supernode server hps_id String Resource ID of the supernode to which the server belongs.
Enums: BMS: BMS ECS: ECS HPS: supernode server hps_id String Resource ID of the supernode to which the server belongs.
Enums: BMS: BMS ECS: ECS HPS: supernode server hps_id String Resource ID of the supernode to which the server belongs.
Enums: BMS: BMS ECS: ECS HPS: supernode server hps_id String Resource ID of the supernode to which the server belongs.
ECS BMS EVS DEW ecs:cloudServers:create ecs:cloudServers:delete ecs:cloudServers:get ecs:cloudServers:start ecs:cloudServers:stop ecs:cloudServers:reboot ecs:cloudServers:redeploy ecs:cloudServers:listServerInterfaces ecs:cloudServers:changeVpc ecs:cloudServerFlavors:get ecs:quotas
Enums: BMS: BMS ECS: ECS HPS: supernode server hps_id String Resource ID of the supernode to which the server belongs.
Creating a Custom Image for a Notebook Instance Creating a Custom Image Creating a Custom Image on ECS and Using It Creating a Custom Image Using Dockerfile Creating a Custom Image Using the Image Saving Function Parent topic: Creating a Custom Image for ModelArts Standard
ECS An Elastic Cloud Server (ECS) is a basic computing unit that consists of vCPUs, memory, OS, and Elastic Volume Service (EVS) disks. After an ECS is created, you can use it similarly to how you would use your local PC or physical server.
The default resources provided by the cloud services, such as elastic cloud server (ECS), elastic IP (EIP), and Scalable File Service (SFS), may not meet your requirements. Submit a service ticket to increase resource quota. Grant the required basic permissions to the IAM user.
Creating a Custom Image for Inference Creating a Custom Image for a Model Creating a Custom Image in a Notebook Instance Using the Image Saving Function Creating a Custom Image in a Notebook Instance Using Dockerfile Creating a Custom Image on ECS Parent topic: Creating a Custom Image
Using Custom Images in Notebook Instances Constraints on Custom Images in Notebook Instances Registering an Image in ModelArts Creating a Custom Image Saving a Notebook Instance as a Custom Image Creating and Using a Custom Image in Notebook Creating a Custom Image on an ECS and Using
You can directly copy and paste the content. { "Version": "1.1", "Statement": [ { "Effect": "Allow", "Action": [ "ecs:serverKeypairs:list", "ecs:serverKeypairs:get", "ecs:serverKeypairs:delete
