Microservices Engine:Migrate configurations from a self-managed Nacos instance to MSE Nacos

Option A: Cold migration with export and import

Option B: Hot migration with MSE Sync

MSE Sync provides real-time configuration synchronization between the self-managed instance and MSE Nacos. For deployment instructions, see Migration solution based on MSE Sync.

1. After MSE Sync is deployed, log on to the MSE console. In the left-side navigation pane, choose Microservices Registry > Migration to Cloud. Click Migration configuration.

   

2. In the Migration configuration panel, click Next to reach the Create Configuration step. Configure the following fields:

   Field	Value
   Source instance type	Nacos
   Synchronization Type	Configure Synchronization
   Source Instance Node Address	IP address and port of your self-managed Nacos node
   Destination Instance	Your MSE Nacos instance

3. Click Next to reach the Implement migration step. Click Download and save the configuration that you want to migrate. to import the configurations into MSE Sync.

   

Spring Cloud Alibaba

Check whether the following dependency exists in your pom.xml:

<dependency>
    <groupId>com.alibaba.cloud</groupId>
    <artifactId>spring-cloud-starter-alibaba-nacos-config</artifactId>
</dependency>

If it does, update bootstrap.properties:

# Replace with the MSE Nacos endpoint (internal or public)
spring.cloud.nacos.config.server-addr=<mse-nacos-endpoint>

If the namespace ID has changed, update it as well. Leave it blank for the default namespace. Find the namespace ID on the Namespace page of your MSE Nacos instance.

Nacos SDK for Java

Check whether the following dependency exists in your pom.xml:

<dependency>
    <groupId>com.alibaba.nacos</groupId>
    <artifactId>nacos-client</artifactId>
</dependency>

If it does, update the connection properties and redeploy:

// Replace with the MSE Nacos endpoint
properties.put("serverAddr", "<mse-nacos-endpoint>");
// Replace with the MSE Nacos namespace ID (leave blank for the default namespace)
properties.put("namespace", "<namespace-id>");

Nacos Spring Boot

Update application.properties:

# Replace with the MSE Nacos endpoint
nacos.config.server-addr=<mse-nacos-endpoint>
# Replace with the MSE Nacos namespace ID
nacos.config.namespace=<namespace-id>

Go

Update the server configuration in your Go application:

sc := []constant.ServerConfig{
    {
        IpAddr: "<mse-nacos-endpoint>",
        Port:   8848,
    },
}

For a complete example, see nacos-sdk-go.

Python

Update the server address and namespace:

SERVER_ADDRESSES = "<mse-nacos-endpoint>"
NAMESPACE = "<namespace-id>"
client = nacos.NacosClient(SERVER_ADDRESSES, namespace=NAMESPACE)

Node.js

Update the client configuration:

const configClient = new NacosConfigClient({
  serverAddr: '<mse-nacos-endpoint>',
  namespace: '<namespace-id>',
  accessKey: 'MSE_AK',
  secretKey: 'MSE_SK',
  requestTimeout: 6000,
});

C#

Update the NacosConfig section in your configuration file:

{
  "NacosConfig": {
    "Listeners": [
      {
        "Optional": false,
        "DataId": "common",
        "Group": "DEFAULT_GROUP"
      },
      {
        "Optional": false,
        "DataId": "demo",
        "Group": "DEFAULT_GROUP"
      }
    ],
    "Namespace": "<namespace-id>",
    "ServerAddresses": [ "http://<mse-nacos-endpoint>:8848/" ],
    "UserName": "<username>",
    "Password": "<password>",
    "AccessKey": "MSE_AK",
    "SecretKey": "MSE_SK",
    "EndPoint": "acm.aliyun.com",
    "ConfigFilterAssemblies": ["YouPrefix.AssemblyName"],
    "ConfigFilterExtInfo": "some ext information"
  }
}

C++

Update the server address and namespace:

Properties props;
props[PropertyKeyConst::SERVER_ADDR] = "<mse-nacos-endpoint>:8848";
props[PropertyKeyConst::NAMESPACE] = "<namespace-id>";