Help Center/ ModelArts/ ModelArts User Guide (Standard)/ ModelArts Standard Resource Management/ Managing Standard Dedicated Resource Pools/ Resizing a Standard Dedicated Resource Pool
Updated on 2024-12-26 GMT+08:00
View PDF
Share

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 pools in ModelArts Standard.

  • You can add instances for existing flavors in the resource pool.
  • You can delete instances 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:

  • Increase or decrease the total number of instances in 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 Clusters.

    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.

  2. For a yearly/monthly resource pool, only Scale Out is displayed. To scale in the resource pool, go to the details page and unsubscribe from the resources. For a yearly/monthly resource pool, only Scale Out is displayed. To scale in the resource pool, go to the details page and unsubscribe from the resources.

  3. On the dedicated resource pool scaling page, set Target Instances as needed. Scale-out is the process of increasing the number of target instances, while scale-in is the process of decreasing the number of target instances.

    When you purchase a resource pool, the nodes for certain specifications can be purchased by rack. When you resize the resource pool, the instances 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 instances.

    When you add instances, 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.

  4. In the Resource Configurations area, set AZ to Automatically allocated or Specifies AZ.
    • After the scaling, nodes are randomly allocated to AZs.
    • If you select Specifies AZ, you can allocate nodes to different AZs.
    Figure 1 Configuring resources on a single node
  5. Resizing the container engine space

    When scaling out a resource pool, you can set the container engine space size of the created node. This operation will cause inconsistence of dockerBaseSize of nodes in the resource pool. Some tasks may run differently on different nodes. Exercise caution when performing this operation. The container engine space size cannot be changed for existing nodes.

  6. Modify the OS. Select an OS version from the OS drop-down list.
  7. Configure the node billing mode. When adding nodes, you can enable Node Billing Mode to set the billing mode and required duration for the new nodes, and enable the auto-renewal function. 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.
  8. Click Submit and then OK.