Document navigation

Prerequisites

Make sure that the latest version of ZStack Cloud is installed, and the basic initialization is completed. Specifically, basic hardware resources, such as the zone, cluster, host, image storage, and primary storage, are added, and an instance offering is created. For more information, see the installation and deployment section and the wizard configuration section in the User Guide.

This tutorial elaborates on the basic deployment of a VPC.

Basic Deployment

ZStack Cloud VPC network supports both IPv4 and IPv6 protocols and users can choose to use IPv4, IPv6, or IPv4+IPv6 dual-stack networks as needed. This chapter introduces the basic deployment of IPv4 and IPv6 VPC networks in detail.

IPv4 Basic Deployment

IPv4, also known as the Internet Protocol version 4, with a 32-bit long address, is the most widely used version of the inter-networking protocol today. ZStack Cloud VPC network supports IPv4 protocol and this chapter will introduce the basic deployment of IPv4 VPC network in detail.

Assume that the customer environment is as follows:

  1. Public Network

    Public Network Configuration
    NIC em1
    VLAN ID No VLAN
    IP Range 10.108.10.100~10.108.10.200
    Netmask 255.0.0.0
    Gateway 10.0.0.1
    DHCP IP 10.108.10.101
  2. Management Network

    Management Network Configuration
    NIC em2
    VLAN ID No VLAN
    IP Range 192.168.29.10~192.168.29.20
    Netmask 255.255.255.0
    Gateway 192.168.29.1
    • For security and stability reasons, we recommend that you deploy an independent management network and separate it from the public networks.
    • The management network we mentioned here is the same as that in ZStack Cloud. That is, the management network is the network used to manage hosts, primary storage, and image storage. If a management network was created before, you can use it directly.
  3. VPC Network-1

    Private Network Configuration
    NIC em1
    VLAN ID 2800
    IP CIDR 192.168.10.0/24
    Gateway 192.168.10.1
    DHCP IP 192.168.10.2
  4. VPC Network-2

    Private Network Configuration
    NIC em1
    VLAN ID 2900
    IP CIDR 192.168.11.0/24
    Gateway 192.168.11.1
    DHCP IP 192.168.11.2

To deploy a VPC Network in the Cloud, follow these steps:

  1. Create an L2 public network and attach it to the corresponding cluster.
  2. Create an L3 public network.
  3. Create an L2 management network and attach it to the corresponding cluster.
  4. Create an L3 management network.
  5. Add a vRouter image.
  6. Create a vRouter offering.
  7. Create a VPC vRouter from the vRouter offering you created in the preceding step.
  8. Create an L2 private network and attach it to the corresponding cluster. This L2 private network is used to create an L3 VPC network (VPC Network-1).
  9. Create an L3 VPC network (VPC Network-1).
  10. Create an L2 private network and attach it to the corresponding cluster. This L2 private network is used to create an L3 VPC network (VPC Network-2).
  11. Create an L3 VPC network (VPC Network-2).
  12. Use VPC Network-1 and VPC Network-2 to create VM-1 and VM-2, respectively.
  13. Test the connectivity between VPC Network-1 and VPC Network-2.
  1. Create an L2 public network and attach it to the corresponding cluster.

    For network configuration information, see Public Network configuration.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L2 Network Resources > L2 Network. On the L2 Network page, click Create L2 Network. Then, the Create L2 Network page is displayed. On the displayed page, set the following parameters:

    • Zone: By default, the current zone is displayed.
    • Name: Set the name as L2-Public Network.
    • Description: Optional. Enter a description for the L2 network.
    • Switch Type: Select Linux Bridge.
    • Network Type: Select L2NoVlanNetwork.
    • Cluster: Select a cluster to be attached, for example, Cluster-1.
    • NIC Name: Enter a NIC name for the L2 network. For example, em1.
    Create L2-Public Network
  2. Create an L3 public network.

    For network configuration information, see Public Network configuration.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L3 Network Resources > Public Network. On the Public Network page, click Create Public Network. The Create Public Network page is displayed. On the displayed page, set the following parameters:

    • Name: Set the name as L3-Public Network.

    • Description: Optional. Enter a description for the public network.

    • L2 Network: Select the existing L2-Public Network.

    • Network Address Type: Select IPv4.

    • Network Range Method: Select IP Range.

    • Start IP: Set a start IP address for the network range, for example, 10.108.10.100.

    • End IP: Set an end IP address for the network range, for example, 10.108.10.200.

    • Netmask: Set a netmask for the network range, for example, 255.0.0.0.

    • Gateway: Set a gateway for the network range, for example, 10.0.0.1.

    • IP Allocation Policy: Optional. After the DHCP service is enabled, IP addresses can be assigned according to the following three allocation policies:

      • Random: The system randomly assigns IP addresses from the network range.

      • Allocate in Order:

        • The system assigns all available IP addresses from the network range in ascending order. Released IP addresses are assigned in the next allocation.
        • Example: Assume that the network range is 192.168.0.101~192.168.0.120, within which 192.168.0.101~192.168.0.108 are allocated. If 192.168.0.106 is released, it will be assigned first in the next allocation.
      • Allocate in Cycle:

        • The system assigns available IP addresses to VM instances from the network range in ascending order. Released IP addresses are assigned when currently available IP addresses are used up.
        • Example: Assume that the network range is 192.168.0.101~192.168.0.120, within which 192.168.0.101~192.168.0.108 are allocated. If 192.168.0.106 is released, it will be assigned after 192.168.0.120 is used.
    • DHCP Service: Choose whether to enable the DHCP service.

      • The DHCP service is a built-in distributed service of the Cloud, which assigns IP addresses only to resources in the Cloud and does not conflict with your existing DHCP server.
      • By default, the DHCP service is enabled so that IP addresses are automatically assigned to resources in the Cloud. You can customize a DHCP IP or use the DHCP IP that the system assigned according to the IP allocation policy.
      • If you disable this option, IP addresses are not automatically assigned to resources that use this network. Therefore, you need to manually assign IP addresses to these resources. In addition, you cannot specify a DHCP IP. Neither can the system allocate one.
      • DHCP IP: Optional. Set an IP address for the DHCP server, for example, 10.108.10.101.

        • A DHCP IP is an IP address used by the DHCP service to assign IP addresses to resources that use this L3 network.
        • If you create an L3 network for the first time with the DHCP service enabled, or if you add the first network range to an L3 network with the DHCP service enabled, you can customize the DHCP IP.
        • If the L3 network has a DHCP IP, you cannot customize the DHCP IP when you add a network range.
        • The DHCP IP can be in or outside the added IP range, but it must be an unoccupied IP address in the CIDR block of the added IP range
        • The IP range determined by the start IP and end IP cannot contain the link-local address 169.254.0.0/16.
        • If you select random as the IP allocation policy and this field is left blank, the system randomly assigns IP addresses from the added network range.
        • If you select allocate in order/allocate in cycle as the IP allocation policy and this field is left blank, the system uses the start IP address in the network range as the DHCP IP.
    • DNS: Optional. Add a DNS server to provide domain name resolution services for the public network, for example, 114.114.114.114.

    Create L3-Public Network
  3. Create an L2 management network and attach it to the corresponding cluster.

    For network configuration information, see Management Network Configuration.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L2 Network Resources > L2 Network. On the L2 Network page, click Create L2 Network. Then, the Create L2 Network page is displayed. On the displayed page, set the following parameters:

    • Zone: By default, the current zone is displayed.
    • Name: Set the name as L2-Management Network.
    • Description: Optional. Enter a description for the L2 network.
    • Switch Type: Select Linux Bridge.
    • Network Type: Select L2NoVlanNetwork.
    • Cluster: Select a cluster to be attached, for example, Cluster-1.
    • NIC Name: Enter a NIC name for the L2 network. For example, em2.
    Create L2-Management Network
  4. Create an L3 management network.

    For network configuration information, see Management Network Configuration.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > Dedicated Network > Management Network. On the Management Network page, click Create Management Network. Then, the Create Management Network page is displayed. On the displayed page, set the following parameters:

    • Name: Set the name as L3-Management Network.
    • Description: Optional. Enter a description for the management network.
    • L2 Network: Select the existing L2-Management Network.
    • Network Range Method: Select IP Range.
    • Start IP: Set a start IP address for the network range, for example, 192.168.29.10.
    • End IP: Set an end IP address for the network range, for example, 192.168.29.20.
    • Netmask: Set a netmask for the network range, for example, 255.255.255.0.
    • Gateway: Set a gateway for the network range, for example, 192.168.29.1.
    Create L3-Management Network
  5. Add a vRouter image.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > vRouter > vRouter Image. On the vRouter Image page, click Add vRouter Image. Then, the Add vRouter Image page is displayed.

    Set the following parameters:

    • Name: Enter a name for the vRouter image.

    • Description: Optional. Enter a description for the vRouter image.

    • Image Usage: Display VPC vRouter.

    • CPU Architecture: Select a CPU architecture for the vRouter image. VPC vRouters created from the vRouter image inherit this CPU architecture.

    • OS: Select a OS for the vRouter image. Supported OS types differ depending on the CPU architecture.

    • Image Storage: Select an image storage to store the vRouter image.

    • Image Path: Enter a URL or upload a local file.

      • URL: Enter the download URL of the vRouter image.

      • Local File: Upload a vRouter image file that can directly be accessed by the current browser.

        • You can upload the vRouter image to an ImageStore or Ceph image storage.
        • A local browser will serve as a transmission relay used for uploading the vRouter image. Do not refresh or stop the current browser, nor stop your management node. Otherwise, you will fail to add the vRouter image.
  6. Create a vRouter offering.

    On the displayed page, set the following parameters:

    • Zone: By default, the current zone is displayed.

    • Name: Enter a name for the vRouter offering.

    • Description: Optional. Enter a description for the vRouter offering.

    • CPU: Set the number of CPU cores for a vRouter.

      Currently, a vRouter can have up to 240 CPU cores. In an actual production environment, we recommend that you set more than 8 CPU cores for a vRouter.

    • Memory: Set the memory size for a vRouter. Unit: MB, GB, and TB. In an actual production environment, we recommend that the memory size greater than 8 GB.

    • Image: Select a vRouter image you added before.

      If the L3 public network in the vRouter offering has a network range of the IPv6 type, when you create a VPC vRouter, you must use the vRouter image of version 3.10.0 or later.

    • Management Network: Select an L3 management network you created before.

      • A management network is used by the management node to deploy and configure resources such as hosts and VPC vRouters.
      • If a system network is used to manage physical resources, select the system network as the management network.
      • If you use a public network to manage physical resources, select the public network as the management network.
    • Public Network: Select a public network you created before.

      • vRouters created from this vRouter offering can provide VPC network services.
    Create vRouter Offering
  7. Create a VPC vRouter from the vRouter offering you created in the preceding step.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > vRouter > VPC vRouter. On the VPC vRouter page, click Create VPC vRouter. Then, the Create VPC vRouter page is displayed. On the displayed page, set the following parameters:

    On the displayed page, set the following parameters:

    • Name: Enter a name for the VPC vRouter.

    • Description: Optional. Enter a description for the VPC vRouter.

    • vRouter Offering: Select a vRouter offering you created before.

      A VPC vRouter created from a vRouter offering has a public network and a management network.

      • Enable SR-IOV: Optional. Choose whether to use SR-IOV to pass through a VF NIC to the VPC vRouter as a default public network NIC.

        • By default, SR-IOV is disabled and a vNIC is attached to the VPC vRouter as a public network NIC.

        • If the hardware requirements are satisfied, you can enable SR-IOV to attach a VF NIC to the VPC vRouter as a public network NIC.

        • To enable SR-IOV, ensure the following points:

          • The public network and the management network of the VPC vRouter are deployed separately.
          • The vRouter offering uses an openEuler image.
          • There are available VF NICs based on the physical NICs corresponding to the public network.
    • Cluster: Optional. Specify a cluster for the host on which the VPC vRouter is to be started.

    • Storage Allocation Policy: Specify how the Cloud allocates a primary storage. The following two policies are supported:

      • System Allocation: The Cloud allocates a primary storage according to the preconfigured policy.

      • Custom: Select a primary storage as needed.

        • Primary Storage: Select a primary storage for the VPC vRouter.
    • Host: Optional. Select a host on which the VPC vRouter is started.

    • Default IPv4/IPv6 Address: Optional. Specify a default IP address for the VPC vRouter. If not specified, the Cloud allocates one automatically.

    • Assign Management Network IP: Optional. Assign a management network IP to the VPC vRouter.

      To assign a management network IP, make sure that the management network used by the VPC vRouter is separated from the public network the VPC vRouter uses. If the VPC vRouter uses a same network both as its management network and public network, you cannot assign a management network IP.

    • DNS: Optional. Set the DNS service for the VPC vRouter. If not specified, 223.5.5.5 will be used.

      • You can set an IPv4 DNS or IPv6 DNS as needed. For example, you can set the IPv4 DNS to 223.5.5.5 or IPv6 DNS to 240C::6644.
      • Services in the VPC vRouter can access the public network services via DNS. You can also specify the other DNS address if necessary.
      • For VM instances created by using a VPC network, the DNS is the gateway of the VPC network. The VM traffics are forwarded by a VPC vRouter.
    • CPU Pinning: Associate the virtual CPUs (vCPUs) of a VPC vRouter with host pCPUs stringently and allow you to allocate specific pCPUs for the VPC vRouter, thus improving VPC vRouter performances.

      • Pinning Format

        • In the left input box, set a vCPU range. In the right input box, set a pCPU range. Range format: integer, hyphen(-), and caret (^). Use commas to separate them.
        • The vCPU range depends on the vRouter offering attached to the VPC vRouter.
        • The pCPU range depends on the pCPU quantity of the selected cluster or host.
      • Example: In the left input box, enter 1. In the right input box, enter 0-3,^2. This example indicates that vCPU 1 is stringently associated with pCPU 0, pCPU 1, and pCPU 3, while ^ represents that vCPU 2 is excluded.

    Create VPC vRouter
  8. Create an L2 private network and attach it to the corresponding cluster. This L2 private network is used to create an L3 VPC network (VPC Network-1).

    For network configuration information, see VPC Network-1 Configuration.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L2 Network Resources > L2 Network. On the L2 Network page, click Create L2 Network. Then, the Create L2 Network page is displayed. On the displayed page, set the following parameters:

    • Zone: By default, the current zone is displayed.
    • Name: Set the name as L2-Private Network.
    • Description: Optional. Enter a description for the L2 network.
    • Switch Type: Select Linux Bridge.
    • Network Type: Select L2VlanNetwork.
    • Cluster: Select a cluster to be attached, for example, Cluster-1.
    • VLAN ID: Enter 2800.
    • NIC Name: Enter a NIC name for the L2 network. For example, em1.
    • PVLAN (Isolated): Disable the switch.
    Create L2-Private Network
  9. Create an L3 VPC network (VPC Network-1).

    For network configuration information, see VPC Network-1 Configuration.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L3 Network Resources > VPC Network. On the VPC Network page, click Create VPC Network. The Create VPC Network page is displayed. On the displayed page, set the following parameters:

    • Name: Set the name as VPC Network-1.

    • Description: Optional. Enter a description for the VPC network.

    • L2 Network: Select the existing L2-Private Network.

    • VPC vRouter: Optional. Select the existing VPC vRouter.

    • Network Address Type: Select IPv4.

    • Network Range Method: Select CIDR.

    • CIDR: Set a CIDR block for the VPC network, for example, 192.168.10.0/24.

    • Gateway: Set a gateway for the VPC network, for example, 192.168.10.1.

    • IP Allocation Policy: Optional. After the DHCP service is enabled, IP addresses can be assigned according to the following three allocation policies:

      • Random: The system randomly assigns IP addresses from the network range.

      • Allocate in Order:

        • The system assigns all available IP addresses from the network range in ascending order. Released IP addresses are assigned in the next allocation.
        • Example: Assume that the network range is 192.168.0.101~192.168.0.120, within which 192.168.0.101~192.168.0.108 are allocated. If 192.168.0.106 is released, it will be assigned first in the next allocation.
      • Allocate in Cycle:

        • The system assigns available IP addresses to VM instances from the network range in ascending order. Released IP addresses are assigned when currently available IP addresses are used up.
        • Example: Assume that the network range is 192.168.0.101~192.168.0.120, within which 192.168.0.101~192.168.0.108 are allocated. If 192.168.0.106 is released, it will be assigned after 192.168.0.120 is used.
    • DHCP Service: Choose whether to enable the DHCP service.

      • The DHCP service is a built-in distributed service of the Cloud, which assigns IP addresses only to resources in the Cloud and does not conflict with your existing DHCP server.
      • By default, the DHCP service is enabled so that IP addresses are automatically assigned to resources in the Cloud. You can customize a DHCP IP or use the DHCP IP that the system assigned according to the IP allocation policy.
      • If you disable this option, IP addresses are not automatically assigned to resources that use this network. Therefore, you need to manually assign IP addresses to these resources. In addition, you cannot specify a DHCP IP. Neither can the system allocate one.
      • DHCP IP: Optional. Set an IP address for the DHCP server, for example, 192.168.10.2.

        • A DHCP IP is an IP address used by the DHCP service to assign IP addresses to resources that use this L3 network.
        • If you create an L3 network for the first time with the DHCP service enabled, or if you add the first network range to an L3 network with the DHCP service enabled, you can customize the DHCP IP.
        • If the L3 network has a DHCP IP, you cannot customize the DHCP IP when you add a network range.
        • The DHCP IP can be in or outside the added IP range, but it must be an unoccupied IP address in the CIDR block of the added IP range
        • The IP range determined by the start IP and end IP cannot contain the link-local address 169.254.0.0/16.
        • If you select random as the IP allocation policy and this field is left blank, the system randomly assigns IP addresses from the added network range.
        • If you select allocate in order/allocate in cycle as the IP allocation policy and this field is left blank, the system uses the start IP address in the network range as the DHCP IP.
    • DNS: Optional.

    Create VPC Network-1
  10. Create an L2 private network and attach it to the corresponding cluster. This L2 private network is used to create an L3 VPC network (VPC Network-2).

  11. Create an L3 VPC network (VPC Network-2).

  12. Use VPC Network-1 and VPC Network-2 to create VM-1 and VM-2, respectively.

    On the main menu of ZStack Cloud, choose Resource Center > Resource Pool > Virtual Resource > VM Instance. Click Create VM Instance. Use the existing VPC Network-1 and VPC Network-2 to create VM-1 and VM-2, respectively.

  13. Test the connectivity between VPC Network-1 and VPC Network-2.

    Expected result: VPC Netowrk-1 and VPC Network-2 can communicate with each other.

    To test the connectivity, follow these steps:

    • Log in to VM-1, use the ping command to ping VM-2.

      VM-1 Ping VM-2
    • Log in to VM-2, use the ping command to ping VM-1.

      VM-2 ping VM-1

So far, we have introduced the basic deployment of IPv4 VPC network.

IPv6 Basic Deployment

IPv6, also known as Internet Protocol version 6, with an address length of 128 bits, not only solves the problem of insufficient IPv4 address, but it also clears the barrier for multiple access devices to connect to the Internet. ZStack Cloud VPC network supports IPv6 protocol and this chapter will introduce the basic deployment of IPv6 VPC network in detail.

Assume that the customer environment is as follows:

  1. Public Network

    Public Network Configuration
    NIC em1
    VLAN ID No VLAN
    IP Range 10.108.10.100~10.108.10.200
    Netmask 255.0.0.0
    Gateway 10.0.0.1
    DHCP IP 10.108.10.101

    The public network used to create the VPC vRouter supports both IPv4 and IPv6 networks. In this scenario, we use IPv4 as an example.

  2. Management Network

    Management Network Configuration
    NIC em2
    VLAN ID No VLAN
    IP Range 192.168.29.10~192.168.29.20
    Netmask 255.255.255.0
    Gateway 192.168.29.1
    • The management network used to create the VPC vRouter supports IPv4 network only.
    • For security and stability reasons, we recommend that you deploy an independent management network and separate it from the public networks.
    • The management network we mentioned here is the same as that in ZStack Cloud. That is, the management network is the network used to manage hosts, primary storage, and image storage. If a management network was created before, you can use it directly.
  3. VPC Network-1

    VPC Network Configuration
    NIC em1
    VLAN ID 2800
    IP CIDR 234e:0:4569::/64
    DHCP IP 234e:0:4569::2
  4. VPC Network-2

    VPC Network Configuration
    NIC em1
    VLAN ID 2900
    IP CIDR 234e:0:456a::/64
    DHCP IP 234e:0:456a::2

