Help Center> Migration Center> User Guide> Migration Clusters> Creating a Migration Cluster
Updated on 2024-05-06 GMT+08:00
View PDF

Creating a Migration Cluster

After you create a migration cluster, you can manage the migration and list nodes in the cluster, such as installing or upgrading migration plug-ins on the nodes.

You pay for migration clusters and additional resources used by these clusters. For details, see Billing.

Procedure

  1. Log in to the MgC console. In the left navigation pane, choose Deploy > Migration Clusters.
  2. Click Create Cluster in the upper right corner of the page.
  3. Configure the parameters listed in Table 1.

    Table 1 Parameters for creating a cluster

    Area

    Parameter

    Configuration

    Constraints

    Basic Settings

    Cluster Name

    Enter a custom name.

    Cluster names in the same account must be unique.

    Region

    Select the region to provision the cluster.

    -

    Cluster Type

    Select a cluster application scenario.

    Currently, only storage migration is supported.

    Node Settings

    Master Node

    Select the specifications of the master node which is used to manage migration nodes and list nodes in the cluster. The master node is created by default. You do not need to configure it.

    The master node has the same specifications as migration nodes.

    Migration Node

    Migration nodes are used for executing migration and verification tasks. The recommended specifications are 8 vCPUs and 16 GB of memory.
    • The node specifications cannot be modified after the cluster is created.
    • The number of nodes must meet the following requirements:
      • Number of migration nodes + Number of list nodes + 1 ≤ 100
      • Number of migration nodes + Number of list nodes + 1 ≤ Number of unused IP addresses in the subnet

    List Node

    List nodes are used for listing tasks. The recommended specifications are 8 vCPUs and 16 GB of memory.

    Network Settings

    VPC

    Select a VPC from the drop-down list.

    -

    Subnet

    Make sure that there are enough IP addresses for the migration and list nodes in this cluster.

    Number of unused IP addresses in the subnet ≥ Number of migration nodes + Number of list nodes + 1

    Network Type
    • Public: Select a public NAT gateway. If there is no gateway available, choose Buy Gateway from the drop-down list and select the gateway specifications and EIPs you want to associate with the gateway. A maximum of 20 EIPs can be selected at a time.
    • Private: Enter an IP address of such as Nginx or gateway that is allowed to forward or send requests over the private line.

    -

    -

    Traffic Limiting

    Allocate the maximum bandwidth to be used by the workflow during a specified period.

    • If you do not select this option, migration traffic is not limited.
    • If you select this option, limit the migration traffic by setting the start time, end time, and bandwidth limit.
      NOTICE:

      For example, if you set Start Time to 08:00, End Time to 12:00, and Maximum Bandwidth to 20 MB/s, the maximum migration speed is limited to 20 MB/s when the migration task is running in the period from 08:00 to 12:00. The migration speed is not limited beyond this period.
    • A maximum of five traffic limiting rules can be added.
    • The time is the local standard time of the region you are migrating to.

    Log Collection
    • If this option is enabled, logs generated during storage migrations are collected for locating problems if any.
    • If this option is disabled, logs generated during storage migrations are not collected.

    -

  4. Click Confirm. You can view the cluster status in the migration cluster list. For details about cluster statuses, see Cluster Statuses.
  5. After the migration cluster is created, perform the following operations:

    • If the cluster status is Healthy or Subhealthy, click Create Workflow in the Operation column .
    • Click Manage in the Operation column to add or delete nodes and traffic control rules. For details, see Managing a Migration Cluster.

Parent topic: Migration Clusters