Create a multi-active instance

Prerequisites

Before you create a geo-redundant instance, you must activate the required modules, create a Business LDC, import your ECS and SLB resources, and create and configure an ingress cluster.

Procedure

A multi-active instance, which corresponds to an MSHA namespace, functions as a logical tenant. It provides logical isolation for MSHA control configurations and data. The following steps describe how to create a multi-active instance.

1. Log on to the MSHA console.

2. In the navigation pane on the left, choose Multi-active Instance to open the Multi-active Instance list page.

3. In the upper-left corner of the list, click Create Multi-active Instance. On the Create Multi-active Instance page, configure the following parameters.

   1. Enter a Multi-active Instance Name, for example, "Production environment for transaction unitization" or "Test environment for shopping-guide unitization".

   2. From the Business LDC drop-down list, select a Business LDC for the namespace. After you select a Business LDC, its business type identifier appears on the right.

      Note

      To create a business type, click Create Business LDC. This takes you to the Business LDC page, where you can create a Business LDC. For detailed instructions, see Business LDC.

   3. After you select Business LDC, you can select a Multi-active Architecture Type. Set Multi-active Architecture Type to Geo-redundancy.

      Important

      1. The geo-redundancy architecture option is available only if the Business LDC contains two units.

      2. A geo-redundancy architecture can nest an intra-city multi-active architecture. However, a single multi-active instance cannot use two different types of geo-redundancy architectures.

   4. After you select the Multi-active Architecture Type, the Multi-active Components section appears. Select the Multi-active Components to enable. You can select more than one.

4. Click Next. This takes you to the Control Command Channel configuration page. You must configure a control command channel to push MSHA rules. You can choose Nacos (in a VPC or Classic Network) or ACM (for on-premises environments only).

   Note

   The region of Nacos or ACM must be the same as the region of its corresponding unit.

   • If you set the Control Command Channel to Nacos, configure the following parameters:

     Parameter	Description
     Nacos Address	You can specify the Nacos address in one of the following ways: Method 1: Enter the private IP address of the server where Nacos is deployed. The address must include the port number, for example: 192.168.xx.xx:9848. Method 2: Enter the instance ID of a Microservices Engine (MSE) instance that uses Nacos as its engine. For example: mse-cn-7mzxxxxxx.
     Nacos Namespace ID	Enter the namespace ID of the Nacos service or MSE instance used for pushing MSHA rules.
     VPC ID	Enter the VPC ID where Nacos is located.

   • If you set the Control Command Channel to ACM, you only need to enter the ACM namespace ID.

5. After configuring the Control Command Channel, click Next. The Ingress Cluster configuration page opens. On this page, you need to select an ingress cluster from a list and configure it for each unit of your multi-active instance.

   • To create an MSFE cluster, click Create Cluster. For more information, see Manage MSFE ingress clusters.

   • To create a cloud-native gateway cluster, click Create Cluster. For more information, see Manage cloud-native gateway ingress clusters.

   Note

   You need to configure the ingress cluster only if you have selected the Ingress Component in the Multi-active Components section. Otherwise, this page is skipped.

6. Click Submit.