DocsKnowledge BaseAPI Explorer
Documentation›Explore more›ZStack Cloud›PrerequisitesZCF
Document navigation

Prerequisites

In this Tutorial, assume that you have installed the latest ZStack Cloud, and complete the basic cloud initialization, including adding a zone, cluster, host, image storage, primary storage, and other basic resources. For more information, see installation and deployment chapter and initialization by Wizard chapter in User Guide.

This Tutorial mainly describes basic deployments and typical scenarios of flat networks.

Basic Deployment

ZStack Cloud supports IPv4 flat networks, IPv6 flat networks, and public networks. This section describes basic deployments of IPv4 flat networks and IPv6 flat networks.

Deploy an IPv4 Flat Network

IPv4, known as Internet Protocol version 4 which defines IP addresses in a 32-bit format, is the most popular Internet Protocol version across the globe. ZStack Cloud flat networks support the IPv4 protocol. This topic mainly describes the basic deployment of IPv4 flat networks.

About this task

The following table lists the assumed environment configurations.
Flat Network Configurations
NIC em01
VLAN ID No VLAN
IP Range 172.20.108.40-172.20.108.50
Netmask 255.255.0.0
Gateway 172.20.0.1
DHCP IP 172.20.180.41
To create an IPv4 flat network, follow these steps:
  1. Create an L2 network corresponded by an IPv4 flat network, and attach the L2 network to the corresponding cluster.
  2. Create an L3 network corresponded by an IPv4 flat network.
  3. Create a VM instance by using this IPv4 flat network.
  4. Validate the connectivity of this IPv4 flat network.

Procedure

  1. Create an L2 network corresponded by an IPv4 flat network, and attach this L2 network to the corresponding cluster.
    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 Create L2 Network page, set the following parameters by referring to IPv4 Flat Network Configuration:
    • Zone: By default, the current zone is displayed.
    • Name: Enter a name for the L2 flat network.
    • Description: Optional. Enter a description for the L2 flat network.
    • Switch Type: Select Linux Bridge.
    • Network Type: Select L2NoVlanNetwork.
    • Cluster: Optional. Select the cluster to be attached, for example, Cluster-1.
    • NIC Name: Select or enter an NIC name for the L2 network. For example, em01.
    Figure 1. Create L2 Flat Network


  2. Create an L3 network corresponded by an IPv4 flat network.
    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L3 Network Resources > Flat Network. On the Flat Network page, click Create Flat Network. The Create Flat Network page appears. On the displayed Create Private Network page, set the following parameters by referring to IPv4 Flat Network Configuration:
    • Name: Enter a name for the L3 flat network.
    • Description: Optional. Enter a description for the L3 flat network.
    • L2 Network: Select an L2 flat network that you created.
    • IP Address Management: Select whether to enable IP Address Management (IPAM) for the L3 flat network. If you enable IPAM, you can set network ranges, IP allocation policy, and DHCP service for the L3 network. Enable IPAM here.
    • Network Address Type: Select IPv4.
    • Network Range Method: Select a method to add a network range for the flat network. Here, select IP Range.
    • Start IP: Set a start IP address for the network range, for example, 172.20.108.40.
    • End IP: Set an end IP address for the network range, for example, 172.20.108.50.
    • Netmask: Set a netmask for the network range, for example, 255.255.0.0.
    • Gateway: Set a gateway for the network range, for example, 172.20.0.1.
    • DHCP Service: Choose whether to enable the DHCP service.
      Note:
      • 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, 172.20.180.41.
        Note:
        • 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. Enter a DNS, such as 114.114.114.114.
    Figure 2. Create L3 Flat Network


  3. Create a VM instance by using this IPv4 flat 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 displayed. On the displayed page, create two VM instances by using the IPv4 flat network, for example, VM-1 and VM-2.

  4. Validate the connectivity of this IPv4 flat network.

    Expected result: The two VM instances (VM-1 and VM-2) on the same network range can communicate with each other.

    Validate the connectivity:
    • Log in to VM-1 and validate whether VM-1 can ping VM-2.
      Figure 3. VM-1 Pings VM-2


    • Log in to VM-2 and validate whether VM-2 can ping VM-1.
      Figure 4. VM-2 Pings VM-1


    So far, we have introduced the basic deployments of the IPv4 flat network.

