Resizing a Standard Dedicated Resource Pool

Description

The demand for resources in a dedicated resource pool may change due to the changes of AI development services. In this case, you can resize your dedicated resource pool in ModelArts.

• You can add nodes for existing flavors in the resource pool.
• You can delete nodes for existing flavors in the resource pool.

Before scaling in a resource pool, ensure that there are no services running in the pool. Alternatively, go to the resource pool details page, delete the nodes where no services are running to scale in the pool.

Constraints

• Only dedicated resource pools in the Running status can be resized.
• When scaling in a dedicated resource pool, the number of flavors or nodes of a flavor cannot be decreased to 0.

Resizing a Dedicated Resource Pool

You can resize a resource pool in any of the following ways:

• Adjusting the number of nodes of existing specifications
• Resizing the container engine space

1. Log in to the ModelArts management console. In the navigation pane on the left, choose AI Dedicated Resource Pools > Elastic Cluster.
   

   A resource pool is suspended when it is migrated from the old version to the new version. You cannot adjust the capacity of such a resource pool or unsubscribe from it.

   Figure 1 Viewing resource pools
   

2. Add or delete nodes.

   To resize a resource pool, locate the resource pool on the Elastic Clusters page, and click Adjust Capacity. For Yearly/Month resource pools, only Expand Capacity is displayed on the page. To scale in such a resource pool, click the resource pool name to access the details page, and unsubscribe some nodes.

   In the Resource Configurations area, set AZ to Automatically allocated or Specifies AZ. Click Submit and then OK to save the changes.

   • If you select Automatically allocated, you can increase or decrease the number of target nodes to implement scaling. This allows you to adjust the number of nodes based on service requirements. Scale-out is the process of increasing the number of target nodes, while scale-in is the process of decreasing the number of target nodes. After the scaling, nodes are automatically allocated to AZs.
   • If you select Specifies AZ, you can allocate nodes to different AZs.

   Figure 2 Configuring resources on a single node
   

   When you purchase a resource pool, the nodes for certain specifications can be purchased by rack. When you resize the resource pool, the nodes are also added or deleted by rack. You can choose to purchase nodes by rack when creating a resource pool, which cannot be modified when resizing a resource pool. You can configure the rack quantity to change the number of Target Nodes.

   Figure 3 Configuring resources by rack
   
   

   When you add nodes, you can specify the billing mode that is not the mode for charging resource pools. For example, you can create pay-per-use nodes in a yearly/monthly resource pool. If the billing mode is not specified, it will be the mode for charging resource pools.

3. Resizing the container engine

   If you need larger container engine size, perform any of the following operations:

   • For new resource pools, you can specify the container engine space when creating a resource pool. For details, see advanced configurations of Specification Management in Creating a Standard Dedicated Resource Pool.
   • For existing resource pools, you can specify the container engine space to add nodes.
     • Method 1: Click the resource pool name to view its details. In the Specifications tab, locate the specification, and click Change the container engine space size in the Operation column. The space will be modified automatically.
     • Method 2: Locate the resource pool and click Adjust Capacity. If it is a yearly/monthly resource pool, only Expand Capacity is displayed.
     

     Resizing the container engine space is only applicable to new nodes. Furthermore, dockerBaseSize may vary across nodes of this flavor within the resource pool. Consequently, this can lead to discrepancies in the status of tasks distributed among different nodes.

   Figure 4 Resizing the container engine in the Specifications tab
   
   Figure 5 Resizing the container engine on the Resize page