Changing the Subnet of a Cluster

Changing a Subnet When No Network ACL Is Associated

1. Log in to the MRS console.
2. Click the target cluster name to go to its details page.
3. Click Change Subnet on the right of Default Subnet.
   Figure 1 Changing a subnet
   

4. Select the target subnet and click OK.

   If no subnet is available, click Create Subnet to create a subnet first.

   Figure 2 Selecting the target subnet
   

Changing a Subnet When a Network ACL Is Associated

1. Log in to the MRS console and click the target cluster to go to its details page.
2. In the Basic Information area, view VPC.
3. Log in to the VPC console. In the navigation pane on the left, choose Virtual Private Cloud and obtain the IPv4 CIDR block corresponding to the VPC obtained in 2.
   Figure 3 Obtaining the IPv4 CIDR block
   

4. Choose Access Control > Network ACLs and click the name of the network ACL that is associated with the default and new subnets.
   

   If both the default and new subnets are associated with a network ACL, add inbound rules to the network ACL by referring to 5 to 7.

   Figure 4 Network ACLs
   

5. On the Inbound Rules page, choose More > Insert Rule Above in the Operation column.
   Figure 5 Inserting Rule Above
   

6. Add a network ACL rule. Set Action to Allow, Source to the VPC IPv4 CIDR block obtained in 3, and retain the default values for other parameters.
   Figure 6 Adding a network ACL rule
   

7. Click OK.
   

   If you do not want to allow access from all IPv4 CIDR blocks of the VPC, add the IPv4 CIDR blocks of the default and new subnets by performing 8 to 12. If the rules for VPC IPv4 CIDR blocks have been added, skip 8 to 12.

8. Log in to the MRS console.
9. Click the target cluster to go to its details page.
10. Click Change Subnet on the right of Default Subnet.
    Figure 7 Changing a subnet
    

11. Obtain the IPv4 CIDR blocks of the default and new subnets.
    

    In this case, you do not need to click OK displayed in the Change Subnet dialog box. Otherwise, the default subnet will be updated to the new subnet, thereby making it difficult to query the IPv4 CIDR block of the default subnet. Exercise caution when performing this operation.

    Figure 8 Obtaining the subnet IP address
    

12. Add the IPv4 CIDR blocks of the default and target subnets to the inbound rules of the network ACL bound to the two subnets by referring to 4 to 7.
13. Log in to the MRS console.
14. Click the target cluster to go to its details page.
15. Click Change Subnet on the right of Default Subnet.
    Figure 9 Changing a subnet
    

16. Select the target subnet and click OK.
    Figure 10 Selecting the target subnet
    

How Do I Configure a Network ACL Outbound Rule?

• Method 1

  Allow all outbound traffic. This method ensures that clusters can be created and used properly.

• Method 2

  Allow the mandatory outbound rules that can ensure the successful creation of clusters. You are not advised to use this method because created clusters may not run properly due to absent outbound rules. If the preceding problem occurs, contact O&M personnel.

  Similar to the example provided in method 1, set Action to Allow and add the outbound rules whose destinations are the address with Secure Communications enabled, NTP server address, OBS server address, OpenStack address, and DNS server address, respectively.