Deploy an IPv6 Flat Network

IPv6 is Internet Protocol version 6 that defines IP addresses in a 128-bit format. IPv6 resolves the long-anticipated problem of IPv4 address exhaustion, so many devices can be connected to the Internet. ZStack Cloud flat networks support the IPv6 protocol. This topic describes the basic deployment of IPv6 flat networks.

About this task

The following table lists the assumed environment configurations.
Flat Network Configurations
NIC em1
VLAN ID 2002
IP Range 234e:0:4567::2-234e:0:4567:0:ffff:ffff:ffff:ffff
Prefix length 64
Gateway 234e:0:4567::1
DHCP IP 234e:0:4567::3
DNS 240c::6644
To create an IPv6 flat network, follow these steps:
  1. Create an L2 network corresponded by an IPv6 flat network, and attach this L2 network to the corresponding cluster.
  2. Create an L3 network corresponded by the IPv6 flat network.
  3. Create two VM instances by using the IPv6 flat network.
  4. Obtain IPv6 addresses of the VM instances.
  5. Validate the connectivity of the IPv6 flat network.

Procedure

  1. Create an L2 network corresponded by an IPv6 flat network, and attach this L2 network to the corresponding cluster.
    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 Create L2 Network page, set the following parameters by referring to IPv6 Flat Network Configuration:
    • Zone: By default, the current zone is displayed.
    • Name: Enter a name for the L2 flat network, for example, L2-IPv6-Flat Network.
    • Description: Optional. Enter a description for the L2 flat network.
    • Switch Type: Select Linux Bridge.
    • Network Type: Select L2VlanNetwork.
    • Cluster: Optional. Select the cluster to be attached, for example, Cluster-1.
    • VLAN ID: Enter a VLAN ID, for example, 2002.
    • NIC Name: Select or enter an NIC name for the L2 network. For example, em1.
    • PVLAN (Isolated): Disable the switch.
    Figure 5. Create L2-IPv6-Flat Network


  2. Create an L3 network corresponded by the IPv6 flat network.
    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L3 Network Resources > Flat Network. On the Flat Network page, click Create Flat Network. The Create Flat Network page appears. On the displayed Create Private Network page, set the following parameters by referring to IPv6 Flat Network Configuration.
    • Name: Enter a name for the L3 network, such as L3-IPv6-Flat Network.
    • Description: Optional. Enter a description for the L3 flat network.
    • L2 Network: Select an L2 flat network that you created, such as L2-IPv6-Flat Network.
    • IP Address Management: Select whether to enable IP Address Management (IPAM) for the L3 flat network. If you enable IPAM, you can set network ranges, IP allocation policy, and DHCP service for the L3 network. Enable IPAM here.
    • Network Address Type: Select IPv6.
    • Network Range Method: Select a method to add a network range for the flat network. Here, select IP Range.
    • IP Configuration Mode: Select Stateful-DHCP.
    • Start IP: Set a start IP address for the network range, for example, 234e:0:4567::2.
    • End IP: Set an end IP address for the network range, for example, 234e:0:4567:0:ffff:ffff:ffff:ffff.
    • Prefix Length: Set a prefix length for the network range, for example, 64.
    • Gateway: Set a gateway for the network range, for example, 234e:0:4567::1.
    • DHCP Service: Choose whether to enable the DHCP service.
      Note:
      • 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 flat 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:4567::3.
        Note:
        • 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.
    • DNS: Set a DNS address for the L3 network, for example, 240c::6644.
    Figure 6. Create L3-IPv6-Flat Network


  3. Create two VM instances by using the IPv6 flat 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 displayed. On the displayed page, create two VM instances by using the IPv6 flat network, for example, VM-1 and VM-2.

  4. Obtain IPv6 addresses of the VM instances.
    By default, ZStack Cloud can automatically obtain IP addresses for the IPv4 network, while you must manually configure IP addresses for VM instances that use the IPv6 network. Launch the consoles of these two VM instances respectively, and run the following commands to obtain IPv6 addresses:
    [root@loaclhost~]# dhclient -6 eth0  //eth0 indicates the NIC name.
    Note: The address that begins with FE80 is the link-local address instead of the expected address.
    Figure 7. Obtain IPv6 Address


    In this scenario, you will obtain the following IPv6 addresses:
    • VM-1 IP address: 234e:0:4567::63:ab4d
    • VM-2 IP address: 234e:0:4567::31:3c6e
  5. Validate the connectivity of the IPv6 flat network.

    Expected result: The two VM instances (VM-1 and VM-2) on the same network range can communicate with each other.

    Validate the connectivity:
    • Log in to VM-1 and validate whether VM-1 can ping VM-2.
      Figure 8. VM-1 Pings VM-2


    • Log in to VM-2 and validate whether VM-2 can ping VM-1.
      Figure 9. VM-2 Pings VM-1


    So far, we have introduced the basic deployments of the IPv6 flat network.