To deploy a VPC network in the Cloud, follow these steps:

  1. Create an L2 public network and attach it to the corresponding cluster.
  2. Create an L3 public network.
  3. Create an L2 management network and attach it to the corresponding cluster.
  4. Create an L3 management network.
  5. Add a vRouter image.
  6. Create a vRouter offering.
  7. Create a VPC vRouter from the vRouter offering you created in the preceding step.
  8. Create an L2 private network and attach it to the corresponding cluster. This L2 private network is used to create an L3 VPC network.
  9. Create L3 VPC networks and attach it to the VPC vRouter.
  10. Use two VPC networks to create VM instances respectively.
  11. Obtain the IPv6 address of the VM instances.
  12. Test the connectivity between two VPC networks.
  1. Create an L2 public network and attach it to the corresponding cluster.

    For network configuration information, see Public Network Configuration.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L2 Network Resources > L2 Network. On the L2 Network page, click Create L2 Network. Then, the Create L2 Network page is displayed. On the displayed page, set the following parameters:

    • Zone: By default, the current zone is displayed.
    • Name: Set the name as L2-Public Network.
    • Description: Optional. Enter a description for the L2 network.
    • Switch Type: Select Linux Bridge.
    • Network Type: Select L2NoVlanNetwork.
    • Cluster: Select a cluster to be attached, for example, Cluster-1.
    • NIC Name: Enter a NIC name for the L2 network. For example, em1.
    Create L2-Public Network
  2. Create an L3 public network.

    For network configuration information, see Public Network Configuration.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L3 Network Resources > Public Network. On the Public Network page, click Create Public Network. The Create Public Network page is displayed. On the displayed page, set the following parameters:

    • Name: Set the name as L3-Public Network.

    • Description: Optional. Enter a description for the public network.

    • L2 Network: Select the existing L2-Public Network.

    • Network Address Type: Select IPv4.

    • Network Range Method: Select IP Range.

    • Start IP: Set a start IP address for the network range, for example, 10.108.10.100.

    • End IP: Set an end IP address for the network range, for example, 10.108.10.200.

    • Netmask: Set a netmask for the network range, for example, 255.0.0.0.

    • Gateway: Set a gateway for the network range, for example, 10.0.0.1.

    • IP Allocation Policy: Optional. After the DHCP service is enabled, IP addresses can be assigned according to the following three allocation policies:

      • Random: The system randomly assigns IP addresses from the network range.

      • Allocate in Order:

        • The system assigns all available IP addresses from the network range in ascending order. Released IP addresses are assigned in the next allocation.
        • Example: Assume that the network range is 192.168.0.101~192.168.0.120, within which 192.168.0.101~192.168.0.108 are allocated. If 192.168.0.106 is released, it will be assigned first in the next allocation.
      • Allocate in Cycle:

        • The system assigns available IP addresses to VM instances from the network range in ascending order. Released IP addresses are assigned when currently available IP addresses are used up.
        • Example: Assume that the network range is 192.168.0.101~192.168.0.120, within which 192.168.0.101~192.168.0.108 are allocated. If 192.168.0.106 is released, it will be assigned after 192.168.0.120 is used.
    • DHCP Service: Choose whether to enable the DHCP service.

      • The DHCP service is a built-in distributed service of the Cloud, which assigns IP addresses only to resources in the Cloud and does not conflict with your existing DHCP server.
      • By default, the DHCP service is enabled so that IP addresses are automatically assigned to resources in the Cloud. You can customize a DHCP IP or use the DHCP IP that the system assigned according to the IP allocation policy.
      • If you disable this option, IP addresses are not automatically assigned to resources that use this network. Therefore, you need to manually assign IP addresses to these resources. In addition, you cannot specify a DHCP IP. Neither can the system allocate one.
      • DHCP IP: Optional. Set an IP address for the DHCP server, for example, 10.108.10.101.

        • A DHCP IP is an IP address used by the DHCP service to assign IP addresses to resources that use this L3 network.
        • If you create an L3 network for the first time with the DHCP service enabled, or if you add the first network range to an L3 network with the DHCP service enabled, you can customize the DHCP IP.
        • If the L3 network has a DHCP IP, you cannot customize the DHCP IP when you add a network range.
        • The DHCP IP can be in or outside the added IP range, but it must be an unoccupied IP address in the CIDR block of the added IP range
        • The IP range determined by the start IP and end IP cannot contain the link-local address 169.254.0.0/16.
        • If you select random as the IP allocation policy and this field is left blank, the system randomly assigns IP addresses from the added network range.
        • If you select allocate in order/allocate in cycle as the IP allocation policy and this field is left blank, the system uses the start IP address in the network range as the DHCP IP.
    • DNS: Optional. Add a DNS server to provide domain name resolution services for the public network, for example, 114.114.114.114.

  3. Create an L2 management network and attach it to the corresponding cluster.

    For network configuration information, see Management Network Configuration.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L2 Network Resources > L2 Network. On the L2 Network page, click Create L2 Network. Then, the Create L2 Network page is displayed. On the displayed page, set the following parameters:

    • Zone: By default, the current zone is displayed.
    • Name: Set the name as L2-Management Network.
    • Description: Optional. Enter a description for the L2 network.
    • Switch Type: Select Linux Bridge.
    • Network Type: Select L2NoVlanNetwork.
    • Cluster: Select a cluster to be attached, for example, Cluster-1.
    • NIC Name: Enter a NIC name for the L2 network. For example, em2.
  4. Create an L3 management network.

    For network configuration information, see Management Network Configuration.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > Dedicated Network > Management Network. On the Management Network page, click Create Management Network. Then, the Create Management Network page is displayed. On the displayed page, set the following parameters:

    • Name: Set the name as L3-Management Network.
    • Description: Optional. Enter a description for the management network.
    • L2 Network: Select the existing L2-Management Network.
    • Network Range Method: Select IP Range.
    • Start IP: Set a start IP address for the network range, for example, 192.168.29.10.
    • End IP: Set an end IP address for the network range, for example, 192.168.29.20.
    • Netmask: Set a netmask for the network range, for example, 255.255.255.0.
    • Gateway: Set a gateway for the network range, for example, 192.168.29.1.
  5. Add a vRouter image.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > vRouter > vRouter Image. On the vRouter Image page, click Add vRouter Image. Then, the Add vRouter Image page is displayed.

    Set the following parameters:

    • Name: Enter a name for the vRouter image.

    • Description: Optional. Enter a description for the vRouter image.

    • Image Usage: Display VPC vRouter.

    • CPU Architecture: Select a CPU architecture for the vRouter image. VPC vRouters created from the vRouter image inherit this CPU architecture.

    • OS: Select a OS for the vRouter image. Supported OS types differ depending on the CPU architecture.

    • Image Storage: Select an image storage to store the vRouter image.

    • Image Path: Enter a URL or upload a local file.

      • URL: Enter the download URL of the vRouter image.

      • Local File: Upload a vRouter image file that can directly be accessed by the current browser.

        • You can upload the vRouter image to an ImageStore or Ceph image storage.
        • A local browser will serve as a transmission relay used for uploading the vRouter image. Do not refresh or stop the current browser, nor stop your management node. Otherwise, you will fail to add the vRouter image.
  6. Create a vRouter offering.

    On the displayed page, set the following parameters:

    • Zone: By default, the current zone is displayed.

    • Name: Enter a name for the vRouter offering.

    • Description: Optional. Enter a description for the vRouter offering.

    • CPU: Set the number of CPU cores for a vRouter.

      Currently, a vRouter can have up to 240 CPU cores. In an actual production environment, we recommend that you set more than 8 CPU cores for a vRouter.

    • Memory: Set the memory size for a vRouter. Unit: MB, GB, and TB. In an actual production environment, we recommend that the memory size greater than 8 GB.

    • Image: Select a vRouter image you added before.

      If the L3 public network in the vRouter offering has a network range of the IPv6 type, when you create a VPC vRouter, you must use the vRouter image of version 3.10.0 or later.

    • Management Network: Select an L3 management network you created before.

      • A management network is used by the management node to deploy and configure resources such as hosts and VPC vRouters.
      • If a system network is used to manage physical resources, select the system network as the management network.
      • If you use a public network to manage physical resources, select the public network as the management network.
    • Public Network: Select a public network you created before.

      • vRouters created from this vRouter offering can provide VPC network services.
    Create vRouter Offering
  7. Create a VPC vRouter from the vRouter offering you created in the preceding step.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > vRouter > VPC vRouter. On the VPC vRouter page, click Create VPC vRouter. Then, the Create VPC vRouter page is displayed. On the displayed page, set the following parameters:

    • Name: Enter a name for the VPC vRouter.

    • Description: Optional. Enter a description for the VPC vRouter.

    • vRouter Offering: Select a vRouter offering you created before.

    • Cluster: Optional. Specify a cluster for the host on which the VPC vRouter is to be started.

    • Storage Allocation Policy: Specify how the Cloud allocates a primary storage. The following two policies are supported:

      • System Allocation: The Cloud allocates a primary storage according to the preconfigured policy.

      • Custom: Select a primary storage as needed.

        • Primary Storage: Select a primary storage for the VPC vRouter.
    • Host: Optional. Select a host on which the VPC vRouter is started.

    • Default IPv6 Address: Optional. Specify a default IP address for the VPC vRouter. If not specified, the Cloud allocates one automatically.

    • Assign Management Network IP: Optional. Assign a management network IP to the VPC vRouter.

      To assign a management network IP, make sure that the management network used by the VPC vRouter is separated from the public network the VPC vRouter uses. If the VPC vRouter uses a same network both as its management network and public network, you cannot assign a management network IP.

    • DNS: Optional. Set the DNS service for the VPC vRouter. In this scenario, specify 240C::6644.

      • You can set an IPv4 DNS or IPv6 DNS as needed. For example, you can set the IPv4 DNS to 223.5.5.5 or IPv6 DNS to 240C::6644.
      • Services in the VPC vRouter can access the public network services via DNS. You can also specify the other DNS address if necessary.
      • For VM instances created by using a VPC network, the DNS is the gateway of the VPC network. The VM traffics are forwarded by a VPC vRouter.
    • CPU Pinning: Associate the virtual CPUs (vCPUs) of a VPC vRouter with host pCPUs stringently and allow you to allocate specific pCPUs for the VPC vRouter, thus improving VPC vRouter performances.

      • Pinning Format

        • In the left input box, set a vCPU range. In the right input box, set a pCPU range. Range format: integer, hyphen(-), and caret (^). Use commas to separate them.
        • The vCPU range depends on the vRouter offering attached to the VPC vRouter.
        • The pCPU range depends on the pCPU quantity of the selected cluster or host.
      • Example: In the left input box, enter 1. In the right input box, enter 0-3,^2. This example indicates that vCPU 1 is stringently associated with pCPU 0, pCPU 1, and pCPU 3, while ^ represents that vCPU 2 is excluded.

    Create VPC vRouter
  8. Create an L2 private network and attach it to the corresponding cluster. This L2 private network is used to create an L3 VPC network.

    For network configuration information, see VPC Network-1 Configuration.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L2 Network Resources > L2 Network. On the L2 Network page, click Create L2 Network. Then, the Create L2 Network page is displayed. On the displayed page, set the following parameters:

    • Zone: By default, the current zone is displayed.
    • Name: Set the name as L2-VPC-1.
    • Description: Optional. Enter a description for the L2 network.
    • Switch Type: Select Linux Bridge.
    • Network Type: Select L2VlanNetwork.
    • Cluster: Select a cluster to be attached, for example, Cluster-1.
    • VLAN ID: Enter 2800.
    • NIC Name: Enter a NIC name for the L2 network. For example, em1.
    • PVLAN (Isolated): Disable the switch.
    Create L2-VPC-1

    Similarly, Create L2-VPC-2 and attach it to the corresponding cluster.

  9. Create L3 VPC networks and attach it to the VPC vRouter.

    For network configuration information, see VPC Network-1 Configuration.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L3 Network Resources > VPC Network. On the VPC Network page, click Create VPC Network. The Create VPC Network page is displayed. On the displayed page, set the following parameters:

    • Name: Set the name as L3-VPC-1.

    • Description: Optional. Enter a description for the VPC network.

    • L2 Network: Select the existing L2-VPC-1.

    • VPC vRouter: Optional. Select the existing VPC vRouter.

    • Network Address Type: Select IPv6.

    • Network Range Method: Select CIDR.

    • IP Configuration Mode: Select Stateful-DHCP.

      • Stateful-DHCP: The interface address and other parameters are all configured through DHCP. The IP range method supports stateful DHCP.
      • Stateless-DHCP: The interface address is automatically derived from the route advertisement prefix and the interface Mac address. Other parameters are configured through DHCP.
      • SLAAC: The interface address is automatically derived from the prefix of the route advertisement that also contains other parameters.
    • CIDR: Set a CIDR block for the VPC network, for example, 234e:0:4569::/64.

    • DHCP Service: Choose whether to enable the DHCP service.

      • The DHCP service is enabled by default. This service automatically assigns an IP address to a VM instance. You can specify an IP address for the DHCP server. If you do not specify, the system assigns a random IP address for the DHCP server.
      • If you disable the DHCP service, no IP address is automatically assigned to VM instances in the public network. You need to manually configure IP addresses for the VM instances.
      • DHCP IP: Optional. Set an IP address for the DHCP server, for example, 234e:0:4569::2.

        • When you create an L3 network and enable the DHCP service for the first time, or when you add the first network range for an L3 network that has the DHCP service enabled, you can specify an IP address for the DHCP server.
        • If a DHCP IP is specified for an L3 network, you cannot specify another DHCP IP when you add a network range for the network.
        • The DHCP IP must be within the CIDR block and must not be in use.
        • If not specified, the system would randomly specify a DHCP IP within the added IP range for the DHCP server.
        • The first IP address in the CIDR block is predefined as the default gateway and cannot be used as a DHCP server IP.
    • DNS: Provide DNS services for an L3 network. Here, you can specify a DNS address such as 240C::6666.

    Create L3-VPC-1

    Similarly, create L3-VPC-2 and attach it to the VPC vRouter.

  10. Use two VPC networks to create VM instances respectively.

    On the main menu of ZStack Cloud, choose Resource Center > Resource Pool > Virtual Resource > VM Instance. Click Create VM Instance. Use the existing L3-VPC-1 and L3-VPC-2 to create VM-1 and VM-2, respectively.

  11. Obtain the IPv6 address of the VM instances.

    You need to manually obtain the IP address of the IPv6 VM instance. Launch the console of the two VM instances and run the following command to obtain the IP address:

    [root@localhost~]# dhclient -6 eth0  //eth0 indicates the NIC name
    [root@localhost~]# ifconfig

    FE80-started address is the link-local address.

    Obtain IP Address

    In this scenario, the obtained IP addresses are as follows:

    • VM-1 IP address: 234e:0:4569::42:e4a6
    • VM-2 IP address: 234e:0:456a::1a:ebe9
  12. Test the connectivity between two VPC networks.

    Expected result: L3-VPC-1 and L3-VPC-2 can communicate with each other.

    To test the connectivity, follow these steps:

    • Log in to VM-1, use the ping command to ping VM-2.

      VM-1 ping VM-2
    • Log in to VM-2, use the ping command to ping VM-1.

      VM-2 ping VM-1

So far, we have introduced the basic deployment of IPv6 VPC network.

Typical Scenarios

The following lists the typical scenarios of a VPC network:

  • Practice of IPv4+IPv6 dual stack in VPC network.
  • Practice of multi-tenant isolation in VPC network.
  • Practice of multi-web server in VPC network.
  • Practice of multiple public network STS in VPC network.
  • Practice of address pool in VPC network.

IPv4+IPv6 Dual Stack

IPv4+IPv6 dual stack means that one NIC has both IPv4 and IPv6 addresses, combining the advantages of IPv4 and IPv6. With IPv4+IPv6 dual stack, you can customize for different scenarios.

Assume the customer environment is as follows:

  1. Public Network

    Public Network Configuration
    NIC em1
    VLAN ID No VLAN
    IP Range 10.108.10.100~10.108.10.200
    Netmask 255.0.0.0
    Gateway 10.0.0.1
    DHCP IP 10.108.10.101
  2. Management Network

    Management Network Configuration
    NIC em2
    VLAN ID No VLAN
    IP Range 192.168.29.10~192.168.29.20
    Netmask 255.255.255.0
    Gateway 192.168.29.1
    • For security and stability reasons, we recommend that you deploy an independent management network and separate it from the public networks.
    • The management network we mentioned here is the same as that in ZStack Private Cloud. That is, the management network is the network used to manage hosts, primary storages, and backup storages. If a management network was created before, you can use it directly.
  3. VPC Network-1

    VPC Network Configuration
    NIC em1
    VLAN ID 2800
    IP CIDR 192.168.10.0/24
    Gateway 192.168.10.1
    DHCP IP 192.168.10.2
    VPC Network Configuration
    IP CIDR 234e:0:4569::/64
    Gateway 234e:0:4569::1
    DHCP IP 234e:0:4569::2
  4. VPC Network-2

    VPC Network Configuration
    NIC em1
    VLAN ID 2900
    IP CIDR 192.168.11.0/24
    Gateway 192.168.11.1
    DHCP IP 192.168.11.2
    VPC Network Configuration
    IP CIDR 234e:0:456a::/64
    Gateway 234e:0:456a::1
    DHCP IP 234e:0:456a::2

To use IPv4+IPv6 dual stack, follow these steps:

  1. Set up IPv4 network environments.
  2. Add a IPv6 network range.
  3. Reboot the VPC vRouter.
  4. Add a IPv6 DNS.
  5. Create two VM instances using the dual-stack network.
  6. Obtain the IPv6 address of the VM instance.
  7. Test the connectivity among VM instances.
  1. Set up IPv4 network environments.

    Create IPv4 type VPC networks according to IPv4 Basic Deployment. Assume the created VPC networks are L3-VPC-1 and L3-VPC-2. Now, the two VPC networks under the same VPC vRouter are both IPv4 type.

    You can also create a IPv6 flat network and then add a IPv4 network range.

  2. Add a IPv6 network range.

    Add a IPv6 network range to L3-VPC-1 and L3-VPC-2 respectively to set up a IPv4+IPv6 dual-stack network. For IPv6 network configuration information, see Table 12: IPv6 VPC Network-1 configuration and Table 14: IPv6 VPC Network-2 Configuration.

    On the VPC Network page, locate the IPv4 network and click Actions > Add IPv6 Range. On the displayed Add Network Range page, set the following parameters:

    • Network Range Method: Select a method to add a network range for the VPC network. You can select IP Range or CIDR. In this scenario, select IP Range.

    • IP Configuration Mode: Select Stateful-DHCP.

      • Stateful-DHCP: The interface address and other parameters are all configured through DHCP. The IP range method supports stateful DHCP.
      • Stateless-DHCP: The interface address is automatically derived from the route advertisement prefix and the interface Mac address. Other parameters are configured through DHCP.
      • SLAAC: The interface address is automatically derived from the prefix of the route advertisement that also contains other parameters.
    • Start IP: Set a start IP address for the network range, for example, 234e:0:4568::2.

    • End IP: Set an end IP address for the network range, for example, 234e:0:4568:0:ffff:ffff:ffff:ffff.

    • Prefix Length: Set a prefix length for the network range, for example, 64. The prefix length ranges from 64 to 126.

    • Gateway: Set a gateway for the network range, for example, 234e:0:4568::1.

    • DHCP IP: Optional. Set an IP address for the DHCP server, for example, 234e:0:4568::3.

      • When you create an L3 network and enable the DHCP service for the first time, or when you add the first network range for an L3 network that has the DHCP service enabled, you can specify an IP address for the DHCP server.
      • If a DHCP IP is specified for an L3 network, you cannot specify another DHCP IP when you add a network range for the network.
      • The DHCP IP can be within or out of the added IP range. However, the IP address must be within the CIDR block to which the added IP range belongs and must not be in use.
      • The IP range determined by the start IP and end IP cannot contain the link-local address fe80::/10.
      • If not specified, the system would randomly specify a DHCP IP within the added IP range for the DHCP server.
    Add IPv6 Network Range
  3. Reboot the VPC vRouter.

    To add a new type of network range to a VPC network that already has a VPC vRouter attached, you need to reboot the VPC vRouter, otherwise the network may not work as expected.

    On the VPC vRouter page, locate the VPC vRouter and click Actions > Reboot.

  4. Add a IPv6 DNS.

    On the DNS tab of the details page of the VPC vRouter, click Add DNS. On the Add DNS dialogue box, set the following parameters:

    • IP Version: Select IPv6.
    • DNS: Specify a DNS address, for example, 240c::6644.
    Add IPv6 DNS
  5. Create two VM instances using the dual-stack network.

    Create two VM instances using L3-VPC-1 and L3-VPC-2 respectively. In this scenario, we will introduce the creation of VM-dual-stack-1.

    On the main menu of ZStack Cloud, choose Resource Center > Resource Pool > Virtual Resource > VM Instance. Click Create VM Instance. On the displayed Create VM Instance page, set the following parameters:

    • Name: Set the name as VM-dual-stack.
    • Description: Optional. Enter a description for the VM instance.
    • Quantity: Enter 2.
    • Instance Offering: Select an existing instance offering.
    • Image: Select an existing image.
    • Root Disk Offering: Select an existing disk offering for the root volume of the VM instance.
    • Network Configuration: Select the IPv4+IPv6 dual-stack network.
    • User Data: Optional. Inject user-defined parameters or scripts to customize configurations for the VM instance or to accomplish specific tasks.

    Click OK to create two VM instance using the dual-stack network.

  6. Obtain the IPv6 address of the VM instance.

    You need to manually obtain the IP address of the IPv6 VM instance. Launch the console of the two VM instances and run the following command to obtain the IP address:

    [root@localhost~]# dhclient -6 eth0  //eth0 indicates the NIC name
    [root@localhost~]# ifconfig

    FE80-started address is the link-local address.

    Obtain IPv6 Address

    In this scenario, the obtained IP addresses are as follows:

    • VM-dual-stack-1 IPv4 address: 192.168.10.105
    • VM-dual-stack-1 IPv6 address: 234e:0:4569::61:bcf4
    • VM-dual-stack-2 IPv4 address: 192.168.11.250
    • VM-dual-stack-2 IPv6 address: 234e:0:456a::46:7348
  7. Test the connectivity among VM instances.

    To test the connectivity, follow these steps:

    • Log in to VM-dual-stack-1, use IPv4 and IPv6 address respectively to ping VM-dual-stack-2.
    • Log in to VM-dual-stack-2, use IPv4 and IPv6 address respectively to ping VM-dual-stack-1.
    Test Network Connectivity

So far, we have introduced how to use a IPv4+IPv6 dual-stack VPC network.

Multi-Tenant Isolation

You can use VLAN or VXLAN to provide isolation for multiple tenants on layer 2 network.

VLAN VXLAN
  • VLAN supports a maximum of 4096 VLAN IDs, that is a maximum of 4096 isolated tenant networks are provided in a single VLAN network, which is difficult to meet the needs of large-scale cloud computing data centers.
  • The VLAN configuration methods of each switch vendors vary differently.
  • VXLAN can support a maximum of 16 million logical networks for multi-tenant isolation, based on the existing network typology of client’s IDC.
  • VXLAN is an overlay technology that allows for the creation of overlaying L2 networks. The overlay virtualization process can be realized by software or by a VXLAN-enabled switch. You can choose the method as needs.
  • Compared to VLAN, VXLAN has higher performance loss and higher network latency.

This chapter mainly introduces the practice of multi-tenant isolation provided by the VXLAN VPC network.

