• Cloud Container Engine

cce
  1. Help Center
  2. Cloud Container Engine
  3. User Guide 2.0
  4. Data Migration from an Earlier Version to the Latest Version
  5. Migrating a Cluster

Migrating a Cluster

This section describes how to create a VM cluster in the console of the latest CCE version with the same specifications as that in the earlier CCE version.

If you need to create a cluster using APIs, see Cloud Container Engine API Reference 2.0 for details.

Procedure

  1. Log in to the CCE console. In the navigation pane, choose Resource Management > VM Clusters, and click Create VM Cluster.
  2. Set the parameters. The parameters marked with * are mandatory.

    Figure 1 shows an example of specifications of a cluster created in the earlier CCE version.

    Figure 1 Cluster specifications in the earlier CCE version
    Table 1 Parameters for creating a cluster

    New Parameter

    Old Parameter

    Description

    * Cluster Name

    Name

    Name of the cluster to be created.

    * Version

    This parameter is not available in the earlier CCE version. Retain the default value.

    Cluster version, which corresponds to the Kubernetes base version.

    * Size

    This parameter is not available in the earlier CCE version. Set this parameter based on service requirements.

    Maximum number of nodes that can be managed by the cluster.

    * High Availability

    Cluster Type

    • Yes: Three management nodes are created in the cluster. When two management nodes are faulty, the cluster is still available.
    • No: A common cluster is a single master. If the management node is faulty, the cluster becomes unavailable, but running applications are not affected.

    * VPC

    The VPC created in the earlier CCE version can be used in the new version.

    VPC where the new cluster is located.

    If no VPC is available, click Create a VPC and create one.

    * Subnet

    The subnet created in the earlier CCE version can be used.

    Subnet in which the VM on the node runs.

    * Network Model

    This parameter is not available in the earlier CCE version. Set this parameter based on service requirements.

    • Tunnel network: A virtual network built on top of a VPC network, applicable to common scenarios.
    • VPC network: A VPC network that delivers higher performance and applies to high-performance and intensive interaction scenarios. Only one cluster using the VPC network model can be created under a VPC.

    Description

    Description

    Description of the new container cluster.

  3. After the configuration is complete, click Next to add a node.
  4. Select whether to create a node. Click Yes.
  5. Set parameters shown in Table 2.

    Table 2 Parameters for adding a node

    New Parameter

    Old Parameter

    Description

    Region

    AZ

    Region

    Physical location where resources use independent power supplies and networks. AZs are physically isolated but interconnected through an internal network. To improve application reliability, you are advised to create cloud servers in different AZs.

    Specifications

    Node Name

    Specifications

    Node name.

    Node Specifications

    • General-purpose: Provides general computing, storage, and network configurations for the majority of application scenarios. General-purpose instances can be used for web servers, development and test environments, and small database applications.
    • Memory-optimized: Provides instances with larger-size memory. It is applicable for memory-intensive applications that process a large amount of data, such as relational databases and NoSQL databases.

    Operating System

    Only EulerOS 2.2 is supported.

    Nodes

    Quantity

    Number of nodes.

    Network

    NOTE:

    By default, the SNAT function of VPCs is disabled on CCE. If SNAT is enabled, EIPs are not required for accessing external networks.

    EIP

    EIP

    An independent public IP address. If a node needs to access the Internet, buy an EIP or use an existing EIP.

    • Do not use: A cloud server without an EIP cannot access the Internet. It can be used only as a cloud server for deploying services or clusters on a private network.
    • Automatically assign: An EIP is automatically assigned with exclusive bandwidth to each cloud server. When creating an ECS, ensure that the EIP quota is sufficient. Set the specifications and bandwidth as required.
    • Specify: An existing EIP is assigned to the cloud server.

    Disk

    Storage

    A system disk or a data disk.

    • The system disk capacity ranges from 40 GB to 1024 GB, which can be configured by users. The default value is 40 GB.
    • The data disk capacity ranges from 100 GB to 32678 GB, which can be configured by users. The default value is 100 GB.
    Data disks deliver three levels of I/O performance:
    • Common I/O: EVS disks of this level provide reliable block storage and can be used for key applications. The IOPS of a single disk can reach up to 1000.
    • High I/O: EVS disks of this level provide a maximum IOPS of 3,000 and a minimum read/write latency of 1 ms. They can be used for RDS, NoSQL, data warehouse, and file system applications.
    • Ultra-high I/O: EVS disks of this level provide a maximum IOPS of 20,000 and a minimum read/write latency of 1 ms. They can be used for RDS, NoSQL, and data warehouse applications.

    Login Information

    Key Pair

    Key Pair

    Key pair for identity authentication when you remotely log in to a node. Select an existing key pair.

    If no key pair is available, click Create a key pair and create one.

    Advanced Settings

    File Injection

    This parameter is not available in the earlier CCE version.

    Used to inject files into ECSs when performing tasks involving scripts, such as:

    • Simplifying ECS configuration using scripts
    • Initializing OS configuration using scripts
    • Uploading your scripts to an ECS at creation time

    Procedure

    1. Click Add File.
    2. Enter the file path or the file name. In Linux, enter the file path that contains the file name (for example, /etc/foo.txt). The file name can contain only letters and digits.
    3. Click Select File, and select a written script that meets the OS requirements.

  6. Click Create Now, review the details, and click Submit.

    It takes 6 to 10 minutes to create a cluster. Information about the progress of the creation process will be displayed.