Deploy a Flat Network Disabled with IP Address Management

About this task

IP Address Management (IPAM) is a service for the allocation and management of IP addresses on an L3 network. Enabling IPAM for an L3 network requires you to add network ranges from which IP addresses are allocated to the resources on this L3 network automatically. ZStack Cloud allows you to disable IPAM when creating a flat network which does not need network ranges and other relevant parameters. You can allocate and manage IP addresses of resources on this flat network by yourself without the restriction of network ranges. This topic describes the deployment of a flat network disabled with IPAM.

The following table lists the assumed environment configurations.
Flat Network Configurations
NIC eth0
VLAN ID 2002
Flat Network Configurations
IP address 172.20.60.107
Netmask 255.255.0.0
Gateway 172.20.0.1
To create a flat network disabled with IPAM, follow these steps:
  1. Prepare an L2 network for the flat network, and attach this L2 network to the corresponding cluster.
  2. Create a flat network and disable IP Address Management.
  3. Create a VM instance based on the no-IPAM flat network.
  4. Install GuestTools for the VM instance.
  5. Sync VM NIC configurations.
  6. Validate the IP configuration of the VM NIC.

Procedure

  1. Prepare an L2 network for the flat network, and attach this L2 network to the corresponding cluster.
    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 Create L2 Network page, set the following parameters by referring to Flat Network Configuration:
    • Zone: By default, the current zone is displayed.
    • Name: Enter a name for the L2 flat network, for example, L2-No-IPAM-Flat.
    • Description: Optional. Enter a description for the L2 flat network.
    • Switch Type: Select Linux Bridge.
    • Network Type: Select L2VlanNetwork.
    • Cluster: Optional. Select the cluster to be attached, for example, Cluster-1.
    • VLAN ID: Enter a VLAN ID, for example, 2002.
    • NIC Name: Select or enter an NIC name for the L2 network. For example, eth0.
    • PVLAN (Isolated): Disable the switch.
    Figure 10. Create L2-No-IPAM-Flat Network


  2. Create a Flat Network and disable IP Address Management.
    On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L3 Network Resources > Flat Network. On the Flat Network page, click Create Flat Network. The Create Flat Network page appears. On the displayed Create Private Network page, set the following parameters:
    • Name: Enter a name for the L3 network, such as L3-No-IPAM-Flat.
    • Description: Optional. Enter a description for the L3 flat network.
    • L2 Network: Select an L2 flat network that you created, such as L2-No-IPAM-Flat.
    • IP Address Management: Select whether to enable IP address management (IPAM) service for the 3 network. Disable IPAM in this scenario. After the disabling, you do not need to set network ranges, gateway netmask, and IP allocation policy for the L3 network.
    • DHCP Service: After disabling IPAM, the DHCP service is disabled by default and cannot be enabled.
    • DNS: Set a DNS address for the L3 network. You can leave this parameter as blank in this scenario.
    Figure 11. Create L3-No-IPAM-Flat Network


  3. Create a VM instance based on the no-IPAM flate 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 displayed. On the displayed page, create a VM instances by using the no-IPAM flat network you created. You can set the network configuration according to Table 2.
    • Network: Select the flat network disabled with IPAM you create.
    • Make Default: Select whether to set the flat network as the default network of the VM instance. In this scenario, set the flat network as the default network.
    • Enable SR-IOV: Do not enable SR-IOV in this scenario.
    • Assign IPv4: The system does not allocate an IP address to a VM NIC created on an L3 network disabled with IPAM. To configure the NIC IP address, you can either manually assign one on the Cloud or configure one in the VM instance. Assign one on the Cloud in this scenario.
      Note: If you configure an IP address in the VM instance, the IP address cannot be read or managed by the Cloud currently.
      • IPv4 : Manually assign an IP address for the VM instance. Enter 172.20.60.107 in this scenario.
        Note:
        • Make sure that the IP address has not been occupied on the Cloud.
        • Install GuestTools for the VM instance after the creation and sync NIC configurations to make the IP address take effect.
      • Netmask: Set the IPv4 netmask. Enter 255.255.0.0 in this scenario.
      • IPv4 Gateway: Set the IPv4 gateway. Enter 172.20.0.1 in this scenario.
      • Security Group: Associate an existing security group to the VM instance for network security services. You can leave this paramater as blank in this scenario.
    • Assign IPv6: Select whether to manually assign an IPv6 address for the VM instance. Do not assign an IPv6 address in this scenario.
    • MAC Address: Select whether to manually assign a MAC address for the VM instance. DO not assign a MAC address in this scenario.
    Figure 12. VM Instance Network Configuration


  4. Install GuestTools for the VM Instance.
    Follow these steps to install GuestTools for the VM instance:
    1. Install ISO.
      On the details page of the VM-Self-Managed-IP, click GuestTools: Install > Next: Install on VM Console.
      Figure 13. Install GuestTools: Install ISO


    2. Install on VM Console
      Run the following commands on the VM console to finish the installation:
      # Create a mount point.