To set up a VXLAN VPC network for multi-tenant isolation, follow these steps:

  1. Admin creates two sub-accounts (Sub-Account-A and Sub-Account-B).
  2. Admin creates an L2 public network and attaches it to the corresponding cluster.
  3. Admin creates an L3 public network.
  4. Admin creates an L2 management network and attaches it to the corresponding cluster.
  5. Admin creates an L3 management network that is used to communicate with physical resources, such as hosts, primary storage, and image storage.
  6. Admin adds a vRouter image.
  7. Admin creates a vRouter offering and shares it to Sub-Account-A and Sub-Account-B.
  8. Admin creates a VXLAN pool, attaches it to the corresponding cluster, and shares it to Sub-Account-A and Sub-Account-B.
  9. Create VPC vRouters from the vRouter offering using Sub-Account-A and Sub-Account-B respectively, for example, VPC vRouter-A and VPC vRouter-B.
  10. Create two VXLAN networks from the VXLAN pool using Sub-Account-A and Sub-Account-B respectively, for example, L2-VXLAN-A1, L2-VXLAN-A2, L2-VXLAN-B1, and L2-VXLAN-B2.
  11. Create VPC networks using the four VXLAN networks in Sub-Account-A and Sub-Account-B respectively, for example, VPC-A1, VPC-A2, VPC-B1, and VPC-B2.
  12. Create a VM instance in each sub-account using the corresponding VPC networks, for example, VM-A1, VM-A2, VM-B1, and VM-B2.
  13. Test the connectivity among VM instances.
  14. Admin shares the L3 public network to Sub-Account-A and Sub-Account-B.
  15. Create a route table to enable VM-A1 and VM-B1 that are isolated in layer 2 can communicate with each other.
  16. Test the connectivity between VM-A1 and VM-B1.
  • VXLAN pool and VXLAN network together provide configuration for the VXLAN network type.
  • If you create an L2 network of the VxlanNetwork type, you must specify a software SDN-based VXLAN pool. The L2 network must correspond to a VNI in the pool.
  • A VXLAN pool is only a collection of VXLAN networks and cannot be used to create L3 networks. You can L3 networks from L2 VxlanNetworks.

Assume the customer environment is as follows:

  1. Public Network

    Public Network Configuration
    NIC em01
    VLAN ID No VLAN
    IP Range 10.151.10.100~10.151.10.200
    Netmask 255.0.0.0
    Gateway 10.0.0.1
    DHCP IP 10.151.10.101
  2. Management Network

    Management Network Configuration
    NIC em02
    VLAN ID No VLAN
    IP Range 192.168.28.100~192.168.28.200
    Netmask 255.255.255.0
    Gateway 192.168.28.1
    • For security and stability reasons, we recommend that you deploy an independent management network and separate it from the public networks.
    • The management network we mentioned here is the same as that in ZStack Private Cloud. That is, the management network is the network used to manage hosts, primary storages, and backup storages. If a management network was created before, you can use it directly.
  3. VXLAN Pool

    VXLAN Pool Configuration
    VNI Range 20-1200
    VTEP CIDR 192.168.28.1/24
  4. VPC-A1

    VPC Network Configuration
    NIC em01
    IP CIDR 192.168.21.0/24
    Gateway 192.168.21.1
    DHCP IP 192.168.21.2
  5. VPC-A2

    VPC Network Configuration
    NIC em01
    IP CIDR 192.168.22.0/24
    Gateway 192.168.22.1
    DHCP IP 192.168.22.2
  6. VPC-B1

    VPC Network Configuration
    NIC em01
    IP CIDR 192.168.23.0/24
    Gateway 192.168.23.1
    DHCP IP 192.168.23.2
  7. VPC-B2

    VPC Network Configuration
    NIC em01
    IP CIDR 192.168.24.0/24
    Gateway 192.168.24.1
    DHCP IP 192.168.24.2

To create a VXLAN-VPC network, follow these steps:

  1. Admin creates two sub-accounts (Sub-Account-A and Sub-Account-B).

    On the main menu of ZStack Cloud, choose Settings > Sub-Account Setting > Sub-Account Management. On the Sub-Account page, click Create Sub-Account. Then, the Create Sub-Account page is displayed. On the displayed page, set the following parameters:

    • Name: Enter a name for the sub-account, for example, Sub-Account-A.
    • Description: Optional. Enter a description for the sub-account.
    • Password: Enter a password for the sub-account.
    • Confirm Password: Confirm the sub-account password.
    • Pricing List: Optional. Select a pricing list. If left blank, the default pricing list is used.
    Create Sub-Account

    Similarly, create another sub-account named as Sub-Account-B.

    Create Sub-Account
  2. Admin creates an L2 public network and attaches it to the corresponding cluster.

    For network configuration information, see Public Network Configuration.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L2 Network Resources > L2 Network. On the L2 Network page, click Create L2 Network. Then, the Create L2 Network page is displayed. On the displayed page, set the following parameters:

    • Zone: By default, the current zone is displayed.
    • Name: Set the name as L2-Public Network.
    • Description: Optional. Enter a description for the L2 network.
    • Switch Type: Select Linux Bridge.
    • Network Type: Select L2NoVlanNetwork.
    • Cluster: Select a cluster to be attached, for example, Cluster-1.
    • NIC Name: Enter a NIC name for the L2 network. For example, em01.
    Create L2-Public Network
  3. Admin creates an L3 public network.

    For network configuration information, see Public Network Configuration.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L3 Network Resources > Public Network. On the Public Network page, click Create Public Network. The Create Public Network page is displayed. On the displayed page, set the following parameters:

    • Name: Set the name as L3-Public Network.

    • Description: Optional. Enter a description for the public network.

    • L2 Network: Select the existing L2-Public Network.

      ZStack Cloud allows you to use an L2 network to create multiple L3 networks. However, we recommend that you do not use an L2 network to create multiple L3 networks if not for specific business needs.

      On the Select L2 Network page, two tabs are displayed:

      • Recommended: lists L2 networks in the current zone that are not attached to an L3 network.
      • All: lists all L2 networks in the current zone.
    • Network Address Type: Select IPv4.

    • Network Range Method: Select IP Range.

    • Start IP: Set a start IP address for the network range, for example, 10.151.10.100.

    • End IP: Set an end IP address for the network range, for example, 10.151.10.200.

    • Netmask: Set a netmask for the network range, for example, 255.0.0.0.

    • Gateway: Set a gateway for the network range, for example, 10.0.0.1.

    • DHCP Service: Choose whether to enable the DHCP service.

      • The DHCP service is a built-in distributed service of the Cloud, which assigns IP addresses only to resources in the Cloud and does not conflict with your existing DHCP server.
      • By default, the DHCP service is enabled so that IP addresses are automatically assigned to resources in the Cloud. You can customize a DHCP IP or use the DHCP IP that the system assigned according to the IP allocation policy.
      • If you disable this option, IP addresses are not automatically assigned to resources that use this network. Therefore, you need to manually assign IP addresses to these resources. In addition, you cannot specify a DHCP IP. Neither can the system allocate one.
      • IP Allocation Policy: Optional. IP addresses can be assigned according to the following three allocation policies:

        • Random: The system randomly assigns IP addresses from the network range.

        • Allocate in Order:

          • The system assigns all available IP addresses from the network range in ascending order. Released IP addresses are assigned in the next allocation.
          • Example: Assume that the network range is 192.168.0.101~192.168.0.120, within which 192.168.0.101~192.168.0.108 are allocated. If 192.168.0.106 is released, it will be assigned first in the next allocation.
        • Allocate in Cycle:

          • The system assigns available IP addresses to VM instances from the network range in ascending order. Released IP addresses are assigned when currently available IP addresses are used up.
          • Example: Assume that the network range is 192.168.0.101~192.168.0.120, within which 192.168.0.101~192.168.0.108 are allocated. If 192.168.0.106 is released, it will be assigned after 192.168.0.120 is used.
      • DHCP IP: Optional. Set an IP address for the DHCP server.

        • A DHCP IP is an IP address used by the DHCP service to assign IP addresses to resources that use this L3 network.
        • If you create an L3 network for the first time with the DHCP service enabled, or if you add the first network range to an L3 network with the DHCP service enabled, you can customize the DHCP IP.
        • If the L3 network has a DHCP IP, you cannot customize the DHCP IP when you add a network range.
        • The DHCP IP can be in or outside the added IP range, but it must be an unoccupied IP address in the CIDR block of the added IP range
        • The IP range determined by the start IP and end IP cannot contain the link-local address 169.254.0.0/16.
        • If you select random as the IP allocation policy and this field is left blank, the system randomly assigns IP addresses from the added network range.
        • If you select allocate in order/allocate in cycle as the IP allocation policy and this field is left blank, the system uses the start IP address in the network range as the DHCP IP.
    • DNS: Optional. Add a DNS server to provide domain name resolution services for the public network, for example, 223.5.5.5.

      When you add an IP range for an IPv4 L3 network, note that:

      • The IP range cannot contain gateway IP addresses in the format of xxx.xxx.xxx.1, broadcast addresses in the format of xxx.xxx.xxx.255, or network addresses in the format of xxx.xxx.xxx.0.
      • The IP range of a private network cannot overlap with the IP range of a public network used to create a vRouter offering or of a management network.
    Create L3-Public Network
  4. Admin creates an L2 management network and attaches it to the corresponding cluster.

    For network configuration information, see Management Network Configuration.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L2 Network Resources > L2 Network. On the L2 Network page, click Create L2 Network. Then, the Create L2 Network page is displayed. On the displayed page, set the following parameters:

    • Zone: By default, the current zone is displayed.
    • Name: Set the name as L2-Management Network.
    • Description: Optional. Enter a description for the L2 network.
    • Switch Type: Select Linux Bridge.
    • Network Type: Select L2NoVlanNetwork.
    • Cluster: Select a cluster to be attached, for example, Cluster-1.
    • NIC Name: Enter a NIC name for the L2 network. For example, em02.
    Create L2-Management Network
  5. Admin creates an L3 management network that is used to communicate with physical resources, such as hosts, primary storage, and image storage.

    For network configuration information, see Management Network Configuration.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > Dedicated Network > Management Network. On the Management Network page, click Create Management Network. Then, the Create Management Network page is displayed. On the displayed page, set the following parameters:

    • Name: Set the name as L3-Management Network.

    • Description: Optional. Enter a description for the management network.

    • L2 Network: Select the existing L2-Management Network.

      ZStack Cloud allows you to use an L2 network to create multiple L3 networks. However, we recommend that you do not use an L2 network to create multiple L3 networks if not for specific business needs.

      On the Select L2 Network page, two tabs are displayed:

      • Recommended: lists L2 networks in the current zone that are not attached to an L3 network.
      • All: lists all L2 networks in the current zone.
    • Network Range Method: Select IP Range.

    • Start IP:Set a start IP address for the network range, for example, 192.168.28.100.

    • End IP: Set an end IP address for the network range, for example, 192.168.28.200.

    • Netmask: Set a netmask for the network range, for example, 255.255.255.0.

    • Gateway: Set a gateway for the network range, for example, 192.168.28.1.

    • When you add an IP range for an IPv4 L3 network, note that:

      • The IP range cannot contain gateway IP addresses in the format of xxx.xxx.xxx.1, broadcast addresses in the format of xxx.xxx.xxx.255, or network addresses in the format of xxx.xxx.xxx.0.
      • The IP range of a private network cannot overlap with the IP range of a public network used to create a vRouter offering or of a management network.
    Create L3-Management Network
  6. Admin adds a vRouter image.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > vRouter > vRouter Image. On the vRouter Image page, click Add vRouter Image. Then, the Add vRouter Image page is displayed.

    Set the following parameters:

    • Name: Enter a name for the vRouter image.

    • Description: Optional. Enter a description for the vRouter image.

    • Image Usage: Display VPC vRouter.

    • CPU Architecture: Select a CPU architecture for the vRouter image. VPC vRouters created from the vRouter image inherit this CPU architecture.

    • OS: Select a OS for the vRouter image. Supported OS types differ depending on the CPU architecture.

    • Image Storage: Select an image storage to store the vRouter image.

    • Image Path: Enter a URL or upload a local file.

      • URL: Enter the download URL of the vRouter image.

      • Local File: Upload a vRouter image file that can directly be accessed by the current browser.

        • You can upload the vRouter image to an ImageStore or Ceph image storage.
        • A local browser will serve as a transmission relay used for uploading the vRouter image. Do not refresh or stop the current browser, nor stop your management node. Otherwise, you will fail to add the vRouter image.
  7. Admin creates a vRouter offering and shares it to Sub-Account-A and Sub-Account-B.

    1. Create a vRouter offering.

      On the displayed page, set the following parameters:

      • Zone: By default, the current zone is displayed.

      • Name: Enter a name for the vRouter offering.

      • Description: Optional. Enter a description for the vRouter offering.

      • CPU: Set the number of CPU cores for a vRouter.

        Currently, a vRouter can have up to 240 CPU cores. In an actual production environment, we recommend that you set more than 8 CPU cores for a vRouter.

      • Memory: Set the memory size for a vRouter. Unit: MB, GB, and TB. In an actual production environment, we recommend that the memory size greater than 8 GB.

      • Image: Select a vRouter image you added before.

        If the L3 public network in the vRouter offering has a network range of the IPv6 type, when you create a VPC vRouter, you must use the vRouter image of version 3.10.0 or later.

      • Management Network: Select an L3 management network you created before.

        • A management network is used by the management node to deploy and configure resources such as hosts and VPC vRouters.
        • If a system network is used to manage physical resources, select the system network as the management network.
        • If you use a public network to manage physical resources, select the public network as the management network.
      • Public Network: Select a public network you created before.

        • vRouters created from this vRouter offering can provide VPC network services.
      Create vRouter Offering
    2. Share the vRouter offering to Sub-Account-A and Sub-Account-B.

      On the main menu of ZStack Cloud, choose Resource Center > Network Resource > vRouter > vRouter Offering. On the vRouter Offering page, locate the vRouter offering and click Actions > Set Sharing Mode. On the Set Sharing Mode dialogue box, select Share to specified projects/accounts and select Sub-Account-A and Sub-Account-B in Specify Account.

      Set Sharing Mode
  8. Admin creates a VXLAN pool, attaches it to the corresponding cluster, and shares it to Sub-Account-A and Sub-Account-B.

    1. Create a VXLAN pool.

      For VXLAN pool configuration information, see VXLAN Pool Configuration.

      On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L2 Network Resources > VXLAN Pool. On the VXLAN Pool page, click Create VXLAN Pool. Then, the Create VXLAN Pool page is displayed. On the displayed page, set the following parameters:

      • Zone: By default, the current zone is displayed.

      • Name: Enter a name for the VXLAN pool.

      • Description: Optional. Enter a description for the VXLAN pool.

      • SDN Type: Select Software.

      • VNI Range: Enter the start ID and end ID of VXLAN networks.

        • You can enter an ID that ranges from 1 to 16777214.
        • The end ID must be equal to or greater than the start ID.
        • The two VNI IDs 16777215 and 16777216 are reserved by the system of this cloud platform.
      • Cluster: Optional. Attach the VXLAN pool to a cluster.

        • You can attach a VXLAN pool to a cluster when you create the VXLAN pool or after the VXLAN pool is created.
        • When you attach the VXLAN pool to a cluster, IP addresses of the compute nodes must be available in the cluster that correspond to the VTEP CIDR block.
      • VTEP CIDR: Enter the corresponding VTEP CIDR block.

      Create VXLAN Pool
    2. Share the VXLAN pool to Sub-Account-A and Sub-Account-B.

      On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L2 Network Resources > VXLAN Pool. On the VXLAN Pool page, locate the VXLAN pool and click Actions > Set Sharing Mode. On the Set Sharing Mode dialogue box, select Share to specified projects/accounts and select Sub-Account-A and Sub-Account-B in Specify Account.

      Set Sharing Mode
  9. Create VPC vRouters from the vRouter offering using Sub-Account-A and Sub-Account-B respectively, for example, VPC vRouter-A and VPC vRouter-B.

    Log in to the Cloud using Sub-Account-A. On the main menu of ZStack Cloud, choose Resource Center > Network Resource > vRouter > VPC vRouter. On the VPC vRouter page, click Create VPC vRouter. Then, the Create VPC vRouter page is displayed. On the displayed page, set the following parameters:

    • Name: Enter a name for the VPC vRouter.

    • Description: Optional. Enter a description for the VPC vRouter.

    • vRouter Offering: Select a vRouter offering you created before.

    • Cluster: Optional. Specify a cluster for the host on which the VPC vRouter is to be started.

    • Storage Allocation Policy: Specify how the Cloud allocates a primary storage. The following two policies are supported:

      • System Allocation: The Cloud allocates a primary storage according to the preconfigured policy.

      • Custom: Select a primary storage as needed.

        • Primary Storage: Select a primary storage for the VPC vRouter.
    • Host: Optional. Select a host on which the VPC vRouter is started.

    • Default IPv4/IPv6 Address: Optional. Specify a default IP address for the VPC vRouter. If not specified, the Cloud allocates one automatically.

    • Assign Management Network IP: Optional. Assign a management network IP to the VPC vRouter.

      To assign a management network IP, make sure that the management network used by the VPC vRouter is separated from the public network the VPC vRouter uses. If the VPC vRouter uses a same network both as its management network and public network, you cannot assign a management network IP.

    • DNS: Optional. Set the DNS service for the VPC vRouter. If not specified, 223.5.5.5 will be used.

      • You can set an IPv4 DNS or IPv6 DNS as needed. For example, you can set the IPv4 DNS to 223.5.5.5 or IPv6 DNS to 240C::6644.
      • Services in the VPC vRouter can access the public network services via DNS. You can also specify the other DNS address if necessary.
      • For VM instances created by using a VPC network, the DNS is the gateway of the VPC network. The VM traffics are forwarded by a VPC vRouter.
    • CPU Pinning: Associate the virtual CPUs (vCPUs) of a VPC vRouter with host pCPUs stringently and allow you to allocate specific pCPUs for the VPC vRouter, thus improving VPC vRouter performances.

      • Pinning Format

        • In the left input box, set a vCPU range. In the right input box, set a pCPU range. Range format: integer, hyphen(-), and caret (^). Use commas to separate them.
        • The vCPU range depends on the vRouter offering attached to the VPC vRouter.
        • The pCPU range depends on the pCPU quantity of the selected cluster or host.
      • Example: In the left input box, enter 1. In the right input box, enter 0-3,^2. This example indicates that vCPU 1 is stringently associated with pCPU 0, pCPU 1, and pCPU 3, while ^ represents that vCPU 2 is excluded.

    Create VPC vRouter-A

    Similarly, log in to the Cloud using Sub-Account-B and create another VPC vRouter.

  10. Create two VXLAN networks from the VXLAN pool using Sub-Account-A and Sub-Account-B respectively, for example, L2-VXLAN-A1, L2-VXLAN-A2, L2-VXLAN-B1, and L2-VXLAN-B2.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L2 Network Resources > L2 Network. On the L2 Network page, click Create L2 Network. Then, the Create L2 Network page is displayed. On the displayed page, set the following parameters:

    • Zone: By default, the current zone is displayed.

    • Name: Set the name as L2-VXLAN-A1.

    • Description: Optional. Enter a description for the L2 network.

    • Switch Type: Select Linux Bridge.

    • Network Type: Select VxlanNetwork.

    • VXLAN Pool: Select a VXLAN pool of the software SDN type.

    • VNI: Optional. Select a specified VNI in the VXLAN pool.

      If not specified, the Cloud allocates a VNI randomly.

    Create L2-VXLAN-A1

    Similarly, create L2-VXLAN-A2, L2-VXLAN-B1, and L2-VXLAN-B2 respectively.

  11. Create VPC networks using the four VXLAN networks in Sub-Account-A and Sub-Account-B respectively, for example, VPC-A1, VPC-A2, VPC-B1, and VPC-B2.

    For VPC network configuration information, see VPC-A1 Configuration.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L3 Network Resources > VPC Network. On the VPC Network page, click Create VPC Network. The Create VPC Network page is displayed. On the displayed page, set the following parameters:

    • Name: Set the name as VPC-A1.

    • Description: Optional. Enter a description for the VPC network.

    • L2 Network: Select the existing L2-VXLAN-A1.

      On the Select L2 Network page, two tabs are displayed:

      • Recommended: lists L2 networks in the current zone that are not attached to an L3 network.
      • All: lists all L2 networks in the current zone.
    • VPC vRouter: Optional. You can specify a VPC vRouter when you create a VPC network or attach a VPC vRouter after you create the VPC network.

    • Network Address Type: Select IPv4.

    • Network Range Method: Select CIDR.

    • CIDR: Set a CIDR block for the VPC network, for example, 192.168.108.1/24.

    • Gateway: Set a gateway for the VPC network, for example, 192.168.108.1.

      • You can use the first or last IP address in the specified CIDR block as the gateway.
      • If left blank, the first IP address in the specified CIDR block is used as the gateway.
    • DHCP Service: Choose whether to enable the DHCP service.

      • The DHCP service is a built-in distributed service of the Cloud, which assigns IP addresses only to resources in the Cloud and does not conflict with your existing DHCP server.
      • By default, the DHCP service is enabled so that IP addresses are automatically assigned to resources in the Cloud. You can customize a DHCP IP or use the DHCP IP that the system assigned according to the IP allocation policy.
      • If you disable this option, IP addresses are not automatically assigned to resources that use this network. Therefore, you need to manually assign IP addresses to these resources. In addition, you cannot specify a DHCP IP. Neither can the system allocate one.
      • IP Allocation Policy: Optional. After the DHCP service is enabled, IP addresses can be assigned according to the following three allocation policies:

        • Random: The system randomly assigns IP addresses from the network range.

        • Allocate in Order:

          • The system assigns all available IP addresses from the network range in ascending order. Released IP addresses are assigned in the next allocation.
          • Example: Assume that the network range is 192.168.0.101~192.168.0.120, within which 192.168.0.101~192.168.0.108 are allocated. If 192.168.0.106 is released, it will be assigned first in the next allocation.
        • Allocate in Cycle:

          • The system assigns available IP addresses to VM instances from the network range in ascending order. Released IP addresses are assigned when currently available IP addresses are used up.
          • Example: Assume that the network range is 192.168.0.101~192.168.0.120, within which 192.168.0.101~192.168.0.108 are allocated. If 192.168.0.106 is released, it will be assigned after 192.168.0.120 is used.
      • DHCP IP: Optional. Set an IP address for the DHCP server, for example, 192.168.21.2.

        • A DHCP IP is an IP address used by the DHCP service to assign IP addresses to resources that use this L3 network.
        • If you create an L3 network for the first time with the DHCP service enabled, or if you add the first network range to an L3 network with the DHCP service enabled, you can customize the DHCP IP.
        • If the L3 network has a DHCP IP, you cannot customize the DHCP IP when you add a network range.
        • The DHCP IP can be in or outside the added IP range, but it must be an unoccupied IP address in the CIDR block of the added IP range
        • The IP range determined by the start IP and end IP cannot contain the link-local address 169.254.0.0/16.
        • If you select random as the IP allocation policy and this field is left blank, the system randomly assigns IP addresses from the added network range.
        • If you select allocate in order/allocate in cycle as the IP allocation policy and this field is left blank, the system uses the start IP address in the network range as the DHCP IP.
    • DNS: Optional.

    Create VPC-A1

    Similarly, create VPC-A2, VPC-B1, and VPC-B2 respectively.

  12. Create a VM instance in each sub-account using the corresponding VPC networks, for example, VM-A1, VM-A2, VM-B1, and VM-B2.

    As for how to create a VM instance, you can refer to the Create VM Instance chapter of the User Guide.

  13. Test the connectivity among VM instances.

    1. Log in to VM-A1 and use the ping command to test the network connectivity:

      Expected result:

      • ping baidu.com: Successful
      • ping VM-A2: Successful
      • ping VM-B1: Failed (Two VXLAN-VPC network are isolated in layer 2)
      • ping VM-B2: Failed (Two VXLAN-VPC network are isolated in layer 2)

      In VM-A1 system, you need to manually add the IP addresses of other VM instances to the /etc/hosts directory.

      [root@Localhost~]# vim /etc/hosts
      ...
      192.168.22.156 VM-A2
      192.168.23.177 VM-B1
      192.168.24.193 VM-B2
      ...
      Test VM-A1 Network Connectivity
    2. Similarly, the network connectivity of VM-A2 is expected the be the same as that of VM-A1.

    3. Log in to VM-B1 and use the ping command to test the network connectivity.

      Expected result:

      • ping baidu.com: Successful
      • ping VM-A1: Failed (Two VXLAN-VPC network are isolated in layer 2)
      • ping VM-A2: Failed (Two VXLAN-VPC network are isolated in layer 2)
      • ping VM-B2: Successful

      In VM-B1 system, you need to manually add the IP addresses of other VM instances to the /etc/hosts directory.

      [root@Localhost~]# vim /etc/hosts
      ...
      192.168.21.250 VM-A1
      192.168.22.156 VM-A2
      192.168.24.193 VM-B2
      ...
      Test VM-B2 Network Connectivity
    4. Similarly, the network connectivity of VM-B2 is expected the be the same as that of VM-B1.

  14. Admin shares the L3 public network to Sub-Account-A and Sub-Account-B.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L3 Network Resources > Public Network. On the Public Network page, locate the L3-Public Network and click Actions > Set Sharing Mode. On the Set Sharing Mode dialogue box, select Share to specified projects/accounts and select Sub-Account-A and Sub-Account-B in Specify Account.

    Set Sharing Mode
  15. Create a route table to enable VM-A1 and VM-B1 that are isolated in layer 2 can communicate with each other.

    1. Create a route table.

      On the main menu of ZStack Cloud, choose Resource Center > Network Service > Advanced Network Service > Route Table. On the Route Table page, click Create Route Table. Then, the Create Route Table page is displayed.

      On the displayed page, set the following parameters:

      • Name: Enter a name for the route table.
      • Description: Optional. Enter a description for the route table.
      • VPC vRouter: Optional. Select a VPC vRouter to which the route table is attached.
      Create Route Table
    2. Add two route entries to the route table.

      Destination Network Next Hop
      Route Entry-1 The VPC network CIDR of VM-A1 The public IP of the VPC vRouter of VM-A1
      Route Entry-2 The VPC network CIDR of VM-B1 The public IP of the VPC vRouter of VM-B1

      On the Route Table page, locate the created route table and enter its details page. On the Route Entry tab of the details page, click Add Route Entry to add two route entries respectively.

      Add Route Entry
  16. Test the connectivity between VM-A1 and VM-B1.

    Expected result:

    • Log in to VM-A1, ping VM-B1: Successful
    • Log in to VM-B1, ping VM-A2: Successful
    Test Connectivity Between VM-A1 and VM-B1
    Test Connectivity Between VM-A1 and VM-B1 (2)

