Planning VPC networking

To enable VPC networking, the network architecture diagram is shown below:

• Management network: Used for cluster management.
• Storage network: Used for data exchange between hosts within the cluster.
• TEP IP pool: Used to allocate TEP IP addresses to hosts in the cluster and edge gateway virtual machines.
• Internal subnet: Used to allocate internal service IP addresses to gateway services of each VPC.
• External subnet: Used to specify the interface between the data plane of the edge gateway virtual machine and the external network, and to define address ranges.

To use the VPC networking, you need to plan the internal subnet, TEP network, and external subnet according to the following requirements and suggestions. Before planning, obtain the IP addresses of the management network and storage network of the ACOS (AVE) in advance.

• TEP IP pool

  You can plan the number of TEP IP addresses based on the formula TEP IP count > (number of edge gateway virtual machines * 2 + number of hosts in associated clusters + 3). Ensure there are sufficient IP addresses to avoid failures in creating edge gateway or associating clusters.

  You can add multiple TEP IP pools. Ensure that the addresses in multiple TEP IP pools can communicate with each other.

  It is recommended that the addresses in the TEP IP pools do not overlap with the IP addresses of the cluster management network and storage network.

• Internal subnet

  The default address block is 100.64.0.0/16, but you can use another address block. Ensure there are sufficient IP addresses to avoid failures in creating gateway services.

  Ensure that there is no overlap between the CIDR blocks of the internal subnet and the VPC subnet. When you need to use a routing gateway to communicate between a VPC and an external network, Ensure that the CIDR blocks of the internal subnet, external subnet, and VPC subnet do not overlap with each other.

  It is also recommended that the internal subnet does not overlap with TEP IP pools, cluster management IP addresses, and storage network IP addresses.

• External subnet

  It is recommended that the external subnet does not overlap with TEP IP pools, internal subnet, cluster management IP addresses, and cluster storage IP addresses.

  It is recommended to plan the address blocks of the NAT gateway and floating IP. Layer 2 gateway and routing gateway can be planned as needed when used.

  When you need to use a routing gateway to communicate between a VPC and an external network, ensure that the CIDR blocks of the internal subnet, external subnet, and VPC subnet do not overlap with each other.