(Optional) Creating a DataArts Studio Incremental Package

DataArts Studio provides basic and incremental packages. If the basic package cannot meet your requirements, you can create an incremental package. Before you create an incremental package, ensure that you have a DataArts Studio instance.

You can choose the following incremental packages:

  • DataArts Migration (namely CDM) incremental package

    The DataArts Studio instance does not contain CDM clusters. To use the DataArts Migration function, create a CDM incremental package.

Background

After you create an incremental package, the system automatically creates a cluster for your service based on your selected specifications.

Creating a CDM Cluster

  1. Locate an enabled instance and click Create.

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

    Table 1 Parameters for the CDM incremental package

    Parameter

    Description

    Package

    Select CDM.

    AZ

    When you a DataArts Studio instance or incremental package for the first time, there is no requirement on the AZ.

    When you create 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.

    Workspace

    Select the workspace where the CDM incremental package is to be used. For example, if you want to create a CDM incremental package in workspace A of the test DataArts Studio instance, select A. After you create 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, 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, 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, see Virtual Private Cloud User Guide.

    Note

    After the CDM instance is created, the security group cannot be changed.

    Important

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

  2. Click Create Now, confirm the specifications, and click Next.

  3. View the CDM cluster in the corresponding workspace.