So far, we have introduced the deployment practice of multi-tenant isolation in VPC network.

Multi-Web Server

To deploy a multi-web server of VPC network, follow these steps:

  1. Create three VPC subnets from the same VPC vRouter, for example, VPC-Web, VPC-app, and VPC-database.

    The network range of the three VPC subnets cannot overlap with one another.

  2. Create three VM instances using the three VPC subnets respectively, for example, VM-web, VM-app, and VM-database.

  3. Test the network connectivity among three VM instances.

Assume the customer environment is as follows:

  1. Public Network

    Public Network Configuration
    NIC em01
    VLAN ID No VLAN
    IP Range 10.151.10.100~10.151.10.200
    Netmask 255.0.0.0
    Gateway 10.0.0.1
  2. Management Network

    Management Network Configuration
    NIC em02
    VLAN ID No VLAN
    IP Range 192.168.28.100~192.168.28.200
    Netmask 255.255.255.0
    Gateway 192.168.28.1
    • For security and stability reasons, we recommend that you deploy an independent management network and separate it from the public networks.
    • The management network we mentioned here is the same as that in ZStack Cloud. That is, the management network is the network used to manage hosts, primary storage, and image storage. If a management network was created before, you can use it directly.
  3. VPC-web

    Private Network Configuration
    NIC em01
    VLAN ID 2017
    IP CIDR 192.168.10.0/24
  4. VPC-app

    Private Network Configuration
    NIC em01
    VLAN ID 2020
    IP CIDR 192.168.20.0/24
  5. VPC-database

    Private Network Configuration
    NIC em01
    VLAN ID 2050
    IP CIDR 192.168.50.0/24

The following part describes the practice of deploying a multi-web server of VPC network in detail.

  1. Create three VPC subnets from the same VPC vRouter, for example, VPC-Web, VPC-app, and VPC-database. For detailed information, you can refer to the Create VPC Network chapter of User Guide.

    The network range of the three VPC subnets cannot overlap with one another.

    Three VPC Subnets
  2. Create three VM instances using the three VPC subnets respectively, for example, VM-web, VM-app, and VM-database.

    Three VM Instances
  3. Test the network connectivity among three VM instances.

    1. Log in to VM-web and use the ping command to test network connectivity.

      Expected result:

      • ping baidu.com: Successful
      • ping VM-app: Successful
      • ping VM-database: Successful

      In VM-web system, you need to manually add the IP addresses of VM-app and VM-database to the /etc/hosts directory.

      [root@VM-web ~]# vim /etc/hosts
      ...
      192.168.20.187 VM-app
      192.168.50.141 VM-database
      ...
      Test VM-web Network Connectivity
    2. Log in to VM-app and use the ping command to test network connectivity.

      Expected result:

      • ping baidu.com: Successful
      • ping VM-web: Successful
      • ping VM-database: Successful

      In VM-app system, you need to manually add the IP addresses of VM-web and VM-database to the /etc/hosts directory.

      [root@VM-app ~]# vim /etc/hosts
      ...
      192.168.10.79 VM-web
      192.168.50.141 VM-database
      ...
      Test VM-app Network Connectivity
    3. Log in to VM-database and use the ping command to test network connectivity.

      Expected result:

      • ping baidu.com: Successful
      • ping VM-app: Successful
      • ping VM-web: Successful

      In VM-database system, you need to manually add the IP addresses of VM-app and VM-web to the /etc/hosts directory.

      [root@VM-database ~]# vim /etc/hosts
      ...
      192.168.20.187 VM-app
      192.168.10.79 VM-web
      ...
      Test VM-database Network Connectivity

So far, we have introduced the practice of deploying a multi-web server.

STS

STS: If a VPC vRouter is connected with multiple public networks, egress traffic is sent to a public network in the same route as the ingress traffic sent from the public network.

  • Make sure that all planned public networks are able to connecting to the Internet.
  • Effectiveness: This policy takes effect on all public networks that are connected with the VPC vRouter except the default public network.

To use the STS feature of a VPC vRouter, follow these steps:

  1. Set up a basic VPC environment.
  2. Attach multiple public networks to the VPC vRouter.
  3. Enable the STS feature of VPC vRouter.
  4. Functional verification.

Assume the customer environment configuration is as follows:

  1. Public Network-Unicom (Default Public Network)

    Public Network Configuration
    NIC eth1
    VLAN ID No VLAN
    CIDR 172.31.5.0/24
  2. Public Network-Mobile

    Public Network Configuration
    NIC eth3
    VLAN ID No VLAN
    CIDR 172.31.4.0/24
  3. Management Network

    Management Network Configuration
    NIC eth2
    VLAN ID No VLAN
    CIDR 10.5.117.0/24
    • For security and stability reasons, we recommend that you deploy an independent management network and separate it from the public networks.
    • The management network we mentioned here is the same as that in ZStack Cloud. That is, the management network is the network used to manage hosts, primary storage, and image storage. If a management network was created before, you can use it directly.
  4. VPC-1

    VPC-1 Configuration
    NIC eth1
    VLAN ID 1982
    IP CIDR 192.168.3.0/24
  5. VPC-2

    VPC-2 Configuration
    NIC eth3
    VLAN ID 1983
    IP CIDR 192.168.4.0/24

The following part describes the practice of deploying a multiple public networks of VPC vRouter.

  1. Set up a basic VPC environment.

    Set up a basic VPC environment according to the assumed customer environment configuration.

    The basic environment supports adding one public network to the VPC vRouter. In this scenario, we use Public Network-Unicom as the default public network. You can create Public Network-Mobile in advance for later use.

    Set up Basic VPC Environment
  2. Attach multiple public networks to the VPC vRouter.

    On the Network tab of the details page, click Public Network. Then, click Attach to attach a public network (Public Network-Mobile) to the VPC vRouter.

    Attach Public Network to VPC vRouter
  3. Enable the STS feature of VPC vRouter.

    On the details page of the VPC vRouter, turn on the STS switch to enable the STS feature.

    Modifications on the policy take effect immediately. You do not need to restart the VPC vRouter.

    Enable STS

    At this point, the STS configuration of the VPC vRouter is completed. And all external traffic accesses to the resources of the VPC vRouter will support STS.

  4. Functional verification.

    Create a VM instance using the VPC network and associate EIPs created from the two public network. Use external network to ping the EIP created from non-default public network (Public Network-Mobile).

    Expected result: Monitor the two NICs (eth1 and eth3) of the VPC vRouter and only the NIC (eth3) of the non-default public network can receive the requested return data.

    1. Create a VM instance for test.

      On the VM Instance page, create a VM instance using VPC-1 or VPC-2.

    2. Create EIPs and associate them with the VM instance.

      Create EIPs using Public Network-Unicom and Public Network-Mobile respectively and associate them with the VM instance.

      Create and Associate EIPs
    3. Monitor data flow direction.

      Use external network to ping the EIP of the VM instance, for example, 172.31.4.18. The requested data goes through the eth3 NIC of the VPC vRouter.

      External Excess to VM Instance

      Log in to the VPC vRouter, use the tcpdump command to monitor the data traffic of the two public network NICs. The returned data only goes through the eth3, which is the same NIC that gives the request.

      Monitor Returned Data

Address Pool

An address pool network range must co-exist with a normal network range. An address pool network range can be only used to create VIPs to provide network services based on VPC vRouters.

To add an address pool, follow these steps:

  1. Plan your network.
  2. Create a public network.
  3. Add an address pool.
  4. Create a VIP using the address pool.
  5. Test whether the VIP works properly.

The following tables list the user’s assumed environment configuration.

  1. Public Network (Normal Network Range)

    Public Network Configuration
    NIC em01
    VLAN ID No VLAN
    CIDR 10.151.0.0~10.151.0.255
    Netmask 255.0.0.0
    Gateway 10.151.0.1
  2. Public Network (Address Pool)

    Address Pool Configuration
    IP Range 172.20.0.1~172.20.0.254
    Netmask 255.255.0.0

The following section describes the detailed steps of how to use an address pool.

  1. Plan your network.

    IPv4 public networks support address pool. Make sure that the address pool network range is planned and configured as a public network. Otherwise, the network is unreachable.

    We recommend that you plan your network according to the actual scenarios and make relevant configurations in key switches.

  2. Create a public network.

    1. Create an L2 network.

      On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L2 Network Resources > L2 Network. On the L2 Network page, click Create L2 Network. Then, the Create L2 Network page is displayed. On the displayed page, set the following parameters:

      • Zone: By default, the current zone is displayed.
      • Name: Set the name as L2- Public Network.
      • Description: Optional. Enter a description for the L2 network.
      • Switch Type: Select Linux Bridge.
      • Network Type: Select L2NoVlanNetwork.
      • Cluster: Optional. Select the cluster to be attached, for example, Cluster-1.
      • NIC Name: Enter a NIC name for the L2 network. For example, em01.
      Create L2-Public Network
    2. Create an L3 public network.

      On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L3 Network Resources > Public Network. On the Public Network page, click Create Public Network. The Create Public Network page is displayed. On the displayed page, set the following parameters:

      • Name: Enter a name for the public network.

      • Description: Optional. Enter a description for the public network.

      • L2 Network: Select an L2 network for the public network.

        ZStack Cloud allows you to use an L2 network to create multiple L3 networks. However, we recommend that you do not use an L2 network to create multiple L3 networks if not for specific business needs.

        On the Select L2 Network page, two tabs are displayed:

        • Recommended: lists L2 networks in the current zone that are not attached to an L3 network.
        • All: lists all L2 networks in the current zone.
      • Network Address Type: Select IPv4.

      • Network Range Method: Select IP Range.

      • Start IP: Set a start IP address for the network range, for example, 10.151.0.2.

      • End IP: Set an end IP address for the network range, for example, 10.151.0.254.

      • Netmask: Set a netmask for the network range, for example, 255.0.0.0.

      • Gateway: Set a gateway for the network range, for example, 10.0.0.1.

      • DHCP Service: Choose whether to enable the DHCP service.

        • The DHCP service is a built-in distributed service of the Cloud, which assigns IP addresses only to resources in the Cloud and does not conflict with your existing DHCP server.
        • By default, the DHCP service is enabled so that IP addresses are automatically assigned to resources in the Cloud. You can customize a DHCP IP or use the DHCP IP that the system assigned according to the IP allocation policy.
        • If you disable this option, IP addresses are not automatically assigned to resources that use this network. Therefore, you need to manually assign IP addresses to these resources. In addition, you cannot specify a DHCP IP. Neither can the system allocate one.
        • IP Allocation Policy: Optional. IP addresses can be assigned according to the following three allocation policies:

          • Random: The system randomly assigns IP addresses from the network range.

          • Allocate in Order:

            • The system assigns all available IP addresses from the network range in ascending order. Released IP addresses are assigned in the next allocation.
            • Example: Assume that the network range is 192.168.0.101~192.168.0.120, within which 192.168.0.101~192.168.0.108 are allocated. If 192.168.0.106 is released, it will be assigned first in the next allocation.
          • Allocate in Cycle:

            • The system assigns available IP addresses to VM instances from the network range in ascending order. Released IP addresses are assigned when currently available IP addresses are used up.
            • Example: Assume that the network range is 192.168.0.101~192.168.0.120, within which 192.168.0.101~192.168.0.108 are allocated. If 192.168.0.106 is released, it will be assigned after 192.168.0.120 is used.
        • DHCP IP: Optional. Set an IP address for the DHCP server, for example, 172.20.108.10.

          • A DHCP IP is an IP address used by the DHCP service to assign IP addresses to resources that use this L3 network.
          • If you create an L3 network for the first time with the DHCP service enabled, or if you add the first network range to an L3 network with the DHCP service enabled, you can customize the DHCP IP.
          • If the L3 network has a DHCP IP, you cannot customize the DHCP IP when you add a network range.
          • The DHCP IP can be in or outside the added IP range, but it must be an unoccupied IP address in the CIDR block of the added IP range
          • The IP range determined by the start IP and end IP cannot contain the link-local address 169.254.0.0/16.
          • If you select random as the IP allocation policy and this field is left blank, the system randomly assigns IP addresses from the added network range.
          • If you select allocate in order/allocate in cycle as the IP allocation policy and this field is left blank, the system uses the start IP address in the network range as the DHCP IP.
      • DNS: Optional. You can specify 114.114.114.114.

      • When you add an IP range for an IPv4 L3 network, note that:

        • The IP range cannot contain gateway IP addresses in the format of xxx.xxx.xxx.1, broadcast addresses in the format of xxx.xxx.xxx.255, or network addresses in the format of xxx.xxx.xxx.0.
        • The IP range of a private network cannot overlap with the IP range of a public network used to create a vRouter offering or of a management network.
      Create L3-Public Network
  3. Add an address pool.

    An address pool network range must co-exist with a normal network range. You cannot add an address pool network range if no normal network range is available. On the Network Range tab of the details page of the L3-Public Network, click Add Network Range. On the displayed Add Network Range page, set the following parameters:

    • IP Address Type: By default, the IPv4 type is displayed.

    • Network Range Method: By default, the IP range method is displayed.

    • Network Range Type: Select Address Pool.

    • Start IP: Set a start IP address for the address pool, for example, 172.20.0.1.

    • End IP: Set a end IP address for the address pool, for example, 172.20.0.254.

      The address pool cannot contain broadcast addresses in the format of xxx.xxx.xxx.255, or network addresses in the format of xxx.xxx.xxx.0.

    • Netmask: Set a netmask for the address pool, for example, 255.255.0.0.

    Add Address Pool
  4. Create a VIP using the address pool.

    On the main menu of ZStack Cloud, choose Resource Center > Network Service > Basic Network Service > VIP. On the VIP page, click Create VIP. Then, the Create VIP page is displayed. On the displayed page, set the following parameters:

    • Name: Enter a name for the virtual IP address (VIP).
    • Description: Optional. Enter a description for the VIP.
    • Network: Select an L3 network that has an address pool.
    • Network Range: Select an address pool.
    • Assign IP: Optional. You can assign a virtual IP address.
    • VIP QoS: You can limit the network bandwidth of public VIPs and flat network VIPs. You can set the QoS for a custom VIP when you create the VIP or after the VIP is created.
    Create VIP
  5. Test whether the VIP works properly.

    The VIP works properly if the VIP are used to provide EIP, port forwarding, load balancing, IPsec tunnel, and other network services. In this scenario, we use the VIP to create an EIP for verification.

    On the main menu of ZStack Cloud, choose Resource Center > Network Service > Basic Network Service > EIP. On the EIP page, click Create EIP. Then, the Create EIP page is displayed. On the displayed page, select Use Existing VIP.

    Create EIP

    The successful creation of EIP indicates that the VIP created from the VPC address pool can work properly.

So far, we have introduced how to use an address pool.

Security Group

Assuming that you have 2 VPC subnets, VPC-1 and VPC-2, attached to the same VPC vRouter. For security reasons, you decide to isolate a VM instance, VM1, on the VPC-1 and prohibit its common communications with the VPC-2. However, a specified IP address on the VPC-2 need to be excluded from this restriction, for it have to communicate with the VM1 to meet your business requirements.

The following tables describes more configuration details in this scenario:

Management/Public Network Configuration
NIC etho
VLAN ID NoVLAN
IP Range 172.26.56.161-172.26.56.170
Netmask 255.255.0.0
Gateway 172.26.0.1
VPC-1 Configuration
NIC eth0
VLAN ID 2800
IP CIDR 10.81.110.0/24
Netmask 255.255.255.0
Gateway 10.81.110.1
VPC-2 Configuration
NIC eth0
VLAN ID 2900
IP CIDR 10.81.111.0/24
Netmask 255.255.255.0
Gateway 10.81.111.1
Network/Direction Rule
VM1/Ingress Denies flows from the VPC-2, except for those from 10.81.111.3.
VM2/Egress Denies flows to the VPC-2, except for those to 10.81.111.3.

