(Optional) buy an Incremental Package

Background

• You can choose More > View Packages to view incremental packages.

Buying a Pay-Per-Use CDM Cluster

If you buy a pay-per-use incremental package, the system automatically creates a CDM cluster based on the specifications you select.

You can buy a CDM cluster by buying an incremental package on the DataArts Studio console or buy a CDM cluster directly on the CDM console.

Note that the CDM clusters you buy on the CDM console can be used only in the default workspace on the DataArts Studio console. In addition, a CDM cluster bought on the DataArts Studio console can only use the incremental package bought on the DataArts Studio console, and a CDM cluster bought on the CDM console can only use the incremental package bought on the CDM console.

The former is recommended, and this section uses it as an example.

1. Locate an enabled instance and click .

2. On the displayed page, set parameters based on Table 1.

   Table 1 Parameters for the CDM incremental package

   Parameter	Description
   Package	Select CDM.
   Billing Mode	Select Pay per Use.
   AZ	When you a DataArts Studio instance or incremental package for the first time, there is no requirement on the AZ. When you buy a new DataArts Studio instance or incremental package, determine whether to select the same AZ as the existing one based on your DR and network latency demands. If your application requires good DR capability, deploy resources in different AZs in the same region. If your application requires a low network latency between instances, deploy resources in the same AZ. For details, see AZs.
   Workspace	Select the workspace where the CDM incremental package is to be used. For example, if you want to buy a CDM incremental package in workspace A of the test DataArts Studio instance, select A. After you buy the CDM incremental package, a CDM cluster will be displayed in workspace A.
   Cluster	Customize the cluster name.
   Instance	The following CDM cluster flavors are available: cdm.large: 8 vCPUs and 16 GB of memory The maximum and assured bandwidths are 3 Gbit/s and 0.8 Gbit/s. Up to 20 jobs can be executed concurrently. cdm.xlarge: 16 vCPUs and 32 GB of memory The maximum and assured bandwidths are 10 Gbit/s and 4 Gbit/s. Up to 100 jobs can be executed concurrently. This flavor is well suited to TB-level data migration requiring 10GE high-speed bandwidth. cdm.4xlarge: 64 vCPUs and 128 GB of memory The maximum and assured bandwidths are 40 and 36 Gbit/s, respectively. Up to 300 jobs can be executed concurrently.
   VPC	VPC to which the CDM cluster in the DataArts Studio instance belongs. A VPC is a secure, isolated, and logical network environment. If you want to connect the DataArts Studio instance or CDM cluster to a cloud service (such as DWS, MRS, and RDS), ensure that the CDM cluster can communicate with the cloud service. If the CDM cluster and the cloud service are in the same region, VPC, subnet, and security group, they can communicate with each other by default. If the CDM cluster and the cloud service are in the same VPC but in different subnets or security groups, you must configure routing rules and security group rules. For details about the operations on VPCs, subnets, and security groups, see Virtual Private Cloud User Guide. NOTE: After the CDM instance is created, the VPC cannot be changed.
   Subnet	Subnet to which the CDM cluster in the DataArts Studio instance belongs. A subnet provides dedicated network resources that are isolated from other networks, improving network security. If you want to connect the DataArts Studio instance or CDM cluster to a cloud service (such as DWS, MRS, and RDS), ensure that the CDM cluster can communicate with the cloud service. If the CDM cluster and the cloud service are in the same region, VPC, subnet, and security group, they can communicate with each other by default. If the CDM cluster and the cloud service are in the same VPC but in different subnets or security groups, you must configure routing rules and security group rules. For details about the operations on VPCs, subnets, and security groups, see Virtual Private Cloud User Guide. NOTE: After the CDM instance is created, the VPC cannot be changed.
   Security Group	Security group to which the CDM cluster in the DataArts Studio instance belongs. A security group is a set of ECS access rules. It provides access policies for ECSs that have the same security protection requirements and are mutually trusted in a VPC. If you want to connect the DataArts Studio instance or CDM cluster to a cloud service (such as DWS, MRS, and RDS), ensure that the CDM cluster can communicate with the cloud service. If the CDM cluster and the cloud service are in the same region, VPC, subnet, and security group, they can communicate with each other by default. If the CDM cluster and the cloud service are in the same VPC but in different subnets or security groups, you must configure routing rules and security group rules. For details about the operations on VPCs, subnets, and security groups, see Virtual Private Cloud User Guide. NOTE: After the CDM instance is created, the security group cannot be changed.

   

   You cannot modify the specifications of an existing cluster. If you need higher specifications, create another cluster.