mkdir /mnt/cdrom
# Attach the CD-ROM image.
mount /dev/cdrom /mnt/cdrom
# Install GuestTools.
cd /mnt/cdrom/
bash ./zs-tools-install.sh
# Unmount the CD-ROM image (optional).
cd ~
umount /mnt/cdrom
      Figure 14. Install GuestTools: Install on VM Console




    Note: If you configure an IP address in the VM instance, you can skip this step.
  5. Sync VM NIC configurations.
    On the details page of VM-Self-Managed-IP, click Configuration > NIC > Synchronize Configurations to deploy the IP address assigned on the Cloud to the NIC actually.
    Note: If you configure an IP address in the VM instance, you can skip this step.
  6. Validate the IP address of the VM NIC.

    Expected result: The IP address assigned on the Cloud can be queried in the VM instance.

    Log in to the VM-Self-Managed-IP and check the VM IP address.

    Figure 15. Validate the IP Address of the VM NIC


    Note: If you configure the IP address in the VM instance, you can skip this validation.

What to do next

So far, you have deployed a flat network disabled with IP Address Management.

Typical Scenarios

IPv4+IPv6 Dual Stack

An IPv4+IPv6 dual stack is one NIC with two types of IP addresses: IPv4 and IPv6, and takes full advantage of both IPv4 and IPv6. With the IPv4+IPv6 dual stack, you can meet the needs of different business scenarios.

About this task

The following tables list the assumed environment configurations.
  1. IPv4 Network Range
    Flat Network Configurations
    NIC em1
    VLAN ID 2002
    IP Range 192.168.2.2-192.168.2.254
    Netmask 255.255.255.0
    Gateway 192.168.2.1
    DHCP IP 192.168.2.3
    DNS 223.5.5.5
  2. IPv6 Network Range
    Flat Network Configurations
    IP Range 234e:0:4568::2-234e:0:4568:0:ffff:ffff:ffff:ffff
    Prefix Length 64
    Gateway 234e:0:4568::1
    DHCP IP 234e:0:4567::3
    DNS 240c::6644
To create an IPv4+IPv6 dual stack, follow these steps:
  1. Create an IPv4 networking environment.
  2. Add an IPv6 range.
  3. Add an IPv6 DNS address.
  4. Create VM instances by using the dual-stack network.
  5. Obtain IPv6 addresses of the VM instances.
  6. Validate the network connectivity.