Follow these steps to configure a security group for the VM1 to meet your security requirements:

  1. Create VPC subnets and VM instances.
  2. Check mutual communications between the VPC subnets.
  3. Create a security group and set security rules.
  4. Check whether the security group take effect and meet your security requirements.
  1. Create VPC subnets and VM instances.

    1. Create two VPC networks, VPC-1 and VPC-2, according to the configuration information above and attach them to the same VPC vRouter.
    2. Create one VM instance, VM1 (IP: 10.81.110.2), on the VPC-1.
    3. Create two VM instances, VM2 (IP:10.81.111.2) and VM3 (IP:10.81.111.3), on the VPC-2.
  2. Check mutual communications between the VPC subnets.

    Log in to the VM1 and ping VM2 and VM3. Generally, VM instances on two VPC subnets can communicate properly before a security group is set.

    VM1 Ping VM2/VM3 Properly
  3. Create a security group and set security rules.

    On the main menu of ZStack Cloud, choose Resource Center > Network Service > Security Group. On the Security Group page, click Create Security Group, and the Create Security Group page is displayed.

    On the displayed page, set the following parameters:

    • Name: Set the security group name.

    • Description: Optional. Set the security group description.

    • Switch Type: Select Linux Bridge.

    • NIC: Choose the NIC of VM1.

    • Ingress Rule: Click Add Rule and set the first ingress rule for the security group.

      • Type: Displays Ingress.
      • Priority: Set as 1 by default.
      • Policy: Choose Allow.
      • IP Address Type: Choose IPv4.
      • Protocol: Choose ALL.
      • Source: Set a source from which flows can access the security group. Choose IP/CIDR and enter 10.81.111.3 here.
      • Enable: Enable this rule.
      • Description: Optional. Enter a description for the rule.

      Click Add Rule and set the second ingress rule for the security group.

      • Type: Displays Ingress.
      • Priority: Set as 2, which means this ingress rule has a lower priority than the first ingress rule.
      • Policy: Choose Reject.
      • IP Address Type: Choose IPv4.
      • Protocol: Choose ALL.
      • Source: Set a source from which flows cannot access the security group. Choose IP/CIDR and enter 10.81.111.0/24 here.
      • Enable: Enable this rule.
      • Description: Optional. Enter a description for the rule.
    • Egress Rule: Click Add Rule and set the first egress rule for the security group.

      • Type: Displays Egress.
      • Priority: Set as 1 by default.
      • Policy: Choose Allow.
      • IP Address Type: Choose IPv4.
      • Protocol: Choose ALL.
      • Destination: Set a destination to which flows from the security group are allowed. Choose IP/CIDR and enter 10.81.111.3 here.
      • Enable: Enable this rule.
      • Description: Optional. Enter a description for the rule.

      Click Add Rule and set the second egress rule for the security group.

      • Type: Displays Egress.
      • Priority: Set as 2, which means this egress rule has a lower priority than the first egress rule.
      • Policy: Choose Reject.
      • IP Address Type: Choose IPv4.
      • Protocol: Choose ALL.
      • Destination: Set a destination to which flows from the security group are denied. Choose IP/CIDR and enter 10.81.111.0/24 here.
      • Enable: Enable this rule.
      • Description: Optional. Enter a description for the rule.

    Click OK to create the security group.

    Create Security Group
  4. Check whether the security group take effect and meet your security requirements.

    1. Test whether the ingress rule works.

      1. Log in to VM-2 (10.81.112.2) and ping VM-1. According to the ingress rule, the VM-2 cannot communicate with VM-1.

        VM-2 Ping VM-1 Failed
      2. Log in to VM-3 (10.81.112.3) and ping VM-1. According to the ingress rule, the VM-3 can communicate with VM-1.

        VM-3 Ping VM-1 Successed
    2. Test whether the egress rule works.

      Log into the VM1 and ping VM-2 (10.81.111.2) and VM-3 (10.81.111.3) respectively. According to the egress rule, the VM-1 can communicate with the VM-2 and cannot communicate with the VM-3.

      VM1 Ping VM2 Failed; VM1 Ping VM3 Succeeded

So far, we have introduced how to use a security group.

Elastic IP

An elastic IP address (EIP) is a method to access a private network through other networks. An EIP converts the IP address of a network into the IP address of another network based on the network address translation (NAT) function.

The following diagram shows the EIP application scenario in a VPC network with a public EIP as an example.

EIP Application Scenario in VPC Network

The VM instance created from a VPC subnet can access to external network when it is associated with an EIP.

The following section describes two scenarios of using EIPs in a VPC network.

  • Create an EIP and associate it with a VM instance.
  • Associate the EIP with another VM instance.
  1. Create VPC subnets and VM instances.

    1. Create two VPC networks, VPC-1 and VPC-2, according to the configuration information above and attach them to the same VPC vRouter.
    2. Create one VM instance, VM1 (IP: 10.81.110.2), on the VPC-1.
    3. Create two VM instances, VM2 (IP:10.81.111.2) and VM3 (IP:10.81.111.3), on the VPC-2.
  2. Create an EIP and associate it with VM-1.

    1. Create an EIP.

      On the main menu of ZStack Cloud, choose Resource Center > Network Service > Basic Network Service > EIP. On the EIP page, click Create EIP. Then, the Create EIP page is displayed.

      On the displayed page, set the following parameters:

      • Name: Enter a name for the EIP.

      • Description: Optional. Enter a description for the EIP.

      • You can use a virtual IP address by using either of the following methods:

        • VIP: Select Create VIP.

          • Network: Select an L3 network to create a VIP. The network can be a public network or a flat network.

            Currently, you cannot create a VIP with a flat network disabled with IP address management.

          • Network Range: Optional. Select a network range.

            • If you selected an IPv4 public network, you can select a normal network range or an address pool. If you selected an IPv6 public network, you can only select a normal network range.
            • If you selected an IPv4 or IPv6 public network, you can only select a normal network range.
            • If you selected an IPv4 VPC network, you can only select a normal network range.
          • Assign IP: Optional. You can assign a virtual IP address.

            • If left blank, the system automatically assigns a VIP.
            • If you do not select a network range, you can specify an IP address only from a normal network range.
        • VIP: Select Use Existing VIP.

          Set the following parameter:

          • VIP: Select an existing VIP.
      Create EIP
    2. Associate EIP-1 with VM-1.

      On the EIP page, locate EIP-1 and click Actions > Attach NIC. Then, the Select Instance NIC page is displayed. On the displayed page, select the NIC of VM-1.

      Associate EIP-1 with VM-1
    3. Log in to VM-1 through EIP-1.

      You can SSH to VM-1 using the EIP-1 from a VM instance that can access to the public network range of the VPC network.

      Log in to VM-1 Through EIP-1
  3. Associate EIP-1 with VM-2.

    1. Disassociate EIP-1 from VM-1.

      On the EIP page, locate EIP-1 and click Actions > Detach NIC.

      Disassociate EIP-1 from VM-1
    2. Associate EIP-1 with VM-2.

      On the EIP page, locate EIP-1 and click Actions > Attach NIC. Then, the Select Instance NIC page is displayed. On the displayed page, select the NIC of VM-2.

      Associate EIP-1 with VM-2
      Associate EIP-1 with VM-2 (2)
    3. Log in to VM-2 through EIP-1.

      You can SSH to VM-2 using the EIP-1.

      Log in to VM-2 Through EIP-1

Port Forwarding

This chapter introduces three scenarios of using a port forwarding in a VPC network.

  • Create a port forwarding and associate it with a VM instance.
  • Associate a port forwarding with other VM instances.
  • Associate different ports of the same VIP with different VM instances.
  1. Create VPC subnets and VM instances.

    Create two subnets using the same VPC vRouter, for example, VPC Network-1 and VPC Network-2. Then, create two VM instances using the VPC subnets respectively.

  2. Create a port forwarding and associate it with VM-1.

    1. Create a port forwarding.

      On the main menu of ZStack Cloud, choose Resource Center > Network Service > Basic Network Service > Port Forwarding. On the Port Forwarding page, click Create Port Forwarding. Then, the Create Port Forwarding page is displayed.

      On the displayed page, set the following parameters:

      • Name: Enter a name for the port forwarding rule, for example, PF-1.

      • Description: Optional. Enter a description for the port forwarding rule.

      • VIP: You can create a VIP or use an existing VIP to provide port forwarding services.

        • Create VIP: Create a VIP. If you select to create a VIP, set the following parameters:

          • Network: Select a public network to create a VIP.

          • Network Range: Optional. Select a network range. If you selected an IPv4 public network, you can select a normal network range or an address pool.

          • Assign IP: Optional. You can assign a virtual IP address.

            • If left blank, the system automatically assigns a VIP.
            • If you do not select a network range, you can specify an IP address only from a normal network range.
        • Use Existing VIP: Use an existing VIP. If you select to use an existing VIP, set the following parameters:

          • VIP: Select an existing VIP.

        The system VIP of a VPC vRouter can be used to provide port forwarding services.

      • Protocol: Select a protocol, Valid values: TCP and UDP.

      • Port: Select a port mapping method.

        Two port mapping methods are supported: port-to-port mapping and port range-based mapping.

        • Specified Port: If you specify ports, set the following parameters:

          • Source Port: Select a port from ports 0-65535 as the source port.
          • VM Port: Select a port from ports 0-65535 as the VM port.

          For example, if you set 24 as the source port and 22 as the VM port, the traffic to port 24 of the public IP will be forwarded to port 22 of the VM instance.

        • Port Range: Select two ports from ports 0-65535 as the start port and end port, respectively.

          For example, if the port range is 22-80, traffic to ports 22-80 of the public IP will be forwarded to ports 22-80 of the VM instance.

      • Allowed CIDR: Optional. You can specify a CIDR block to allow access to only this CIDR block.

      Create Port Forwarding-1
    2. Associate PF-1 with VM-1.

      On the Port Forwarding page, locate PF-1 and click Actions > Associate VM NIC. Then, on the displayed Associate VM NIC page, select the NIC of VM-1.

      Associate PF-1 with VM-1
    3. Log in to VM-1 through PF-1.

      You can log in to the port 22 of VM-1 by SSH the port 24 of a VM instance that can access to public network range of the VPC network.

      Log in to VM-1 Through PF-1
  3. Associate PF-1 with VM-2.

    1. Disassociate PF-1 from VM-1.

      On the Port Forwarding page, locate PF-1 and click Actions > Disassociate VM NIC.

      Disassociate PF-1 from VM-1
    2. Associate PF-1 with VM-2.

      On the Port Forwarding page, locate PF-1 and click Actions > Associate VM NIC. Then, on the displayed Associate VM NIC page, select the NIC of VM-2.

      Associate PF-1 with VM-2
    3. Log in to VM-2 through PF-1.

      You can log in to the port 22 of VM-2 by SSH the port 24 of the VM instance.

      Log in to VM-2 Through PF-1
  4. Associate different ports of the same VIP with different VM instances.

    1. Create another port forwarding using the same VIP.

      On the main menu of ZStack Cloud, choose Resource Center > Network Service > Basic Network Service > Port Forwarding. On the Port Forwarding page, click Create Port Forwarding. Then, the Create Port Forwarding page is displayed.

      On the displayed page, set the following parameters:

      • Name: Enter a name for the port forwarding rule, for example, PF-2.
      • Description: Optional. Enter a description for the port forwarding rule.
      • VIP: Select Use Existing VIP.
      • Protocol: Select TCP.
      • Port: Select Port Range and enter 30-40.
      • Allowed CIDR: Optional. You can specify a CIDR block to allow access to only this CIDR block.
      Create Port Forwarding
    2. Associate PF-2 with VM-1.

      On the Port Forwarding page, locate PF-2 and click Actions > Associate VM NIC. Then, on the displayed Associate VM NIC page, select the NIC of VM-1.

      Associate PF-2 with VM-1
    3. You can see that the same VIP (192.168.1.74) can be associated with different VM instances through different port forwarding rules.

    4. Send a message to VM-1 through PF-2.

      You can use the nc command to send a message to a port ranging form 30 to 40 of the public network IP (192.168.1.74) from a VM instance that can access to the public network range of the VPC network. The VM-1 can receive the message from the corresponding port.

      For example, you can send a message on source port 30 and receive the message on the port 30 of VM-1.

      To clear the original iptables in VM-1, you can use the iptables -F command.

      Send Message on Source Port 30
      Receive Message on Port 30 of VM-1

Load Balancing

Typical scenario: Assume that the user has a high number of application access in the VPC network. The user wants to use a dedicated performance load balancer to distribute traffic flows to a group of backend servers to improve the service capbility of the business. According to the business needs, the load balancer needs to adopt a HTTPS protocol to monitor traffic flows. Assume the user has met the following requirements:

  • The user has deployed the latest version of ZStack Cloud.
  • The user has deployed a public network, VPC network, and management network.
  • The user has created 3 business VMs.
  • Th user has prepared a certificate for HTTPS monitoring.

To use a loading balancing, follow these steps:

  1. Add a dedicated-performance LB image.
  2. Create a load balancer instance offering.
  3. Create a dedicated-performance load balancer.
  4. Create a certificate.
  5. Create a listener.
  6. Attach a NIC to the load balancer.
  7. Add a backend server.
  8. Scenario test.
  1. Add a dedicated-performance LB image.

    On the main menu of ZStack Cloud, choose Resource Center > Network Service > Basic Network Service > Load Balancing > Image. On the Image tab, click Add Image. The Add Image page appears.

    On the displayed page, set the following parameters:

    • Name: Enter a name for the LB image.

    • Description: Optional. Enter a description for the LB image.

    • CPU Architecture: Select a CPU architecture for the LB image. LB instances created from the image inherit this CPU architecture.

    • Backup Storage: Select a backup storage to store the LB image.

    • Image Path: Enter a URL or upload a local file. In this case, enter a URL.

      • URL: Enter the download URL of the LB image.
    Add Dedicated-Performance LB Image
  2. Create a load balancer instance offering.

    On the main menu of ZStack Cloud, choose Resource Center > Network Service > Basic Network Service > Load Balancing > Offering. On the Offering tab, click Create Load Balancer Instance Offering. The Create Load Balancer Instance Offering page is displayed.

    On the displayed page, set the following parameters:

    • Zone: By default, the current zone is displayed.
    • Name: Enter a name for the load balancer (LB) instance offering.
    • Description: Optional. Enter a description for the LB instance offering.
    • CPU: Specify the number of CPU cores for the LB instance offering, for example, specify 2 Core.
    • Memory: Specify the memory size for the LB instance offering, for example, specify 8GB.
    • Image: Select a dedicated-performance LB image that you added.
    • Management Network: Select a management network that you created.
    Create Load Balancer Instance Offering
  3. Create a dedicated-performance load balancer.

    On the main menu of ZStack Cloud, choose Resource Center > Network Service > Basic Network Service > Load Balancing. On the Load Balancer page, click Create Load Balancer. The Create Load Balancer page appears.

    On the displayed page, set the following parameters:

    • Name: Enter a name for the LB.

    • Description: Optional. Enter a description for the LB.

    • LB Type: Select Dedicated Performance.

    • Frontend Network Protocol: Select the network protocol for the frontend network. Here, select IPv4.

    • Frontend Network: Select a network as the frontend network of the LB. Here, select a VPC network.

    • VIP: You can create a VIP or use an existing VIP to provide load balancing services. Here, select New VIP. Set the following parameters:

      • Network Range: Optional. Select an IP range.
      • Assign IP: Optional. Specify a VIP. This parameter is available only after you select an IP range.
    • Backend Network: Select a network as the backend network. Here, specify the same VPC network.

      You can add multiple backend networks by attach NICs to the load balancer. All VPC network in the same VPC vRouter to which the VPC network is attached can be specified as backend networks. For more information, see Attach a NIC to the load balancer.

    • HA Mode: Select single node.

    • LB Instance Name: Enter a name for the LB instance.

    • Load Balancer Offering: Select a LB offering.

    • Storage Allocation Policy: Select the storage allocation policy for the load balancer. Supports System Allocation and Custom. Here, select Custom.

    Create Dedicated-Performance Load Balancer
  4. Create a certificate.

    On the main menu of ZStack Cloud, choose Resource Center > Network Service > Basic Network Service > Load Balancing > Certificate Management. On the Certificate Management tab, click Create Certificate. The Create Certificate page appears.

    On the displayed page, set the following parameters:

    • Name: Enter a name for the certificate.
    • Description: Optional. Enter a description for the certificate.
    • Certificate Text: Enter the certificate content.
    • Private Key: Enter the private key.
    • Certificate Chain: Optional. If you need to upload multiple certificates, you need to combine the root and intermediates certificates and then upload the certificates.
    Create Certificate
  5. Create a listener.

    On the details page of the load balancer, click the Listener tab. On the tab, click Create Listener. The Create Listener page is displayed.

    On the displayed page, set the following parameters:

    • Name: Enter a name for the listener.
    • Description: Optional. Enter a description for the listener.
    • Protocol: Select a listening protocol. Here, select HTTPS.
    • Certificate: Associate a certificate with the listener.
    • Load Balancer Port: Specify a port for load balancing. Valid values: 1 to 65535. Here, specify100.
    • Backend Server Port: Specify a backend server port. Valid values: 1 to 65535. Here, specify 80.
    • Load Balancer Algorithm: Set a routing rule for data packets. Here, select Round Robin.
    • Session Persistence: An innate mechanism of the load balancing service. It identifies the association of the interactions between a client and backend servers based on which a load balancer can direct the client’s requests to a specific backend server and achieve business continuity.
    • Backend Server Group: Optional. Select a backend server group. Here, select the default backend server group.
    • Advanced: Configure advanced settings for the listener. Here, use default settings.
    Create Listener
  6. Attach a NIC to the load balancer.

    On details page of the load balancer, click LB Instance. On the LB Instance tab, click Attach on the NIC section. Then, the Attach NIC page is displayed.

    On the displayed page, set the following parameters:

    • Network: Select backend network to be attached. Here, select the VPC network of the same VPC vRouter.
    • IPV4 Address: Optional. You can specify an IP address for the NIC. If not specified, the Cloud automatically assigns an IP address within the selected network range.
    Attach NIC to Load Balancer
  7. Add a backend server.

    On the details page of the load balancer, click Backend Server Group. On the tab, enter the details page of the backend server group. On the details page, click Add Backend Server. Then, the Add Backend Server page is displayed.

    On the displayed page, set the following parameters:

    • Backend Server: You can add a VM instance or other servers outside of the Cloud as a backend server. Here, select By Instance NIC.
    • Network: Select the VPC network of the same VPC vRouter.
    • NIC: Specify 3 VM instances NICs.
    Add Backend Server
  8. Scenario test.

    In this scenario, we will run the curl command in the port 100 of the VIP address of the load balancer: for i in {1..20}; do curl -k https://192.168.0.249:100; done. The 3 business VM instances will be polled in sequence.

    Scenario Test

So far, we have introduced how to use a dedicated-performance load balancer in a VPC network.

IPsec Tunnel

Typical scenario of IPsec tunnel in a VPC network: In two isolated ZStack Cloud environment, create two VPC environments. In these two VPC environments, create two VPC networks (subnets) respectively. The two VPC subnets cannot directly communicate with each other. You can realize the mutual communication between two VPC subnets by using IPsec tunnel.

Basic steps of using IPsec tunnel:

  1. In the first ZStack Cloud environment, create an IPsec tunnel, specify the local public IP address in the first VPC environment, and specify one or more VPC subnets that are locally available. Enter the public IP address in the second VPC environment as the peer public IP, and enter one or more VPC subnets specified in the second VPC environment as the peer networks.
  2. In the second ZStack Cloud environment, create an IPsec tunnel, specify the local public IP address in the second VPC environment, and specify one or more VPC subnets that are locally available. Enter the public IP address in the first VPC environment as the peer public IP, and enter one or more VPC subnets specified in the first VPC environment as the peer networks.

Make sure that the CIDR blocks of all private networks in two VPC environments do not overlap.

The following tables list the assumed environment configurations.

  • The first ZStack Cloud environment:

    1. Public Network

      Public Network Configuration
      NIC em01
      VLAN ID No VLAN
      IP Range 10.151.10.100~10.151.10.200
      Netmask 255.0.0.0
      Gateway 10.0.0.1
    2. Management Network

      Management Network Configuration
      NIC em02
      VLAN ID No VLAN
      IP Range 192.168.28.100~192.168.28.200
      Netmask 255.255.255.0
      Gateway 192.168.28.1
      • For security and stability reasons, we recommend that you deploy an independent management network and separate it from the public networks.
      • The management network we mentioned here is the same as that in ZStack Private Cloud. That is, the management network is the network used to manage hosts, primary storages, and backup storages. If a management network was created before, you can use it directly.
    3. VPC Network-1

      Private Network Configuration
      NIC em01
      VLAN ID 2018
      IP CIDR 192.168.10.0/24
    4. VPC Network-2

      Private Network Configuration
      NIC em01
      VLAN ID 2020
      IP CIDR 192.168.20.0/24
  • The second ZStack Cloud environment:

    1. Public Network

      Public Network Configuration
      NIC em01
      VLAN ID No VLAN
      IP Range 10.151.20.100~10.151.20.200
      Netmask 255.0.0.0
      Gateway 10.0.0.1
    2. Management Network

      Management Network Configuration
      NIC em02
      VLAN ID No VLAN
      IP Range 192.168.28.10~192.168.28.90
      Netmask 255.255.255.0
      Gateway 192.168.28.1
    3. VPC Network-3

      Private Network Configuration
      NIC em01
      VLAN ID 2017
      IP CIDR 192.168.30.0/24
    4. VPC Network-4

      Private Network Configuration
      NIC em01
      VLAN ID 2030
      IP CIDR 192.168.40.0/24