3. Click Now, confirm the specifications, and click Next.
4. View the CDM cluster in the corresponding workspace.

Buying a Yearly/Monthly CDM Cluster

If you want to enjoy the preferential price of the yearly/monthly incremental package, you can buy a yearly/monthly incremental package and then buy a pay-per-use incremental package which is in the same region and has the same specifications as the yearly/monthly incremental package.

You can buy a CDM cluster by buying an incremental package on the DataArts Studio console or buy a CDM cluster directly on the CDM console.

Note that the CDM clusters you buy on the CDM console can be used only in the default workspace on the DataArts Studio console. In addition, a CDM cluster bought on the DataArts Studio console can only use the incremental package bought on the DataArts Studio console, and a CDM cluster bought on the CDM console can only use the incremental package bought on the CDM console.

The former is recommended, and this section uses it as an example.

1. Locate an enabled instance and click .
2. On the displayed page, set the following parameters:
   1. Select CDM for Package.
   2. Select Yearly/Monthly for Billing Mode.
   3. Specify a validity period in Usage Duration for the package.
   4. Enter the number of subscribed packages in Purchase Quantity. For example, if you specify 1 month for Usage Duration and 2 for Purchase Quantity, you will have a 1490-hour quota and the validity period will be 1 month.
3. Click Buy Now. If there are no changes made to the specifications, submit the order.
4. After you buy the yearly/monthly package, the system will not automatically create a CDM cluster. You need to buy a pay-per-use incremental package in the same region and with the same specifications as the yearly/monthly package by following the instructions in Buying a Pay-Per-Use CDM Cluster. Then you can enjoy the preferential price of the yearly/monthly incremental package.

a DataArts DataService Exclusive Cluster

1. Locate an enabled instance and click .
2. On the displayed page, set parameters based on Table 2.

   Table 2 Parameters for an exclusive DataArts DataService instance

   Parameter	Description
   Package	Select DataArts DataService.
   Billing Mode	Currently, Yearly/Monthly is supported.
   Workspace	The workspace for which you want to use the incremental package. For example, if you want to use DataArts DataService Exclusive in workspace A of the DataArts Studio instance, select workspace A. After an exclusive DataArts DataService cluster, you can view it in workspace A.
   AZ	When you buy a DataArts Studio instance or incremental package for the first time, you can select any available AZ. When you buy another DataArts Studio instance or incremental package, determine whether to deploy your resources in the same AZ based on your DR and network latency demands. If your application requires good DR capability, deploy resources in different AZs in the same region. If your application requires a low network latency between instances, deploy resources in the same AZ. For details, see AZs.
   Name	N/A
   Description	A description of the exclusive DataArts DataService cluster.
   Version	Cluster version of the exclusive DataArts DataService cluster.
   Cluster Details	The number of concurrent API requests supported varies depending on the instance specifications.
   Enabling public IP address	If you select Enabling public IP address, external services can call the APIs created in exclusive instances through the Internet address.
   Bandwidth	Bandwidth range on the Internet.
   VPC	A VPC is a secure, isolated, and logical network environment. Cloud resources (such as ECSs) within the same VPC can call APIs using the private IP address of DataArts DataService Exclusive. Deploy the DataArts DataService Exclusive instance in the same VPC as your other services to facilitate network configuration and secure network access. NOTE: After the DataArts DataService instance is created, the VPC cannot be changed.
   Subnet	A subnet provides dedicated network resources that are logically isolated from other networks for network security. Deploy the DataArts DataService Exclusive instance in the same subnet of the same VPC as your other services to facilitate network configuration and secure network access. NOTE: After the DataArts DataService instance is created, the subnet cannot be changed.
   Security Group	A security group is used to set port access rules, define ports that can be accessed by external services, and determine the IP addresses and ports that can be accessed externally. For example, if the backend service is deployed on an external network, configure security group rules to allow access to the IP address and listening port of the backend service. NOTE: If Enabling the public IP address is selected, the security group must allow access from ports 80 (HTTP) and 443 (HTTPS) in the inbound direction. After the DataArts DataService instance is created, the security group cannot be changed.
   Managing Cluster Resources Using an Enterprise Project	Enterprise project associated with the exclusive DataArts DataService cluster. An enterprise project facilitates management of cloud resources. For details, see Enterprise Management User Guide.
   Nodes	N/A
   Required Duration	N/A

3. Click Now, confirm the settings, and click Next.