Procedure

  1. Create an IPv4 networking environment.
    Create a flat network with an IPv4 address, for example, L3-Flat Network. At this time, this network is an IPv4 network. For network configuration information, see IPv4 Network Configuration and IPv6 Network Configuration.
    Note: You can also create an IPv6 flat network first, and then add an IPv4 range to a flat network.
  2. Add an IPv6 range.

    Add an IPv6 range to the existing IPv4 network to form an IPv4+IPv6 dual-stack network.

    On the Flat 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. Here, select IP Range.
    • IP Configuration Mode: Select Stateful-DHCP.
      Note:
      • 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. Range: 64-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.
      Note:
      • 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.
    Figure 16. Add IPv6 Range


  3. Add an IPv6 DNS address.
    On the DNS tab page of the flat network, click Add DNS. On the Add DNS dialogue box, set the following parameters:
    • Network Address Type: Select IPv6.
    • DNS: Specify a DNS address, for example, 240c::6644.
    Figure 17. Add IPv6 DNS Address


  4. Create VM instances by using the dual-stack 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 displayed. On the displayed page, create two VM instances by using the IPv4 flat network, for example, VM-Dual Stack-1 and VM-Dual Stack-2.

  5. Obtain IPv6 addresses of the VM instances.
    By default, ZStack Cloud can automatically obtain IP addresses for the IPv4 network, while you must manually configure IP addresses for VM instances that use the IPv6 network. Launch the consoles of these two VM instances respectively, and run the following commands to obtain IPv6 addresses:
    [root@loaclhost~]# dhclient -6 eth0  //eth0 indicates the NIC name.
    Note: The address that begins with FE80 is the link-local address instead of the expected address.
    Figure 18. Obtain IP Address


    In this scenario, after running ifconfig, you will obtain the following addresses:
    • VM-Dual Stack-1 IPv4 address: 192.168.2.248
    • VM-Dual Stack-1 IPv6 address: 234e:0:4568::69:9fdc
    • VM-Dual Stack-2 IPv4 address: 192.168.2.183
    • VM-Dual Stack-2 IPv6 address: 234e:0:4568::23:c59b
  6. Validate the network connectivity.
    Expected result:
    • Log in to the VM-Dual Stack-1. Use the IPv4 address and the IPv6 address respectively to validate whether these two IP addresses can ping VM-Dual Stack-2.
    • Log in to the VM-Dual Stack-2. Use the IPv4 address and the IPv6 address respectively to validate whether these two IP addresses can ping VM-Dual Stack-1.
    Figure 19. Validate Network Connectivity


    Similarly, log in to the VM-Dual Stack-2. Use the IPv4 address and the IPv6 address to validate whether these two IP addresses ping VM-Dual Stack-1.

    So far, we have introduced how to use a Dual stack (IPv4+IPv6) flat network.

Load Balancing

Prerequisites

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.

About this task

To create a private flat network load 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 listener.
  5. Add a backend server and assign a weighted value.
  6. Validate the scenario.

Procedure

  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.
    Figure 20. 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.
    Figure 21. 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.
    • Network: Select a network as the frontend network of the LB. Here, select a flat 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 flat network.
    • 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.
    Figure 22. Create Dedicated-Performance Load Balancer


  4. 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 TCP.
    • 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 Weighted 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.
    Figure 23. Create Listener


  5. Add a backend server and assign a weighted value.
    1. 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: By default, the flat network is displayed.
      • NIC: Specify 3 VM instances NICs.
      Figure 24. Add Backend Server


    2. Assign a weighted value.

      On the Add Backend Server page, assign a weighted value to the 3 VM instances respectively. Requests are more likely to be distributed to VM instances with a higher weight.

      Figure 25. Assign Weighted Value


  6. Validate the scenario.

    In this scenario, we will run the curl command in the port 100 of the VIP address (192.168.0.249) of the load balancer: for i in {1..20}; do curl 192.168.0.249:100; done.

    Expected result:
    • VM-1 (Weighted value: 80): The number (probability) of distributed requests is relatively high.
    • VM-2 (Weighted value: 40): The number (probability) of distributed requests is relatively medium.
    • VM-3 (Weighted value: 20): The number (probability) of distributed requests is relatively low.
    Actual result:
    • VM-1: being polled for 11 times.
    • VM-2: being polled for 6 times.
    • VM-3: being polled for 3 times.
    Figure 26. Scenario Validation


    So far, we have introduced how to use the load balancing service based on a flat network.

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.
PreviousZStack CloudNextZStack Cloud
Flat Network Tutorial | 5.5.38 | ZStack Cloud · ZCF | ZStack Resource Center