The follow sections describe the detailed steps of how to create an IPsec tunnel.

  1. Create two VPC networks (subnets) in the first ZStack Cloud environment, for example, VPC Network-1 and VPC Network-2. Then, create two VM instances using the VPC networks respectively, for example, creating VM-1 from VPC Network-1.

  2. Similarly, create two VPC networks (subnets) in the second ZStack Cloud environment, for example, VPC Network -3 and VPC Network-4. Then, create two VM instances using the VPC networks respectively, for example, creating VM-3 from VPC Network-3.

  3. Test the network connectivity among VM-1, VM-2 in the first environment and VM-3, VM-4 in the second environment.

    • Log in to VM-1, and try to SSH to the port 22 of VM-3. You will fail to SSH to VM-3 or ping VM-3.

    • VM-1 Fails to Communicate with VM-3
    • Log in to VM-1, and you will fail to try to communicate with VM-4.

    • Log in to VM-2, and you will fail to try to communicate with VM-3 and VM-4.

    • Log in to VM-3, and you will fail to communicate with VM-1 and VM-2.

    • Log in to VM-4, and you will fail to try to communicate with VM-1 and VM-2.

  4. Create an IPsec tunnel in the first ZStack Cloud environment.

    1. Create an IPsec tunnel.

      On the main menu of ZStack Cloud, choose Resource Center > Network Service > Advanced Network Service > IPsec Tunnel. On the IPsec Tunnel page, click Create IPsec Tunnel. Then, the Create IPsec Tunnel page is displayed. On the displayed page, set the following parameters:

      • Name: Enter a name for the IPsec tunnel, for example, IPsec-1.

      • Description: Optional. Enter a description for the IPsec tunnel.

      • Local IP Address:

        • VIP: You can create a VIP or use an existing VIP to provide IPsec tunnel services.

          Create VIP: Create a VIP. If you select to create a VIP, set the following parameters:

          • Public Network: Select a public network to create a VIP.

          • IP Range: Optional. Select an IP range. If you selected an IPv4 public network, you can select a normal IP range or an address pool.

          • Assign IP: Optional. You can assign a virtual IP address.

            • If left blank, the system automatically assigns a VIP.
            • If you do not select a network range, you can specify an IP address only from a normal network range.

          Use Existing VIP: Use an existing VIP. If you select to use an existing VIP, set the following parameters:

          • VIP: Select an existing VIP.

            The system VIP of a VPC vRouter can be used to provide IPsec tunnel services.

      • Peer Public IP: Enter the peer public IP address that provides IPsec tunnel services.

      • Source Network CIDR: Select a VPC network attached to the VPC vRouter that is associated with the selected public network. If only one VPC network is attached to the VPC vRouter, the VPC network is selected by default.

      • Peer CIDR: Specify a specified peer network CIDR.

        The CIDR block cannot be overlapped with the network range of the management network and public network attached to the VPC vRouter.

      • Authentication Mode: psk

      • Authentication Key: Set a relatively strong authentication key.

        The local authentication key must be consistent with its peer.

      • ID Configuration Method: Configure an ID for the local and peer devices. You can configure an ID in the format of an IP address and name:

        • IP Address: Use an IP address to identify the local and peer devices.

          • Local ID: The unique ID that identifies the local device. You can use this ID for authenticating the peer device. The local ID must be 1-255 characters in length.
          • Peer ID: The unique ID that identifies the peer device. You can use this ID for authenticating the local device. The peer ID must be 1-255 characters in length.
        • Name: Use a name to identify the local and peer devices.

          • Local ID: The unique ID that identifies the local device. You can use this ID for authenticating the peer device. The local ID must be 1-255 characters in length.
          • Peer ID: The unique ID that identifies the peer device. You can use this ID for authenticating the local device. The peer ID must be 1-255 characters in length.
      • Advanced: You can configure advanced parameter settings for the IPsec tunnel, including IKE configurations and IPsec configurations. The Cloud automatically configures default settings for the parameters, as shown in the following list:

        • IKE Configuration:

          • IKE Version: IKEv2
          • IKE Authentication Algorithm: sha256
          • IKE Encryption Algorithm: aes-256
          • IKE DH Group: 2
        • IPsec Configuration:

          • Encapsulation Mode: tunnel
          • IPsec Security Protocol: esp
          • ESP Authentication Algorithm: sha256
          • ESP Encryption Algorithm: aes-256
          • PFS DH Group: dh-group14
        • If you configure an IPsec tunnel by using a VPC vRouter of ZStack Cloud and a third-party device, you need to coordinate the advanced settings of the two devices.
        • When you create an IPsec tunnel, you need to adjust local advanced settings based on the IPsec configurations of the peer network device.
      Create IPsec Tunnel

      Click OK to create IPsec-1.

      IPsec Tunnel
  5. Similarly, create another IPsec tunnel in the second ZStack Cloud environment.

  6. Test the connectivity among VM-1, VM-2 in the first environment and VM-3, VM-4 in the second environment.

    • Log in to VM-1, and you can SSH to VM-3 and VM-4 through port 22 and ping VM-3 and VM-4.

      VM-1 Successfully Connect to VM-3 and VM-4
      VM-1 Successfully Connect to VM-3 and VM-4 (2)
    • Log in to VM-2, and you can SSH to VM-3 and VM-4 through port 22 and ping VM-3 and VM-4.

    • Log in to VM-3, and you can SSH to VM-1 and VM-2 through port 22 and ping VM-1 and VM-2.

      VM-3 Successfully Connect to VM-1 and VM-2
      VM-3 Successfully Connect to VM-1 and VM-2 (2)
    • Log in to VM-4, and you can SSH to VM-1 and VM-2 through port 22 and ping VM-1 and VM-2.

So far, we have introduced how to use an IPsec tunnel in a VPC network.

OSPF Area

Open Shortest Path First (OSPF): An OSPF is an interior gateway protocol of link states and is used to distribute routing information within a single autonomous system (AS). An OSPF is widely used in a data center network and a campus network.

Typical scenario of an OSPF area: Assume that the user has two sets of network environment, one of which is a VPC network environment on the Cloud, and the other is a traditional network environment that configured with OSPF protocol in the physical environment. To ensure that the two network environments can communicate with each other, the user need to create an OSPF area that is identical with that of the physical environment on ZStack Cloud. Then, add a VPC vRouter that is isolated in layer 3 network and the traditional router to the same OSPF area to establish the neighboring relations. This way, you can realize the mutual communication between VPC network and traditional network.

To use an OSPF area, follow these steps:

  1. Create two VPC networks using the same VPC vRouter.
  2. Test the network connectivity when the OSPF protocol is not used.
  3. Create an OSPF area and add VPC vRouter to it.
  4. Test the network connectivity when the OSPF protocol takes effect.

The CIDR block of the private networks in two environments cannot overlap with each other.

The following tables list the assumed environment configurations.

  1. OSPF Area Configuration in Traditional Physical Network

    OSPF Area Configuration
    Area ID 0.0.0.0
    Type Standard
    Authentication Method None
  2. Public Network Configuration in Traditional Physical Network

    Public Network Configuration
    NIC em01
    VLAN ID No VLAN
    IP Range 10.151.0.0~10.151.0.100
    Netmask 255.0.0.0
    Gateway 10.0.0.1
  3. Private Network Configuration in Traditional Physical Network

    Router Network Configuration
    NIC em01
    IP CIDR 192.168.10.0/24
  4. Public Network Configuration on Cloud

    Public Network Configuration
    NIC em01
    VLAN ID No VLAN
    IP Range 10.151.0.101~10.151.0.255
    Netmask 255.0.0.0
    Gateway 10.0.0.1
  5. Management Network on Cloud

    Management Network Configuration
    NIC em02
    VLAN ID No VLAN
    IP Range 192.168.28.100~192.168.28.200
    Netmask 255.255.255.0
    Gateway 192.168.28.1
    • For security and stability reasons, we recommend that you deploy an independent management network and separate it from the public networks.
    • The management network we mentioned here is the same as that in ZStack Private Cloud. That is, the management network is the network used to manage hosts, primary storages, and backup storages. If a management network was created before, you can use it directly.
  6. VPC Network-1 on Cloud

    VPC Network Configuration
    NIC em01
    VLAN ID 2018
    IP CIDR 192.168.3.0/24
  7. VPC Network-2 on Cloud

    VPC Network Configuration
    NIC em01
    VLAN ID 2019
    IP CIDR 192.168.4.0/24

The following section describes the detailed steps of how to use an OSPF area.

  1. Create two VPC networks using the same VPC vRouter.

    According to the planned network configuration information, create a VPC vRouter in ZStack Cloud. Then, create two VPC networks using the VPC vRouter.

    1. Public Network: 10.151.0.101 to 10.151.0.255. Make sure that the public network is on the same gateway with the traditional physical network to ensure network interconnection.
    2. VPC vRouter: VPC vRouter-1.
    3. VPC Network: VPC Network-1 (192.168.3.0/24), VPC Network-2 (192.168.4.0/24).
  2. Test the network connectivity when the OSPF protocol is not used.

    Create VM instances using VPC Network-1 and VPC Network-2 respectively, for example, VM-1 (192.168.3.251), VM-2 (192.168.4.196). You can ping the gateway of physical network to test network connectivity.

    Expected result:

    • Log in to VM-1 (192.168.3.251) ping 192.168.10.1: Failed.
    • Log in to VM-2 (192.168.4.196) ping 192.168.10.1: Failed.
    Test Network Connectivity
  3. Create an OSPF area and add VPC vRouter to it.

    Create an OSPF area on the Cloud with the same area ID as that of the planned OSPF area in traditional physical network.

    On the main menu of ZStack Cloud, choose Resource Center > Network Service > Advanced Network Service > OSPF Area. On the OSPF Area page, click Create OSPF Area. Then, the Create OSPF Area page is displayed. On the displayed page, set the following parameters:

    • Area ID: Set an area ID in dotted decimal notation that identifies an OSPF area. The area ID is in similar format as that of IPv4 address. In this scenario, enter 0.0.0.0.

    • Type: Select an OSPF area type. Valid values: Standard and Stub. In this scenario, select Standard.

      • Standard: Standard areas support all types of LSAs.
      • Stub: Stub areas do not support Type 4 and Type 5 LSAs.
    • Authentication Method: The authentication method used when you select VPC vRouters in an OSPF area to establish neighbors. Valid values: None, Plaintext, and MD5. In this scenario, select None.

      • None: Packets are received without identity authentication.
      • Plaintext: Identity authentication is implemented by using the password contained in the received packets.
      • MD5: Identity authentication is implemented by using the key ID and password MD5 hash that are contained in the received packets.
    • Routing Configuration: Optional. Set routing configurations. If you set this parameter, you need to:

      • VPC vRouter: Select a VPC vRouter to add to the OSPF area, for example, VPC vRouter-1.
      • Network: Select a network associated with the VPC vRouter to add to the OSPF area, for example, VPC Network-1 and L3-Public Network.

      You can add a VPC vRouter to multiple OSPF areas, but you can add a VPC network or public network associated with the VPC vRouter to only one OSPF area.

    Create OSPF Area

    After the OSPF area is created, you can go to the Associated Resource tab of the details page to view neighbor vRouter information. After the neighbor is successfully created (less than 60 seconds), the communication works properly when the OSPF protocol takes effect.

  4. Test the network connectivity when the OSPF protocol takes effect.

    Use VM-1 and VM-2 to test the network connectivity when the OSPF protocol takes effect.

    Expected result:

    • Log in to VM-1 (192.168.3.251) ping 192.168.10.1: Succeeded.
    • Log in to VM-2 (192.168.4.196) ping 192.168.10.1: Failed.
    Test Network Connectivity

So far, we have introduced how to use an OSPF protocol.

Multicast Routing

Multicast Routing: VPC vRouters receive multicast information sent by multicast sources and forward the information to V instances to realize one-to-many connections on senders and receivers.

  • ZStack Cloud allows you to use VM instances as the multicast information receivers, and to use VPC vRouters as multicast routers to participate in the multicast routing message exchanges.
  • VPC vRouters support the PIM-SM/PIM-SSM protocol. In the PIM-SM protocol, RP routers are the key devices in the PIM-SM domain. You can either manually configure RP addresses or dynamically elect or assign RP addresses according to the BSR mechanism.

Typical scenario of multicast routing: Assume that the user has a VPC environment on ZStack Cloud, and demands that VM instances using the VPC vRouter to communicate can receive multicast data from the public network. To do so, the user needs to set relevant configuration of the VPC vRouter on ZStack Cloud.

Multicast Routing Topology

To use multicast routing, follow these steps:

  1. Prepare multicast source.
  2. Configure multicast routing.
  3. Test whether multicast routing works.

The following tables list the assumed environment configurations.

  1. Public Network

    Public Network Configuration
    NIC em01
    VLAN ID No VLAN
    IP Range 10.108.10.100~10.108.10.200
    Netmask 255.0.0.0
    Gateway 10.0.0.1
    DHCP IP 10.108.10.101
  2. Management Network

    Management Network Configuration
    NIC em02
    VLAN ID No VLAN
    IP Range 192.168.29.10~192.168.29.20
    Netmask 255.255.255.0
    Gateway 192.168.29.1
    • For security and stability reasons, we recommend that you deploy an independent management network and separate it from the public networks.
    • The management network we mentioned here is the same as that in ZStack Private Cloud. That is, the management network is the network used to manage hosts, primary storages, and backup storages. If a management network was created before, you can use it directly.
  3. VPC Network

    Private Network Configuration
    NIC em01
    VLAN ID 2800
    IP CIDR 192.168.1.0/24
    DHCP IP 192.168.1.2

The following section describes the detailed steps of how to use a multicast routing.

  1. Prepare multicast source.

    Configure the VM instance as the multicast source according to the following requirements:

    1. Create a VM instance from the public network according to the planned configuration. Set the VM name as VM-sender and use the yum install -y socat command to install socat. This way, the VM-sender can be used as the source to send multicast messages.
    2. Make sure that the multicast feature of the switch is enabled.
  2. Configure multicast routing.

    1. Create a VPC vRouter on ZStack Cloud based on the planned network configuration. You can refer to the Basic Deployment chapter.

      • Public Network: 10.108.10.100 to 10.108.10.200. Make sure that the public network is on the same gateway with the traditional physical network to ensure network interconnection.
      • VPC vRouter: VPC vRouter-1.
    2. On the Multicast Routing tab of the details page of the VPC vRouter, click Enable to enable the multicast routing feature. On the Multicast Routing tab, click Actions > Add to add a static RP Configuration. On the displayed Add Static RP Configuration dialogue box, set the following parameters:

      • RP Address: Enter a RP address, for example, 10.108.10.125.

        You can either manually configure RP addresses or dynamically elect or assign RP addresses according to the BSR mechanism. The RP address must be a stable public IP address.

      • Group: Set an IP multicast group address to which multicast messages are sent, for example, 239.1.1.1/32.

        • An IP multicast group is a collection of receivers identified by IP multicast addresses. VPC vRouters join the IP multicast group as its members so that they can receive the multicast data sent to the group.
        • Enter the IP multicast group address in the format of a CIDR block.
      Add Static RP Configuration
    3. Create a VPC network using the VPC vRouter, and create a VM instance from the VPC network, for example, VM-receiver. Use the yum install -y socat command to install socat so that the VM-receiver can receive multicast messages.

      VM instances need to correctly configure the firewall to receive multicast messages, for example, enabling IGMP protocol and receiving multicast data.

  3. Test whether the multicast routing works.

    1. Launch the console of VM-sender and run the following command to send an UDP data packets to the address whose multicast group address is 239.1.1.1 and port is 54321 and set the TTL of the multicast group data as 10.

      [root@localhost~]# for i in {1..100} ;do echo hi+$i | socat - udp4-sendto:239.1.1.1:54321,sp=54321,ip-multicast-ttl=10 ;done 
      Send Multicast Message
    2. Launch the console of VM-receiver and run the following command, which indicates that specifying the NIC (em01) to add to the multicast group (239.1.1.1) and receiving the UDP data packets from port 54321.

      [root@localhost~]# socat stdio udp4-recv:54321,ip-add-membership=239.1.1.1:em01
      Receive Multicast Message

    As described above, the VM-receiver receives the multicast messages from VM-sender, which indicates that the multicast routing takes effect.

So far, we have introduced how to use multicast routing.

Distributed Routing

Distributed routing: After distributed routing feature is enabled, the Cloud will optimize east-west network traffic to improve I/O performance and reduce the network latency. Distributed routing also strengthens the reliability of communication among VM instances and the intranet traffic across three layers will not fail due to vRouter failures.

Typical distributed routing scenarios:

  • Assume that the user has three hosts. VM-1 and VM-2 are on different hosts, and on vxlan1: 192.168.1.0/24 and vxlan2: 192.168.2.0/24, respectively. Since the L2 and L3 networks of the two VM instances are different, the traffic that flows between VM-1 and VM-2 needs to be routed through a VPC vRouter on the third host.

  • After the distributed routing is enabled, messages sent by VM-1 will be sent to a VPC vRouter through the traditional path. The network proxy of the VPC vRouter sends an optimization instruction through ZSNP protocol to that of the compute node. Then, messages of VM-1 will be directly sent to VM-2 without passing through a VPC vRouter.

    ZSNP protocol: Based on IP protocol, it is used to solve the problem that the router proxy cannot know the information of compute node where the VM instance resides.

This scenario mainly introduces how to use distributed routing with VXLAN network as an example.

  1. Create a VPC vRouter.
  2. Create a VXLAN pool.
  3. Create L2 private networks (L2-VXLAN1 and L2-VXLAN2) and attach them to the corresponding cluster. These L2 private networks are used to create L3 VPC networks.
  4. Specify a VPC vRouter to create L3 VPC networks (VPC Netowrk-1 and VPC Network-2).
  5. Use VPC Network-1 to create VM-1 on Host-1 and use VPC Network-2 to create VM-2 on Host-2.
  6. Enable distributed routing, test the network connectivity between VPC Network-1 and VPC Network-2, and monitor traffic flow direction.

Note that all private network range must not overlap.

The following tables list the assumed environment configurations.

  1. Public Network

    Public Network Configuration
    NIC em01
    VLAN ID No VLAN
    IP Range 10.108.10.100~10.108.10.200
    Netmask 255.0.0.0
    Gateway 10.0.0.1
    DHCP IP 10.108.10.101
  2. Management Network

    Management Network Configuration
    NIC em02
    VLAN ID No VLAN
    IP Range 192.168.29.10~192.168.29.20
    Netmask 255.255.255.0
    Gateway 192.168.29.1
    • For security and stability reasons, we recommend that you deploy an independent management network and separate it from the public networks.
    • The management network we mentioned here is the same as that in ZStack Private Cloud. That is, the management network is the network used to manage hosts, primary storages, and backup storages. If a management network was created before, you can use it directly.
  3. VPC Network-1

    Private Network Configuration
    NIC em01
    VLAN ID 2800
    IP CIDR 192.168.1.0/24
    DHCP IP 192.168.1.2
  4. VPC Network-2

    Private Network Configuration
    NIC em01
    VLAN ID 2900
    IP CIDR 192.168.2.0/24
    DHCP IP 192.168.2.2

The following section describes the detailed steps of how to use distributed routing.

  1. Create a VPC vRouter.

    Create a VPC vRouter according to the planned network configuration. For more information, see Basic Deployment.

    1. Public Network: 10.108.10.100 to 10.108.10.200. Make sure that the public network is on the same gateway with the traditional physical network to ensure network interconnection.
    2. VPC vRouter: VPC vRouter-1.
  2. Create a VXLAN Pool.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L2 Network Resources > VXLAN Pool. On the VXLAN Pool page, click Create VXLAN Pool. Then, the Create VXLAN Pool page is displayed. On the displayed page, set the following parameters:

    • Zone: By default, the current zone is displayed.

    • Name: Enter a name for the VXLAN pool.

    • Description: Optional. Enter a description for the VXLAN pool.

    • SDN Type: Select Software.

    • VNI Range: Enter the start ID and end ID of VXLAN networks, for example, 1 to 1000.

      • You can enter an ID that ranges from 1 to 16777214.
      • The end ID must be equal to or greater than the start ID.
      • The two VNI IDs 16777215 and 16777216 are reserved by the system of this cloud platform.
    • Cluster: Optional. Attach the VXLAN pool to a cluster.

      • You can attach a VXLAN pool to a cluster when you create the VXLAN pool or after the VXLAN pool is created.
      • When you attach the VXLAN pool to a cluster, IP addresses of the compute nodes must be available in the cluster that correspond to the VTEP CIDR block.
    • VTEP CIDR: Enter the corresponding VTEP CIDR block.

    Create VXLAN Pool
  3. Create L2 private networks and attach them to the corresponding cluster. These L2 private networks are used to create L3 VPC networks.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L2 Network Resources > L2 Network. On the L2 Network page, click Create L2 Network. Then, the Create L2 Network page is displayed. On the displayed page, set the following parameters:

    • Zone: By default, the current zone is displayed.
    • Name: Enter a name for the L2 network, for example, L2-VXLAN1.
    • Description: Optional. Enter a description for the L2 network.
    • Switch Type: Select Linux Bridge.
    • Network Type: Select VxlanNetwork.
    • VXLAN Pool: Select a VXLAN pool of the software SDN type.
    • VNI: Optional. Enter a specified VNI in the VXLAN pool. If not specified, the Cloud allocates a VNI randomly.
    Create L2VxlanNetwork

    Similarly, create another L2 private network named as L2-VXLAN2.

  4. Specify a VPC vRouter to create L3 VPC networks.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L3 Network Resources > VPC Network. On the VPC Network page, click Create VPC Network. The Create VPC Network page appears. On the displayed page, set the following parameters:

    • Name: Enter a name for the VPC network, for example, VPC Network-1.

    • Description: Optional. Enter a description for the VPC network.

    • L2 Network: Select L2-VXLAN1.

    • VPC vRouter: Optional. You can specify a VPC vRouter when you create a VPC network or attach a VPC vRouter after you create the VPC network.

    • Network Address Type: Select IPv4.

    • Network Range Method: Select CIDR.

    • CIDR: Set a CIDR block for the VPC network, for example, 192.168.1.0/24.

    • Gateway: Optional. Set a gateway for the VPC network.

    • DHCP Service: Choose whether to enable the DHCP service.

      • The DHCP service is a built-in distributed service of the Cloud, which assigns IP addresses only to resources in the Cloud and does not conflict with your existing DHCP server.
      • By default, the DHCP service is enabled so that the NICs using this L3 network acquire IP addresses in a DHCP mode. You can customize a DHCP IP or use the DHCP IP that the system assigned according to the IP allocation policy.
      • If you disable this option, NICs using this L3 network acquire IP address in a Static mode. The Cloud does not assign IP addresses to NICs automatically. If the NICs need IP addresses, you need to configure IP addresses for them manually. In addition, you cannot specify a DHCP IP. Neither can the system allocate one.
      • IP Allocation Policy: Optional. If the DHCP service enabled, IP addresses can be assigned according to the following three allocation policies:

        • Random: The system randomly assigns IP addresses from the network range.

        • Allocate in Order:

          • The system assigns all available IP addresses from the network range in ascending order. Released IP addresses are assigned in the next allocation.
          • Example: Assume that the network range is 192.168.0.101~192.168.0.120, within which 192.168.0.101~192.168.0.108 are allocated. If 192.168.0.106 is released, it will be assigned first in the next allocation.
        • Allocate in Cycle:

          • The system assigns available IP addresses to VM instances from the network range in ascending order. Released IP addresses are assigned when currently available IP addresses are used up.
          • Example: Assume that the network range is 192.168.0.101~192.168.0.120, within which 192.168.0.101~192.168.0.108 are allocated. If 192.168.0.106 is released, it will be assigned after 192.168.0.120 is used.
      • DHCP IP: Optional. Set an IP address for the DHCP server, for example, 172.20.108.10.

        • A DHCP IP is an IP address used by the DHCP service to assign IP addresses to resources that use this L3 network.
        • If you create an L3 network for the first time with the DHCP service enabled, or if you add the first network range to an L3 network with the DHCP service enabled, you can customize the DHCP IP.
        • If the L3 network has a DHCP IP, you cannot customize the DHCP IP when you add a network range.
        • The DHCP IP can be in or outside the added IP range, but it must be an unoccupied IP address in the CIDR block of the added IP range
        • The IP range determined by the start IP and end IP cannot contain the link-local address 169.254.0.0/16.
        • If you select random as the IP allocation policy and this field is left blank, the system randomly assigns IP addresses from the added network range.
        • If you select allocate in order/allocate in cycle as the IP allocation policy and this field is left blank, the system uses the start IP address in the network range as the DHCP IP.
    • DNS: Optional. Provide DNS services for an L3 network.

    Create VPC Network

    Similarly, use L2-VXLAN2 to create another VPC network named as VPC Network-2.

  5. Use VPC Network-1 to create VM-1 on Host-1 and use VPC Network-2 to create VM-2 on Host-2.

    Use VPC Network to Create VM Instance
  6. Test the network connectivity between VPC Network-1 and VPC Network-2, and monitor traffic flow direction.

    1. Log in to VM-1, test whether VM-1 can successfully ping VM-2.

      VM-1 Ping VM-2
    2. Log in to VM-2, test whether VM-2 can successfully ping VM-1.

      VM-2 Ping VM-1
    3. On the main menu of ZStack Cloud, choose Resource Center > Network Resource > vRouter > VPC vRouter. On the VPC vRouter page, locate the VPC vRouter and enter its details page. On the details page, you can view the NIC monitoring data.

      NIC Monitoring Data

    As described above, VM-1 and VM-2 can communicate with each other. Traffic flows through the VPC vRouter and can be continuously monitored on the NIC monitoring card.

  7. Enable distributed routing, test the network connectivity between VPC Network-1 and VPC Network-2, and monitor traffic flow direction.

    1. On the main menu of ZStack Cloud, choose Resource Center > Network Resource > vRouter > VPC vRouter. On the VPC vRouter page, locate the VPC vRouter and enter its details page. On the details page, turn on the Distributed Routing switch.

      Enable Distributed Routing
    2. Log in to VM-1, test whether VM-1 can successfully ping VM-2.

      VM-1 Ping VM-2
    3. Log in to VM-2, test whether VM-2 can successfully ping VM-1.

      VM-2 Ping VM-1
    4. Log in to the management node and run the following API to view the distributed routing status.

      GetVpcVRouterDistributedRoutingConnections uuid=2f8631b5a13e4f918543565464b21bb0

      Enable Distributed Routing As described above, the distributed routing is successfully enabled and the Cloud begins to optimize east-west network traffic.

    5. On the main menu of ZStack Cloud, choose Resource Center > Network Resource > vRouter > VPC vRouter. On the VPC vRouter page, locate the existing VPC vRouter and enter its details page. On the details page, view the NIC monitoring data.

      NIC Monitoring Data

    As described above, after the traffic between VM-1 and VM-2 is first connected through the VPC vRouter, the subsequent traffic will be directly sent between VM-1 and VM-2. The NIC monitor does not detect traffic flows as expected, indicating that the distributed routing successfully takes effect.

