Creating a Resource Pool

Creating a Dedicated Resource Pool

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

2. On the Resource Pools tab page, click Create and configure parameters.

   Table 1 Dedicated resource pool parameters

   Parameter	Sub-Parameter	Description
   Name	N/A	Name of a dedicated resource pool. Only lowercase letters, digits, and hyphens (-) are allowed. The value must start with a lowercase letter and cannot end with a hyphen (-).
   Description	N/A	Brief description of a dedicated resource pool
   Billing Mode	N/A	You can select Pay-per-use.
   Job Type	N/A	Select job types supported by the resource pool based on service requirements.
   Network	N/A	Network in which the target service instance is deployed. The instance can exchange data with other cloud service resources in the same network. Select a network from the drop-down list box. If no network is available, click Create on the right to create a network. For details about how to create a network, see Creating a Network.
   Specification Management	Specifications	Select required specifications. Due to system loss, the actual available resources are less than those specified in the specifications. After a dedicated resource pool is created, you can view the actual available resources on the Nodes tab page of the dedicated resource pool details page.
   	AZ	You can select Automatically allocated or Specifies AZ. An AZ is a physical region where resources use independent power supplies and networks. AZs are physically isolated but interconnected over an intranet. Automatically allocated: AZs are automatically allocated. Specifies AZ: Specify AZs for resource pool nodes. To ensure system disaster recovery, deploy all nodes in the same AZ. You can set the number of nodes in an AZ.
   	Nodes	Select the number of nodes in a dedicated resource pool. More nodes mean higher computing performance. If AZ is set to Specifies AZ, you do not need to configure Nodes. NOTE: It is a good practice to create no more than 30 nodes at a time. Otherwise, the creation may fail due to traffic limiting.
   Custom Driver	N/A	This parameter is available only when a GPU flavor is selected. Enable this function and select a GPU driver.
   GPU Driver	N/A	This parameter is available only when custom driver is enabled. Select a GPU accelerator driver. NOTE: You should choose NVIDIA driver 535.129.03 or later for hnt8 series specifications.
   Advanced Configuration	N/A	Select Configure Now to set the tag information, CIDR block, cluster specifications, and controller node distribution.
   CIDR Block	N/A	You can select Default or Custom. Default: The system randomly allocates an available CIDR block to you, which cannot be modified after the resource pool is created. For commercial use, customize your CIDR block. Custom: You need to customize K8S container and K8S service CIDR blocks. K8S Container Network: used by the container in a cluster, which determines how many containers there can be in a cluster. The value cannot be changed after the resource pool is created. K8S Service Network: used when the containers in the same cluster access each other, which determines how many Services there can be. The value cannot be changed after the resource pool is created.
   Cluster Specifications	N/A	Cluster Scale: maximum number of nodes that can be managed by the cluster.After the creation, the cluster can be scaled out but cannot be scaled in. You can select Default or Custom.
   Master Distribution	N/A	Distribution locations of controller nodes. You can select Random or Custom. Random: Use the AZs randomly allocated by the system. Custom: Select AZs for controller nodes. Distribute controller nodes in different AZs for disaster recovery.

3. Click Next and confirm the settings. Then, click Submit to create the dedicated resource pool.
   • After a resource pool is created, its status changes to Running. Only when the number of available nodes is greater than 0, tasks can be delivered to this resource pool.
     Figure 1 Viewing a resource pool
     
   • You can view the task records of the resource pool by clicking Records in the upper left corner of the resource pool list.
     Figure 2 Resource pool list
     

FAQs

What if I choose a flavor for a dedicated resource pool, but get an error message saying no resource is available?

The flavors of dedicated resources change based on real-time availability. Sometimes, you might choose a flavor on the purchase page, but it is sold out before you pay and create the resource pool. This causes the resource pool creation to fail.

You can try a different flavor on the creation page and create the resource pool again.

Q: Why cannot I use all the CPU resources on a node in a resource pool?

Resource pool nodes have systems and plug-ins installed on them. These take up some CPU resources. For example, if a node has 8 vCPUs, but some of them are used by system components, the available resources will be fewer than 8 vCPUs.

You can check the available CPU resources by clicking the Nodes tab on the resource pool details page, before you start a task.