- Release Notes and Announcements
- [January 15, 2024]Announcement on the Official Launch of CCN Routing Reception and Routing Propagation Policies
- [July 3, 2023] Start Charging on CCN Connected Network Instances and Inbound Traffic
- Jul. 26, 2022 - CCN Tagging Upgrade
- Feb 10, 2022 - CCN API Authentication Upgrade
- Jun. 25, 2021 - Free Hangzhou-Shanghai and Hangzhou-Nanjing Lines
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Best Practices
- API Documentation
- FAQs
- Troubleshooting
- Service Agreement
- Contact Us
- Release Notes and Announcements
- [January 15, 2024]Announcement on the Official Launch of CCN Routing Reception and Routing Propagation Policies
- [July 3, 2023] Start Charging on CCN Connected Network Instances and Inbound Traffic
- Jul. 26, 2022 - CCN Tagging Upgrade
- Feb 10, 2022 - CCN API Authentication Upgrade
- Jun. 25, 2021 - Free Hangzhou-Shanghai and Hangzhou-Nanjing Lines
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Best Practices
- API Documentation
- FAQs
- Troubleshooting
- Service Agreement
- Contact Us
Separate Deployment of Test Environment and Production Environment
Last updated: 2024-01-10 14:41:59
You have activated the CCN service, and all VPCs in your organization have been interconnected through CCN. By default, network instances added to CCN are interconnected.
In certain scenarios, you can divide different network zones in your organization network, and network instances in different zones are isolated from each other. This can be implemented through the custom route table feature of CCN. Specifically, you can plan different custom route tables for CCN and associate different network instances with them in order to isolate network instances.
Note:
Overview
The network instances associated with CCN are divided into a test zone and a production zone. Network instances are interconnected within the same zone but isolated across zones.
As shown below, create two custom route tables for the CCN instance: the test route table and the production route table.
Here:
The test route table only receives and learns routes from and is bound to the test VPC.
The production route table only receives and learns routes from and is bound to the production VPC.
Prerequisites
1. You have activated the CCN service and created a CCN instance. For detailed directions, please see Creating a CCN Instance.
2. The CCN instance has been associated with 4 network instances (for verification and subject to your actual business needs). For detailed directions, please see Associating Network Instances.
Directions
Step 1. Plan a custom route table
According to the isolation of network zones, two custom route tables need to be planned: the test route table and the production route table.
The routing plan of the custom route table is as follows:
Item | Test Route Table | Production Route Table |
Route reception policy | Receive the routes of the network instances in the network zone of the test environment, i.e., routes of the test frontend VPC and the test backend VPC. | Receive the routes of the network instances in the network zone of the production environment, i.e., routes of the production frontend VPC and the production backend VPC. |
Bound network instance | Bind the network instances in the network zone of the test environment, i.e., the test frontend VPC and test backend VPC. | Bind the network instances in the network zone of the production environment, i.e., the production frontend VPC and production backend VPC. |
Step 2. Create a custom route table
1. Log in to the CCN console.
2. In the CCN list, click the CCN ID to enter the details page and access the Route Table tab.
3. Click Create Route Table.
4. In the pop-up window, enter the name and other information.
5. Click OK.
6. Repeat steps 3–5 to create the production route table.
Step 3. Set the route reception policy
1. Click the test route table ID to enter the details page and access the Route Reception Policy tab.
2. Click Add Network Instance.
3. On the Select a network instance tab, select the network instances in the test zone, i.e., the test frontend VPC and test backend VPC.
4. Click OK to complete the route reception policy configuration of the test route table.
5. Select the production route table and repeat steps 1–4 to configure its route reception policy.
Step 4. Bind a network instance
1. Click the test route table ID to enter the details page and access the Bind an Instance tab.
2. Click Bind Network Instance.
3. On the Select a network instance tab, select the network instances in the test zone, i.e., the test frontend VPC and test backend VPC.
4. Click OK to complete binding the test route table to network instances.
5. Select the production route table and repeat steps 1–4 to bind it to network instances.
Yes
No
Was this page helpful?