So far, we have introduced how to use a distributed routing.

VPC vRouter HA Group

Typical scenario of VPC vRouter HA group: Create a VPC vRouter HA group on ZStack Cloud. Either VPC vRouter in the group can be a primary or secondary VPC vRouter. If the primary VPC vRouter does not work as expected, the VPC vRouter becomes the secondary VPC vRouter in the group to ensure high availability of business.

To use a VPC vRouter HA group, follow these steps:

  1. Create a VPC vRouter HA group.
  2. Create a VPC network using the VPC vRouter HA group.
  3. Create a VM instance using the VPC network.
  4. Test whether the VPC vRouter HA group works.

The following tables list the assumed environment configurations.

  1. Public Network

    Public Network Configuration
    NIC em01
    VLAN ID N o VLAN
    IP Range 172.24.19.64~172.24.19.79
    Netmask 255.255.0.0
    Gatway 172.24.0.1
  2. Management Network

    Management Network Configuration
    NIC em02
    VLAN ID No VLAN
    IP Range 192.168.18.64~192.168.18.79
    Netmask 255.255.0.0
    Gateway 192.168.0.1
    • For security and stability reasons, we recommend that you deploy an independent management network and separate it from the public networks.
    • The management network we mentioned here is the same as that in ZStack Private Cloud. That is, the management network is the network used to manage hosts, primary storages, and backup storages. If a management network was created before, you can use it directly.
  3. VPC Network

    Private Network Configuration
    NIC em01
    VLAN ID 2768
    IP CIDR 10.18.97.0/24
    Gateway 10.18.97.1
    DHCP IP 10.18.97.2

The following section describes the detailed steps of how to use a VPC vRouter HA group.

  1. Create a VPC vRouter HA group and add VPC vRouters to the group. The Cloud automatically configures the peer vRouters with the same configurations. For more information, you can refer to User Guide.

    VPC vRouter HA Group
  2. Specify a VPC vRouter in the HA Group to create a VPC network.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L3 Network Resources > VPC Network. On the VPC Network page, click Create VPC Network. The Create VPC Network page appears. On the displayed page, set the following parameters:

    • Name: Enter a name for the VPC network.

    • Description: Optional. Enter a description for the VPC network.

    • L2 Network: Select an L2 network for the VPC network.

    • VPC vRouter: Optional. Select a VPC vRouter in the HA group.

    • Network Address Type: Select IPv4.

    • Network Range Method: Select CIDR.

    • CIDR: Enter 10.18.97.0/24.

      The CIDR block must not overlap.

    • Gateway: Optional. Set a gateway for the VPC network.

    • DHCP Service: Optional. Choose whether to enable the DHCP service.

      • IP Allocation Policy: Optional. After the DHCP service is enabled, select Random.
      • DHCP IP: Optional. Set an IP address for the DHCP server, for example, 10.18.97.2.
    • DNS: Optional. Provide DNS services for an L3 network.

    Create VPC Network
  3. Create a VM instance using the VPC network.

    On the main menu of ZStack Cloud, choose Resource Center > Resource Pool > Virtual Resource > VM Instance. On the VM Instance page, click Create VM Instance. Then, the Create VM Instance page is dispayed. On the displayed page, set the following parameters:

    • Name: Enter a name for the VM instance.

    • Description: Optional. Enter a description for the VM instance.

    • Quantity: Enter the number of VM instances to be created. You can create VM instances in bulk.

    • Tag: Optional. Bind one or more tags to the VM instance.

    • Group: Optional. Choose a group for the VM instance. If you do not set this parameter, VM instance goes to the default group.

    • Instance Offering: Select an existing instance offering.

    • Image: Select an existing image.

    • Root Disk Offering: Select an existing disk offering for the root volume of the VM instance.

    • Data Volume: Optional. Choose whether to create data volumes and attach the volumes to the VM instance.

    • Network Configurations: Select the created VPC network.

      • Make Default: Optional. Set on of the selected networks as the default network.
      • Assign IP: Optional. Choose whether to assign an IP address to the VM NIC.
      • MAC Address: Optional. Choose whether to configure a MAC address for the VM instance.

      You can click Add Network Configuration to configure different networks.

    • User Data: Optional. Inject user-defined parameters or scripts to customize configurations for the VM instance or to accomplish specific tasks.

  4. Test whether the VPC vRouter HA group works.

    1. Launch the VM console and test whether it can successfully ping an Internet address for example, www.baidu.com.

      VM Ping Internet Address
    2. Stop the primary VPC vRouter in the HA group to simulate the exception state of a VPC vRouter. The secondary VPC vRouter will automatically become the primary VPC vRouter in the group. In the mean time, you can check the ping information.

      Stop Primary VPC vRouter
      VM Ping Internet Address

    As described above, the secondary VPC vRouter automatically becomes the primary VPC vRouter, if the primary VPC vRouter does not work as expected. The VM can still successfully ping the Internet address, only with a short period of network latency. So, the VPC vRouter HA group successfully takes effect.

So far, we have introduced how to use a VPC vRouter HA group.

Firewall

Typical scenario of firewwall: The user has multiple VM instances deployed on the same VPC network, accessing external dependencies and update services through the public network. To prevent source code leakage and reduce security risks, these VM instances need to be restricted from directly accessing the public network. By deploying a VPC firewall and configuring ingress rules, you can control the return traffic forwarded through the VPC vRouter, achieving unified restrictions on public network access for VM instances.

Assume that the user environment is as follows:

  1. Public Network

    Public Network Configuration
    NIC em01
    VLAN ID No VLAN
    IP Range 10.108.10.100~10.108.10.200
    Netmask 255.0.0.0
    Gateway 10.0.0.1
    DHCP IP 10.108.10.101
  2. Management Network

    Management Network Configuration
    NIC em02
    VLAN ID No VLAN
    IP Range 192.168.29.10~192.168.29.20
    Netmask 255.255.255.0
    Gateway 192.168.29.1
    • For security and stability reasons, we recommend that you deploy an independent management network and separate it from the public networks.
    • The management network we mentioned here is the same as that in ZStack Private Cloud. That is, the management network is the network used to manage hosts, primary storages, and backup storages. If a management network was created before, you can use it directly.
  3. VPC Network

    Private Network Configuration
    NIC em01
    VLAN ID 2800
    IP CIDR 192.168.1.0/24
    DHCP IP 192.168.1.2

To use a firewall, follow these steps:

  1. Create a VPC network.
  2. Create a VM instance using the VPC network.
  3. Create a VPC firewall.
  4. Configure VPC firewall ingress rules.
  5. Test the network connectivity between the VM instances(VPC network and pubic network).
  1. Create a VPC network.

    Create a VPC network based on the pre-planned network configuration, and set the VPC vRouter name to VPCvRouter and the VPC network name to VPC-L3.

    For detailed steps, see IPv4 Basic Deployment.

  2. Create a VM instance using the VPC network.

    Create a VM instance, set the name to VM-VPC, and attach the created VPC network VPC-L3. Other parameters such as instance offering and image can be configured based on actual requirements.

  3. Create a VPC firewall.

    On the ZStack Cloud main menu, choose Resource Center > Network Service > Advanced Network Service > Firewall. On the Firewall page, click Create Firewall. On the displayed Create Firewall page, set the following parameters:

    • Name: Set to VPC-Firewall.

    • Description: Optional. You can leave it empty.

    • VPC vRouter: Set to VPCvRouter.

      To create a firewall, the VPC vRouter must be running and not bindded to any firewall.

    As shown in Figure 106: Create VPC Firewall:

    Create VPC Firewall
  4. Configure VPC firewall ingress rules.

    In a VPC network, when a VM instance accesses the public network, the return traffic passes through the VPC vRouter. By controlling the return traffic in the ingress rule set, you can block VM instances from initiating connections to the public network. Therefore, this scenario restricts public network access by configuring ingress rules.

    On the Rules tab of the firewall details page, select Ingress and click Add Rule. On the displayed Add Rule page, set the following parameters:

    • Priority: Set the rule priority to 1001.

      • The priority range is 1001-2999. A smaller number indicates a higher priority.
      • The priority of each rule in the same rule set must be unique.
    • Action: Select Drop.

      • Accept: Allow network requests on the VPC vRouter to pass through.
      • Drop: Block network requests on the VPC vRouter without sending feedback to the requester.
      • Reject: Block network requests on the VPC vRouter and send rejection feedback to the requester.
    • Packets Status: Optional. Do not select.

    • Protocol: Select TCP.

    • Source IP Address: Enter the IP address of the VPC VM instance.

    • Destination IP Address: Enter the IP range of L3-Public: 10.108.10.100-10.108.10.200.

    • Enable Now: Turn on Enable Now.

    As shown in Figure 107: Create Rule:

    Create Rule

    Similarly, add rules for UDP and ICMP protocols with priority set to 1002 and 1003.

  5. Test the network connectivity between the VM instances(VPC network and pubic network).

    1. Create a VM instance using the public network.

      Create a VM instance, set the name to VM-Public, and attach the public network.

    2. Verify the TCP protocol rule.

      Use the iperf command to verify the TCP protocol rule, with VM-VPC as the sender and VM-Public as the receiver.

      Run iperf -s on the receiver. Run iperf -c x.x.x.x (receiver IP address) -i 1 -t 1000 on the sender. Check the network status as shown in Figure 108: TCP Protocol Verification:

      TCP Protocol Verification
      TCP Protocol Verification (2)

      As shown above, after setting the rule, TCP protocol network requests cannot be sent, as expected.

    3. Verify the UDP protocol rule.

      Use the iperf command to verify the UDP protocol rule, with VM-VPC as the sender and VM-Public as the receiver.

      Run iperf -s -u on the receiver. Run iperf -c x.x.x.x (receiver IP address) -u -i 1 -t 1000 on the sender. Check the network status as shown in Figure 109: UDP Protocol Verification:

      UDP Protocol Verification
      UDP Protocol Verification (2)

      As shown above, after setting the rule, UDP protocol network requests cannot be received after being sent, as expected.

    4. Verify the ICMP protocol rule.

      Log in to VM-VPC and check whether it can ping VM-Public, as shown in Figure 110: ICMP Protocol Verification:

      ICMP Protocol Verification

      As shown above, after setting the rule, ICMP protocol network requests cannot be sent, as expected.

This completes the introduction to using the VPC firewall.

Netflow

A NetFlow monitors the ingress and egress traffic of the NICs of VPC vRouters. The supported versions of data flows are V5 and V9.

Typical scenario of Netflow: Assume that the user has a set of VPC network environment and needs to analyse the ingress and egress traffic of a certain NIC. The user can use a Netflow to transmit the traffic information to analysis software.

To use a Netflow, follow these steps:

  1. Create a VM instance using a VPC network.
  2. Create a VM instance using a public network.
  3. Add a Netflow.
  4. Test whether the Netflow works.

The following tables list the assumed environment configuration.

  1. Public Network

    Public Network Configuration
    NIC em01
    VLAN ID No VLAN
    IP Range 10.151.0.100~10.151.0.200
    Netmask 255.0.0.0
    Gateway 10.0.0.1
    DHCP IP 10.151.0.101
  2. Management Network

    Management Network Configuration
    NIC em02
    VLAN ID No VLAN
    IP Range 192.168.29.10~192.168.29.20
    Netmask 255.255.255.0
    Gateway 192.168.29.1
    • For security and stability reasons, we recommend that you deploy an independent management network and separate it from the public networks.
    • The management network we mentioned here is the same as that in ZStack Private Cloud. That is, the management network is the network used to manage hosts, primary storages, and backup storages. If a management network was created before, you can use it directly.
  3. VPC Network

    Private Network Configuration
    NIC em01
    VLAN ID 2800
    IP CIDR 192.168.3.0/24
    DHCP IP 192.168.3.2

The following section describes the detailed steps of how to use a Netflow.

  1. Create VM instances.

    Create a VM instance using the VPC network according to planned network configuration. Set the VM name as Flow-Sender. For more information, see Basic Deployment.

    Similarly, create another VM instance using the public network and set the VM name as Flow-Collector.

  2. Add a Netflow.

    On the main menu of ZStack Cloud, choose Resource Center > Network Service > Advanced Network Service > Netflow. On the Netflow page, click Add Netflow. Then, the Add Netflow page is displayed. On the displayed page, set the following parameters:

    • Name: Enter a name for the Netflow.

    • Description: Optional. Enter a description for the Netflow.

    • IP: Enter the IP address of Flow-Collector.

    • Port: Enter 2055.

      Make sure that the configured IP and port suite of the receiver is correct. Otherwise, the Netflow service may not work as expected.

    • Version: Select V5.

      The output data format varies depending on the Netflow version. Select a Netflow version based on your business requirements.

    • Export Interval: Enter 60.

    • Routing Configuration: Optional. Set the VPC vRouters and networks that you want to monitor.

    Add Netflow
  3. Test whether the Netflow works.

    In this scenario, we use the iperf command to send network traffic and the tshark software to collect Netflow traffic information.

    1. Run the iperf -s command in the Flow-Collector system. Run the iperf -c $Flow-Collector IP address -t 60 -P 10 in the Flow-Sender system. Then, check whether the traffic is received.

      Send Network Traffic
    2. Run the tshark -f "udp port 2055 and ip src 192.168.3.253 " -i eth0 -V -c 1 -a duration:500 command in the Flow-Collector system. Then, you can view the captured packets information in the analysis software.

      tshark Packet Capture Information
    3. As described above, when the traffic passes through the NIC of a VPC vRouter, the Netflow takes effect and forwards the traffic information to the analysis software.

So far, we have introduced how to use a Netflow.

Port Mirroring

Typical scenario of Netflow: Assume that the user has key business services running on VM-2, so the user wants to monitor the traffic that flows in and out of VM-2 for analysis. To ensure that the business services are not affected on VM-2, the user decides to create a port mirroring for VM-2 on the Cloud. This way, the created port mirroring will mirror the data traffic of VM-2 NIC and sends the data traffic to the target VM-1 for analysis.

To use a port mirroring, follow these steps:

  1. Create a VPC network, VM-1, and VM-2.
  2. Create an L2 network for a flow network.
  3. Create a flow network.
  4. Create a port mirroring.
  5. Add a session to the port mirroring with the VM-2 NIC as the source port and the VM-1 NIC as the destination port.
  6. Test whether the port mirroring works.

The following tables list the assumed environment configuration.

Management/Public Network Configuration
NIC eth0
VLAN ID NoVLAN
IP Range 172.26.56.161~172.26.56.170
Netmask 255.255.0.0
Gateway 172.26.0.1
VPC Network Configuration
NIC eth0
VLAN ID 2800
IP CIDR 10.81.110.0/24
Netmask 255.255.255.0
Gatway 10.81.110.1
Flow Network Configuration
NIC eth0
VLAN ID 2900
IP CIDR 10.81.111.0/24
Netmask 255.255.255.0
Gateway 10.81.111.1
  1. Create a VPC network, VM-1, and VM-2.

    1. Create a VPC network according to the environment configurations above. Then, create 2 VM instances, VM-1 and VM-2, on this VPC network.

    2. Attach the second NIC to VM-1.

      Enter the details page of VM-1. Choose Configuration Info > NIC > Attach and attach the second NIC to VM-1. In this scenario, the second NIC uses the public network.

      Attach Second NIC to VM-1
  2. Create an L2 network for a flow network.

    Creates an L2 network according to the environment configurations.

  3. Create a flow network.

    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > Dedicated Network > Flow Network. On the Flow Network page, click Create Flow Network to create a flow network according to the environment configurations.

  4. Create a port mirroring.

    On the main menu of ZStack Cloud, choose Resource Center > Network Service > Advanced Network Service > Port Mirroring. On the Prot Mirroring page, click Create Port Mirroring. Then, the Create Port Mirroring page appears.

    On the displayed page, set the following parameters:

    • Name: Enter a name for the port mirroring.

    • Description: Optional. Enter a description for the port mirroring.

    • Flow Network: Select a flow network for port mirroring.

      • A flow network is a dedicated network for port mirroring. You can use a flow network to transmit the mirrors of data packets of NIC ports to the target ports.
      • You cannot use a flow network for other purposes except for port mirroring.
      • A port mirroring occupies a flow network.
      • The VM instances for which port mirroring is configured must reside in the cluster where the associated flow networks are located.
    • Enable Now: Optional. Choose whether to enable port mirroring immediately after the port mirroring is created. Enabling port mirroring immediately after the creation may occupy physical network bandwidth. Make sure that your business is not affected and then select the checkbox.

  5. Add a session to the port mirroring.

    Enter the details page of the port mirroring. Choose Session > Add Session. Then, the Add Session page appears.

    On the displayed page, set the following parameters:

    • Name: enter a name for the session.
    • Type: Select Bidirection.
    • Source VM: Select VM-2.
    • Source NIC: Select the VM-2 NIC.
    • Destination VM: Select VM-1.
    • Destination NIC: Select the VM-1 NIC that is not the default NIC.
    Add Session
  6. Test whether the port mirroring works.

    1. Enter the console of the VM-2. Run the command ping ${DhcpServerIp} to make VM-2 send ICMP packets to the DHCP server.

      Source VM Sends ICMP Packets
    2. Enter the console of the VM-1. Run the command tcpdump -eni eth1 icmp to check whether the VM-1 can receive the ICMP packets mirrored by the port mirroring. eth1 is the port name of the destination NIC. You can run ifconfig -a to query the NIC port name.

      Destination VM Receives ICMP Packets

So far, the destination VM has copied the network message of the source VM through the port mirroring. The port mirroring takes effect as expected, and the user can use the network messages received by VM-1 for monitoring and analysis.

Glossary

Instance: An instance is a virtual machine or server that runs the images of operating systems in Cloud, such as VM instance and elastic baremetal instance.

VM Instance: A VM instance is a virtual machine instance running on a host. A VM instance has its own IP address and can access public networks and run application services.

Volume: A volume provides storage space for a VM instance. Volumes are categorized into root volumes and data volumes.

Root Volume: A root volume provides support for the system operations of a VM instance.

Data Volume: A data volume provides extended storage space for a VM instance.

Image: An image is a template file used to create a VM instance or volume. Images are categorized into system images and volume images.

Instance Offering: An instance offering defines the number of vCPU cores, memory size, network bandwidth, and other configuration settings of VM instances.

Disk Offering: A disk offering defines the capacity and other configuration settings of volumes.

GPU Specification: A GPU specification defines the frame per second (FPS), video memory, resolution, and other configuration settings of a physical or virtual GPU. GPU specifications are categorized into physical GPU specifications and virtual GPU specifications.

vNUMA Configuration: vNUMA uses CPU pinning to passthrough the topology of associated host physical NUMA (pNUMA) nodes to a VM instance, generating a topology of virtual NUMA (vNUMA) nodes for the VM instance. This topology enables a vCPU on a vNUMA node to primarily access the local memory and thus improves VM performance.

NUMA (Non-Uniform Memory Access): Non-uniform memory access (NUMA) is a computer memory design where the memory access time depends on the memory location relative to the CPU. Under NUMA, a processor can access its own local memory faster than non-local memory and thus improves VM performance.

pNUMA Node (physical NUMA Node): A pNUMA node (physical NUMA node) is a host NUMA node predefined based on the host NUMA architecture. It is used to manage the CPUs and memory of the host.

pNUMA Topology (physical NUMA Topology): A pNUMA topology (physical NUMA topology) is the topology of the host NUMA nodes predefined by the CPU vendor based on the host NUMA architecture.

vNUMA Node (virtual NUMA Node): A vNUMA node (virtual NUMA node) is generated by passing-through associated pNUMA nodes via CPU pinning. It is used to manage the CPUs and memory of a VM instance.

vNUMA Topology (virtual NUMA Topology): A vNUMA topology (virtual NUMA topology) is the topology of VM NUMA nodes generated by passing-through associated pNUMA nodes via CPU pinning.

Local Memory: Local memory is the memory that a CPU (pCPU or vCPU) accesses through the Uncore iMC (Integrated Memory Controller) of the same NUMA (pNUMA or vNUMA) node. Compared with accessing non-local memory, accessing local memory has lower latencies.

CPU Pinning: CPU pinning assigns the virtual CPUs (vCPUs) of a VM instance to specific physical CPUs (pCPUs) of the host, which improves VM performance.

EmulatorPin Configuration: EmulatorPin assigns all other threads than virtual CPU (vCPU) threads and IO threads of a VM instance to physical CPUs (pCPUs) of the host so that these threads run on assigned pCPUs.

Auto-Scaling Group: An auto-scaling group is a group of VM instances that are used for the same scenarios. An auto-scaling group can automatically scale out or in based on application workloads or health status of VM instances in the group.

Snapshot: A snapshot is a point-in-time capture of data status in a volume.

Affinity Group: A VM scheduling policy is a resource orchestration policy based on which VM instances are assigned hosts to achieve the high performance and high availability of businesses.

Zone: A zone is a logical group of resources such as clusters, L2 networks, and primary storage. Zone is the largest resource scope defined in the Cloud.

Cluster: A cluster is a logical group of hosts (compute nodes).

Host: A host provides compute, network, and storage resources for VM instances.

Primary Storage: A primary storage is one or more servers that store volume files of VM instances. These files include root volume snapshots, data volume snapshots, image caches, root volumes, and data volumes.

Image Storage: An image storage is a storage server that stores VM image templates, including ISO image files.

iSCSI Storage: iSCSI storage is an SAN storage that uses the iSCSI protocol for data transmission. You can add an iSCSI SAN block as a Shared Block primary storage or pass through the block to a VM instance.

FC Storage: FC storage is an SAN storage that uses the FC technology for data transmission. You can add an FC SAN block as a Shared Block primary storage or pass through the block to a VM instance.

NVMe Storage: A type of storage implemented via the NVMe-oF (NVMe over fabrics) protocol. You can add a block device configured from an NVMe storage as SharedBlock primary storage.

L2 Network: An L2 network is a layer 2 broadcast domain used for layer 2 isolation. Generally, L2 networks are identified by names of devices on the physical network.

VXLAN Pool: A VXLAN pool is a collection of VXLAN networks established based on VXLAN Tunnel Endpoints (VTEPs). The VNI of each VXLAN network in a VXLAN pool must be unique.

L3 Network: An L3 network includes IP ranges, gateway, DNS, and other network configurations that are used by VM instances.

Public Network: Generally, a public network is a logical network that is connected to the Internet. However, in an environment that has no access to the Internet, you can also create a public network.

Flat Network: A flat network is connected to the network where the host is located and has direct access to the Internet. VM instances in a flat network can access public networks by using elastic IP addresses.

VPC Network: A VPC network is a private network where VM instances can be created. A VM instance in a VPC network can access the Internet through a VPC vRouter.

Management Network: A management network is used to manage physical resources in the Cloud. For example, you can create a management network to manage access to hosts, primary storage, image storage, and VPC vRouters.

Flow Network: A flow network is a dedicated network for port mirror transmission. You can use a flow network to transmit the mirrors of data packets of NIC ports to the target ports.

VPC vRouter: A VPC vRouter is a dedicated VM instance that provides multiple network services.

VPC vRouter HA Group: A VPC vRouter HA group consists of two VPC vRouters. Either VPC vRouter can be a primary or secondary VPC vRouter for the group. If the primary VPC vRouter does not work as expected, the VPC vRouter becomes the secondary VPC vRouter in the group to ensure high availability of business.

vRouter Image: A vRouter image encapsulates network services and can be used to create VPC vRouters.

Dedicated-Performance LB Image: A dedicated-performance load balancer (LB) image encapsulates dedicated-performance load-balancing services and can be used to create load balancer instances. However, a dedicated-performance load balancer image cannot be used to create VM instances.

vRouter Offering: A vRouter offering defines the number of vCPU cores, memory size, image, management network, and public network configuration settings of VPC vRouters. You can use a vRouter offering to create VPC vRouters that can provide network services for public networks and VPC networks.

LB Instance Offering: A load balancer (LB) instance offering defines the CPU, memory, image, and management network configuration settings used to create LB instances. LB instances provide load balancing services for the public network, flat network, and VPC network.

SDN Controller: The SDN controller is the core of the SDN architecture, responsible for centralized management and control of network devices.

SDN Cluster: A cluster of dedicated VM instances designed to provide highly available SDN capabilities.

SDN Instance: A dedicated VM instance designed to provide SDN network capabilities.

SDN Image: An SDN image encapsulates an SDN software and can be used to create SDN instances.

SDN Instance Offering: An SDN instance offering defines the CPU, memory, SDN image, and management network configuration used for creating SDN instances.

Security Group: A security group provides security control services for VM NICs. It filters the ingress or egress TCP, UDP, and ICMP packets of VM NICs based on the specified security rules.

VIP: In bridged network environments, a virtual IP address (VIP) provides network services such as serving as an elastic IP address (EIP), port forwarding, load balancing, IPsec tunneling. When a VIP provides the preceding network services, packets are sent to the VIP and then routed to the destination network where VM instances are located.

EIP: An elastic IP address (EIP) functions based on the NAT technology. IP addresses in a private network are translated into an EIP that is in another network. This way, private networks can be accessed from other networks by using EIPs.

Port Forwarding: Port forwarding functions based on the layer-3 forwarding service of VPC vRouters. This service forwards traffic flows of the specified IP addresses and ports in a public network to specified ports of VM instances by using the specified protocol. If your public IP addresses are insufficient, you can configure port forwarding for multiple VM instances by using one public IP address and port.

Load Balancer: A load balancer distributes traffic flows of a virtual IP address to backend servers. It automatically inspects the availability of backend servers and isolates unavailable servers during traffic distribution. This way, the load balancer improves the availability and service capability of your business.

Listener: A listener monitors the frontend requests of a load balancer and distributes the requests to a backend server based on the specified policy. In addition, the listener performs health checks on backend servers.

Forwarding Rule: A forwarding rule forwards the requests from different domain names or URLs to different backend server groups.

Backend Server Group: A backend server group is a group of backend servers that handles requests distributed by load balancers. It is the basic unit for traffic distribution by load balancer instances.

Backend Server: A backend server handles requests distributed by a load balancer. You can add a VM instance on the Cloud or a server on a third-party cloud as a backend server.

Frontend Network: A frontend network is a type of network that is associated with a load balancer. Requests from the network are distributed by the load balancer to backend servers based on a specified policy.

Backend Network: A backend network is a type of network that is associated with a load balancer. Requests from frontend networks are distributed by the load balancer to servers in the backend network.

Load Balancer Instance: A load balancer instance is a custom VM instance used to provide load balancing services.

Certificate: If you select HTTPS for a listener, associate it with a certificate to make the listener take effect. You can upload either a certificate or certificate chain.

Firewall: A firewall is an access control policy that monitors ingress and egress traffic of VPC vRouters and decides whether to allow or block specific traffic based on the associated rule sets and rules.

Firewall Rule Set: A firewall rule set is a set of rules that a firewall uses to defend against network attacks. You need to associate a rule set with the egress or ingress flow direction of VPC vRouter NICs to make the rule set take effect.

Firewall Rule: A firewall rule is an access control entry associated with the egress or ingress flow direction of VPC vRouter NICs to defend against network attacks. A firewall rule includes rule priority, match condition, and behavior.

Rule Template: A rule template is a template that you can select when you add rules to a rule set or a firewall.

IP/Port Set: An IP or port set is a set of IP addresses or ports that you can select when you add rules to a rule set or a firewall.

IPsec Tunnel: An IPSec tunnel encrypts and verifies IP packets that transmit over a virtual private network (VPN) from one site to another.

OSPF Area: An Open Shortest Path First (OSPF) area is divided from an autonomous system based on the OSPF protocol. This simplifies the hierarchical management of vRouters.

NetFlow: A NetFlow monitors the ingress and egress traffic of the NICs of VPC vRouters. The supported versions of data flows are V5 and V9.

Port Mirroring: Port mirroring mirrors the traffic data of VM NICs and sends the traffic data to the target ports. This allows for the analysis of data packets of ports and simplifies the monitoring and management of data traffic and makes it easier to locate network errors and exceptions.

Route Table: A route table contains information about various routes that you configure. Route entries in a route table must include the destination network, next hop, and route priority.

CloudFormation: CloudFormation is a service that simplifies the management of cloud resources and automates deployment and O&S. You can create a stack template to configure cloud resources and their dependencies. This way, resources can be automatically configured and deployed in batches. CloudFormation provides easy management of the lifecycle of cloud resources and integrates automatic O&S into API and SDK.

Resource Stack: A resource stack is a stack of resources that are configured by using a stack template. The resources in the stack have dependencies with each other. You can manage resources in the stack by managing the resource stack.

Stack Template: A stack template is a UTF8-encoded file based on which you can create resource stacks. The stack template defines the resources that you want, the dependencies between the resources, and the configuration settings of the resources. When you use a stack template to create a resource stack, CloudFormation parses the template and the resources are automatically created and configured.

Sample Template: A sample template is a commonly used resource stack. You can use a sample template provide by the Cloud to create resource stacks.

Designer: A designer is a CloudFormation tool that allows you to orchestrate cloud resources. You can drag and drop resources on a canvas and use lines to establish dependencies between the resources.

Baremetal Cluster: A baremetal cluster consists of baremetal chassis. You can manage baremetal chassis by managing a baremetal cluster where the chassis reside.

Deployment Server: A deployment server is a server that provides PXE service and console proxy service for baremetal chassis.

Baremetal Chassis: A baremetal chassis is used to create a baremetal instance and is identified based on the BMC interface and IPMI configuration setting.

Preconfigured Template: A preconfigured template is used to create a preconfigured file that allows for unattended batch installation of an operating system for baremetal instances.

Baremetal Instance: A baremetal instance is an instantiated baremetal chassis.

Elastic Baremetal Management: Elastic Baremetal Management provides dedicated physical servers for your applications to ensure high performance and stability. In addition, this feature allows elastic scaling. You can apply for and scale resources based on your needs.

Provision Network: A provision network is a dedicated network for PXE boot and image downloads while creating elastic baremetal instances in a gateway proxy cluster.

Elastic Baremetal Cluster: Provides a separated cluster to manage baremetal nodes.

Gateway Node: A gateway node is a node where the ingress and egress traffic of the Cloud and elastic baremetal instances in gateway proxy clusters is forwarded.

Baremetal Node: A baremetal node is used to create a baremetal instance and is identified based on the BMC interface and IPMI configuration setting.

Elastic Baremetal Instance: An elastic baremetal instance has the same performance as physical servers and allows elastic scaling. You can apply for and scale resources based on your needs.

Elastic Baremetal Offering: An elastic baremetal offering defines the number of vCPU cores, memory size, CPU architecture, CPU model, and other configuration settings of elastic baremetal instances.

vCenter: The Cloud allows you to take over vCenter and manage resources on the vCenter.

VM Instance: A VM instance is an ESXi virtual machine instance running on a host. A VM instance has its own IP address to access public networks and can run application services.

Network: A vCenter network defines the network settings of VM instances on vCenter, such as IP range, gateway, DNS, and network services.

Volume: A volume provides storage space for a VM instance on vCenter. A volume attached to a VM instance can be used as a root volume or data volume. A root volume provides support for the system operations of a VM instance. A data volume provides extended storage space for a VM instance.

Image: An image is a template file used to create a VM instance or volume on vCenter. Images are categorized into system images and volume images.

Event Message: Event Message displays event alarm messages of vCenter that is took over by the Cloud. This feature allows you to locate errors and exceptions efficiently.

Network Topology: A network topology visualizes the network architecture of the Cloud. It allows for efficient planning, management, and improvement of network architecture. Network topologies can be categorized into global topologies and custom topologies.

Performance Analysis: Performance Analysis displays the performance metrics of key resources monitored externally or internally in the Cloud. You can view the performance analysis or export the analysis report as needed to improve the O&M efficiency.

Capacity Management: Capacity Management visualizes the capacities and usages of key resources in the Cloud. You can use this feature to improve O&S efficiency.

MN Monitoring: Management Node (MN) monitoring allows you to view the health status of each management node when you use multiple management nodes to achieve high availability.

Alarm: An alarm is used to monitor the status of time-series data and events and respond to the status change. Alarms can be categorized into resource alarm, event alarm, and extended alarm.

One-Click Alarm: A one-click alarm integrates multiple metrics of a resource. You can create one-click alarms for multiple resources to monitor these resources.

Alarm Template: An alarm template is a template of alarm rules. If you associate an alarm template with a resource group, an alarm is created to monitor the resources in the group.

Resource Group: A resource group consists of resources grouped based on your business needs. If you associate an alarm template with a resource group, the alarm rules specified by the template take effect on all the resources in the group.

Message Template: A message template specifies the text template of a resource alarm message or event alarm message sent to an SNS system.

Message Source: A message source is used to take over extended alarm messages. If you configure alarms for message sources, extended alarm messages can be sent to various endpoints.

Endpoint: An endpoint is a method that users obtain subscribed messages. Endpoints are categorized into system endpoints, email, DingTalk, HTTP application, short message service, and Microsoft Teams.

Alarm Message: An alarm message is a message sent the time when an alarm is triggered.

Current Task: A current task is an ongoing operation performed in the Cloud. You can perform centralized management over ongoing operations.

Operation Log: An operation log is a chronological record of operations on the specified objects and their operation results.

Audit: Audit monitors and records all activities on the Cloud. You can use this feature to implement operation tracking, cybersecurity classified protection compliance, security analysis, troubleshooting, and automatic O&M.

Log Collection: Allows you to collect with one click the log data from the Cloud and various nodes on the Cloud generated in the specified time period and download the log data.

One-Click Inspection: Comprehensively inspects the health status of key resources and services of the Cloud and scores their healthiness based on the inspection results. In addition, the one-click inspection service provides O&M suggestions and inspection reports.

Backup Management: Backup management integrates multiple disaster recovery technologies such as incremental backup and full backup that are suitable for multiple business scenarios. You can implement local backup and remote backup based on your business needs.

Backup Job: You can create a backup job to back up local VM instances, volumes, or databases to a specified storage server on a regular basis.

Local Backup Data: Local backup data of VM instances, volumes, and databases is stored in the local backup server.

Local Backup Server: A local backup server is located at the local data center and is used to store local backup data.

Remote Backup Server: A remote backup server is located at a remote data center or a public cloud and is used to store remote backup data.

Continuous Data Protection (CDP): Continuous Data Protection (CDP) provides second-level and fine-grained continuous backups for important business systems in VM instances, allowing users to restore VM data to a specific time state, and retrieve files without restoring the system.

CDP Task: You can create a CDP task to continuously back up your VM data to a specified backup server to achieve continuous data protection and recovery.

CDP Data: The backup data generated from continuous data protection on VM instances is stored in local backup servers.

Recovery Point: A recovery point is a data point generated during continuous data protection. A recovery point corresponds to a data record within the recovery point interval specified by the user.

Locked Recovery Point: You can lock or unlock a recovery point as needed. After a recovery point is locked, data of the recovery point will not be automatically cleared or deleted.

Recovery Task: A recovery task helps you quickly restore data by specifying a CDP task and recovery point, and allows you to view the recovery progress and logs in a more friendly way.

Cryptography Security Compliance: The Cryptography Security Compliance service provides applications with cloud security capabilities based on commercial cryptography, meeting the requirements of commercial cryptography application security assessments.

HSM Pool: An HSM pool is a logical group of hardware security modules (HSMs) and is used to provide unified cryptography services such as signature validation and encryption.

HSM: A hardware security module (HSM) is a dedicated device that encrypts, decrypts, and authenticates information by using the cryptographic technology.

Platform Cryptography Security Compliance: Enables the Cloud to meet the requirements of Cryptography Security Compliance through the cryptography capabilities provided by HSM pools.

Certificate Login: Authenticates the identity of a user by using a UKey device.

Data Protection: Protects important data on the Cloud to ensure the data confidentiality and integrity.

Scheduled Job: A scheduled job defines that a specific action be implemented at a specified time based on a scheduler.

Scheduler: A scheduler is used to schedule jobs. It is suitable for business scenarios that last for a long time.

Tag: A tag is used to mark resources. You can use a tag to search for and aggregate resources.

Migration Service: The Cloud provides V2V migration service that allows you to migrate VM instances and data from other virtualized platform to the current cloud platform.

ZMigrate Migration Service: A migration service installed from Application Market that migrates VM instances and their data from VMware environments to the current cloud platform.

V2V Migration: V2V Migration allows you to migrate VM instances from the VMware or KVM platform to the current cloud platform.

V2V Conversion Host: A V2V conversion host is a host in the destination cluster that you need to specify during V2V migration to cache VM instances and data when you implement V2V migration. After the VM instances and data are cached in the V2Vconversion host, they are migrated to the destination primary storage.

User: A user is a natural person that constructs the most basic unit in Tenant Management.

User Group: A user group is a collection of natural persons or a collection of project members. You can use a user group to grant permissions.

Role: A role is a collection of permissions that can be granted to users. A user that assumes a role can call API operations based on the permissions specified by the role. Roles are categorized into platform roles and project roles.

Single Sign-On: The Single Sign-On service provided by the Cloud. It supports seamless access to SSO systems. Through the service, related users can directly log in to the Cloud and manage cloud resources.

Project: A project is a task that needs to be accomplished by specific personnel at a specified time. In Tenant Management, you can plan resources at the project granularity and allocate an independent resource pool to a project. The word Tenant in Tenant Management mainly refers to projects. A project is a tenant.

Project Member: A project member is a member in a project who is granted permissions on specific project resources and can use the resources to accomplish tasks. Project members include the project admin, project managers, and normal project members.

Process Management: Process management is part of ticket management that manages the processes related to the resources of projects. Processes can be categorized into default processes and custom processes.

My Approvals: In the Cloud, only the administrator and project administrators are granted approval permissions. the administrator and project administrators can approve or reject a ticket. If a ticket is approved, resources are automatically deployed and allocated to the specified project.

Bills: A bill is the expense of resources totaled at a specified time period. Billing is accurate to the second. Bills can be categorized into project bills, department bills, and account bills.

Pricing List: A pricing list is a list of unit prices of different resources. The unit price of a resource is set based on the specification and usage time of the resource.

Console Proxy: Console proxy allows you to log in to a VM instance by using the IP address of a proxy.

AccessKey Management: An AccessKey pair is a security credential that one party authorizes another party to call API operations and access its resources in the Cloud. AccessKey pairs shall be kept confidential.

IP Allowlist/Blocklist: An IP allowlist or blocklist identifies and filters IP addresses that access the Cloud. You can create an IP allowlist or blocklist to improve access control of the Cloud.

Application Center: Application Market allows you to add applications to the Cloud and then access the applications with one click. It extends the functionality of the Cloud. You can add default applications through the built-in installation package or add more applications through URLs.

Sub-Account Management: A sub-account can be created by the admin or synced from an SSO authentication system and is managed by the admin. Resources created under a sub-account are managed by the sub-account.

Theme and Appearance: You can customize the theme and appearance of the Cloud.

Email Server: If you select Email as the endpoint of an alarm, you need to set an email server. Then alarm messages are sent to the email server.

Log Server: A log server is used to collect management node logs or the platform operation logs. You can add a log server to the cloud and use the collected logs for operation trace or troubleshooting. This makes your O&M more efficient.

Global Setting: Global Setting allows you to configure settings that take effect on the whole platform.

Scenario Template: Scenario Template provides multiple templates that encapsulate scenario-based global settings. You can apply a template globally with one click based on your business needs. This improves your O&M efficiency.

HA Policy: HA Policy is a mechanism that ensures sustained and stable running of the business if VM instances are unexpectedly stopped or are errored because of errors occurring to compute, network, or storage resources associated with the VM instances. By enabling this feature, you can customize VM HA policies to ensure your business continuity and stability.

Time Management: Manages the Cloud system time and allows you to configure time servers for the Cloud. After you configure NTP time servers for the Cloud, the clock of the time servers is synced with all nodes of the Cloud.

GPU Device: A GPU device is a powerful microprocessor with high computational capabilities. You can use a GPU device to handle intricate graphics rendering and parallel computing jobs, thus improving the efficiency of businesses such as graphic production, video processing, and machine learning.

Script Library: The script library stores and manages script files centrally. By executing scripts on VM instances, you can complete complex O&M operations and automated jobs.

XML Hook: An XML Hook is a script that can flexibly insert or modify parameters in XML files of VM instances. By attaching an XML Hook to a VM instance, you can customize VM configurations and enable specialized functionalities.

Container Service: A simple and user-friendly container management service, providing features like GPU management & scheduling, multi-tenancy, multi-cluster, quota configuration, CI/CD. and microservice. The service reduces the container using complexity and aligns well with traditional user’s habits, helping you easily manage and deploy your container cluster, and enjoy the benefits of cloud-native technologies in a quick and convenient way.

Advanced Monitoring Server: An advanced monitoring server is a dedicated VM instance used to receive advanced monitoring data of load balancers and other resources.

Advanced Monitoring Server Image: An advanced monitoring server image encapsulates the advanced monitoring service and can be used to create advanced monitoring server.

Advanced Monitoring Server Offering: An advanced monitoring server offering defines the CPU cores, memory size, image, management network, and public network configurations of advanced monitoring server. You can use an advanced monitoring server offering to create advanced monitoring servers.

Plugin Management: You can package extended resources or tools into standardized plugins for quick installation and integration, expanding the Cloud capabilities.

Region Management: A region is a self-contained cloud environment with independent management node(s), networks, hardware, and cloud resources. ZStack IAM enabled user synchronization and SSO across multiple regions.