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

Overview

What Is SR-IOV

SR-IOV (Single Root I/O Virtualization) is a hardware-based virtualization solution. This technology allows a single PCIe device, such as a physical NIC, to create multiple independent Virtual Functions (VFs). These VFs can be directly assigned to multiple instances, including VM instances, VPC vRouters, and load balancers. SR-IOV delivers near-native physical device I/O performance and low latency, significantly improving data processing performance and scalability in virtualized environments.

ZStack Cloud supports the SR-IOV specification. Administrators can virtualize a single physical NIC into multiple VF NICs. After the virtualization, you can directly assign VF NICs to instances.

Compared to traditional vNICs, VF NICs offer the following advantages:
  • Bypass the virtualization layer and shorten the data transmission path, providing VM instances, VPC vRouters, and load balancers with I/O performance close to that of physical devices.
  • Significantly reduce consumption of host CPUs. Even under high CPU load, this effectively reduces network packet loss and improve transmission efficiency.

Applications

Network Functions Virtualization (NFV)

As technologies like cloud computing and virtualization mature, the telecommunications industry is also transforming the architecture of traditional networking through virtualization. NFV devices are accelerating the shift to software-based solutions, enabling large-scale virtualized deployment of applications within network equipment. This approach helps reduce costs, increase flexibility, and effectively enhance competitiveness.

However, these applications have extremely high demands on network capabilities such as throughput, forwarding, and packet processing, requiring high-performance virtual networks to function effectively. Consequently, NICs with SR-IOV capabilities, valued for their maturity and virtualizability, are widely adopted in NFV devices. This allows data centers to obtain high-performance, easily scalable, and elastic network management capabilities at a relatively low cost.

Cloud Gaming

With the development of broadband networks and the widespread adoption of mobile devices, the cloud gaming model—where game computation is offloaded to the cloud, and the client is only responsible for display and control—has quietly gained popularity. For games with high real-time performance requirements, network capabilities such as packet forwarding, instantaneous throughput, and latency stability are essential. Without these, issues like frame drops and input lag may occur, severely impacting the gaming experience.

In this cloud gaming model, you can leverage the stable network performance of physical NICs by using SR-IOV to directly assign VFs to VM instances. The traffic from the VM instance's virtual NIC is sent directly to the VF, bypassing intermediate software switches like bridge NICs or Open vSwitch. This significantly reduces packet processing overhead and provides users with a better gaming experience.

Video Streaming

With the evolution of the Internet, the transmission of multimedia information online has become increasingly critical. To ensure transmission speed, video streaming based on the UDP protocol is widely used. For scenarios requiring real-time video transmission (such as live streaming and video conferencing), network performance in terms of packet forwarding, instantaneous throughput, and latency stability is indispensable. Otherwise, issues like video stuttering and reduced resolution may occur, severely degrading the viewing experience.

It is well-known that while the UDP protocol can increase transmission speed and significantly reduce transmission time, it cannot guarantee data reliability. Network fluctuations and packet loss directly impact video quality—haste makes waste. NICs with SR-IOV capabilities, leveraging their maturity and virtualizability, offer unique advantages in real-time video scenarios. They not only guarantee network performance but also reduce CPU load, effectively minimize packet loss, and improve transmission efficiency. This perfectly compensates for the reliability shortcomings of the UDP protocol, making them an excellent fit for such applications.

Before You Begin

Known Limitations

The SR-IOV feature has the following constraints with NIC bonding:
  • If a physical NIC is in the bond and the bond contains more than two NICs, you cannot virtualize the physical NIC.
  • If a physical NIC is in the bond, when you virtualize this physical NIC, all physical NICs in that bond will be virtualized.
  • If a bond contains a virtualized physical NIC, you cannot add or remove physical NICs from that bond.
  • If a physical NIC has been virtualized, it cannot be added to a bond that contains non-virtualized NICs.
The SR-IOV feature has the following constraints with hot migration:
  • Before you hot migrate a VM instance with VF NICs attached, you must install GuestTools (QGA) in the VM instance and make sure the GuestTools is running normally.
  • VPC vRouters and load balancers come with the GuestTools pre-installed, you can hot migrate them without requiring additional installation.
  • Hot migration with VF NICs may fail if the internal driver version of the VM instance, VPC vRouter, or load balancers is too low. Check and update the driver version as needed.
  • Depending on the actual network environment, short network interruptions may occur during the hot migration of VM instance with VF NICs. Use with caution in business-critical scenarios.
Other limitations or constraints:
  • Security group network services are not available for VF NICs.
  • For a VPC vRouter with SR-IOV enabled, if any of its attached networks have VIP QoS or Network Bandwidth services configured, the VPC vRouter performance may be affected.
  • For users upgrading from a version prior to ZStack Cloud 5.5.0, if a VPC vRouter was already SR-IOV enabled before the upgrade and did not have VIP QoS or Network Bandwidth configured, it is recommended to manually reboot that VPC vRouter after the upgrade to ensure optimal performance.
  • For VM instances, VPC vRouters, or load balancers already using VF NICs:
    • Do not uninstall the PF driver of the physical NIC, as this will cause the system to forcibly reclaim the VF NICs.
    • Stopping an instance will automatically release its VF NICs. Starting the instance will re-acquire VF NICs. If no VF NICs are available, the instance will fail to start.

Prerequisites

To use SR-IOV in ZStack Cloud, your environment must meet the following configuration requirements:
  1. Ensure the physical NIC supports SR-IOV and that SR-IOV is enabled.
  2. Ensure the Intel VT-d or AMD IOMMU and SR-IOV are enabled in the host's BIOS.

    BIOS configuration varies across different servers. For specific procedures, consult your hardware vendor's documentation.

  3. Ensure the host's CPU supports Interrupt Remapping.
    1. Create a script named interrupt_remapping_check.sh with the following content.
      #!/bin/sh
if [ $(dmesg | grep ecap | wc -l) -eq 0 ]; then
  echo "No interrupt remapping support found"
  exit 1
fi

for i in $(dmesg | grep ecap | awk '{print $NF}'); do
  if [ $(( (0x$i & 0xf) >> 3 )) -ne 1 ]; then
    echo "Interrupt remapping not supported"
    exit 1
  fi
done
    2. Grant the script executable permissions.
    3. Execute the interrupt_remapping_check.sh script on the host to check if the CPU supports Interrupt Remapping.
      • If the output is No interrupt remapping support found or Interrupt remapping not supported, the CPU does not support Interrupt Remapping.
      • If there is no output, the CPU supports Interrupt Remapping.
    4. If the CPU does not support Interrupt Remapping, you can configure it by executing the following command.
      [root@localhost ~]# echo "options vfio_iommu_type1 allow_unsafe_interrupts=1" > /etc/modprobe.d/iommu_unsafe_interrupts.conf
  4. Ensure the relevant drivers are installed.
    • The host requires the PF NIC driver to be installed, ensuring the physical NIC is recognized by the host and can be virtualized using SR-IOV.
    • VM instances, VPC vRouters, or load balancers require the VF NIC driver to be installed, ensuring the VF NIC is recognized and functions correctly.
    Note: The operating system release contains a default driver for certain NICs, while for others you must download and install it from a location provided by the vendor of the NIC or the host.

Using SR-IOV

Configure VF NICs for a VM instance

Prerequisites

To use SR-IOV, ensure your environment meets the software and hardware compatibility requirements described in Prerequisites.

Procedure

  1. Log in to ZStack Cloud.
  2. Enable IOMMU on the host.
    For a new host to be added:
    1. On the main menu of ZStack Cloud, choose Resource Center > Hardware > Host.
    2. On the Host page, click Add Host.
    3. On the Add Host page, complete the host configuration and enable the Scan Host IOMMU Setting option.
    Figure 1. Enable Scan Host IOMMU When Adding Hosts


    For an existing host:
    1. On the main menu of ZStack Cloud, choose Resource Center > Hardware > Host.
    2. On the Host page, click the name of the target host to enter its details page.
    3. On the Overview tab of the target host's details page, enable IOMMU State.
    4. After enabling it, restart the host for the configuration to take effect.
    Figure 2. Enable IOMMU State for Existing Hosts


  3. Virtualize the physical NIC using SR-IOV.
    1. On the details page of the target host, click Associated Resource > Physical NIC.
      Administrators can check the Virtualization Status in the Physical NIC list to determine if a physical NIC supports SR-IOV.
    2. In the Physical NIC list, select the target physical NIC, then click Actions > SR-IOV.
    3. In the SR-IOV dialog, enter the number of VFs to create.
    4. Click OK.
    Figure 3. SR-IOV Physical NICs


  4. Create an SR-IOV enabled network.
    1. On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L2 Network.
    2. On the L2 Network page, click Create L2 Network.
    3. On the Create L2 Network page, complete the relevant configuration. For Cluster, select the cluster that contains the hosts with IOMMU enabled. For NIC Name, select the name of the physical NIC that has been virtualized.
    4. Click OK.
    5. On the Network Resource menu, click Flat Network.
    6. On the Flat Network page, click Create Flat Network.
    7. On the Create Flat Network page, complete the relevant network configurations. For L2 Network, select the L2 network you just created.
    8. Click OK.
  5. Create a VM instance with VF NIC attached.
    1. On the main menu of ZStack Cloud, choose Resource Center > Resource Pool > VM Instance.
    2. On the VM Instance page, click Create VM Instance.
    3. On the Create VM Instance page, complete the basic configuration. In the resource configuration, for Network, select the flat network created in step 4, and select the Enabled SR-IOV option.
    4. Continue to complete the system configuration for the VM instance, then click OK.
  6. Install the VF NIC driver for the VM instance.
    VM instances require the VF NIC driver to be installed to ensure the VF NIC is recognized and functions correctly. For more information on obtaining and installing VF NIC drivers, contact your NIC vendor for assistance.

Configure SR-IOV for a VPC vRouter with Bonded NICs

Prerequisites

  • To use SR-IOV, ensure your environment meets the software and hardware compatibility requirements described in Prerequisites.
  • Ensure that the bond containing the physical NIC you intend to virtualize has no more than two NICs. Otherwise, SR-IOV will fail. For more information about usage limitations, see Known Limitations.
  • Obtain the openEuler 22.03 image for the VPC vRouter in advance.
  • Plan the public network and the management network for the VPC vRouter in advance. These two networks must be deployed separately.
  • (Optional) Based on your actual resource and business requirements, you can plan to create a new cluster using two independent servers dedicated to hosting VPC vRouters and providing high performance networking. These two servers can be configured into a VPC vRouter HA group for redundancy. For more information, see (Optional) Create a VPC vRouter HA group.

Procedure

  1. Log in to ZStack Cloud.
  2. Enable IOMMU on the host.
    For a new host to be added:
    1. On the main menu of ZStack Cloud, choose Resource Center > Hardware > Host.
    2. On the Host page, click Add Host.
    3. On the Add Host page, complete the host configuration and enable the Scan Host IOMMU Setting option.
    Figure 4. Enable Scan Host IOMMU When Adding Hosts


    For an existing host:
    1. On the main menu of ZStack Cloud, choose Resource Center > Hardware > Host.
    2. On the Host page, click the name of the target host to enter its details page.
    3. On the Overview tab of the target host's details page, enable IOMMU State.
    4. After enabling it, restart the host for the configuration to take effect.
    Figure 5. Enable IOMMU State for Existing Hosts


  3. Add a bond.
    1. On the details page of the target host, click Associated Resource > Physical NIC.
    2. On the Physical NIC page, select Bond, then click Add Bond.
      Figure 6. Add Bond


    3. In the Add Bond drawer, select two physical NICs, choose the bond mode, and specify the IPv4 and netmask.
      • It is recommended to select physical NICs with the same type, vendor, and model.
      • After selecting the bond mode, configure the switch side to the corresponding mode accordingly.
      Figure 7. Configure Bond Settings


    4. Click OK.
  4. Virtualize a bonded NIC using SR-IOV.
    1. On the Physical NIC page, select the Physical NIC tab.
    2. In the Physical NIC list, select the target physical NIC, then click Actions > SR-IOV.
    3. In the SR-IOV dialog, enter the number of VFs to create.
      Because the selected physical NIC is in a bond, virtualizing this physical NIC will simultaneously virtualize all NICs in the bond.
    4. Click OK.
    Figure 8. SR-IOV Bonded NIC


  5. Create an L2 network.
    1. On the main menu of ZStack Cloud, choose Resource Center > Network Resource > L2 Network.
    2. On the L2 Network page, click Create L2 Network.
    3. On the Create L2 Network page, complete the relevant configuration as needed. For Cluster, select the cluster that contains the hosts with IOMMU enabled. For NIC Name, select the name of the physical NIC that has been virtualized.
    4. Click OK.
    Figure 9. Create L2 Network


  6. Create a public network.
    1. On the Network Resource menu, click Public Network.
    2. On the Public Network page, click Create Public Network.
    3. On the Create Public Network page, complete the public network configuration.
    4. Click OK.
    Figure 10. Create Public Network


  7. Create a management network.
    1. On the Network Resource menu, click Management Network.
    2. On the Management Network page, click Create Management Network.
    3. On the Create Management Network page, complete the management network configurations.
    4. Click OK.
    Figure 11. Create Management Network


  8. Add a vRouter image.
    1. On the Network Resource menu, click vRouter Image.
    2. On the vRouter Image page, click Add vRouter Image.
    3. On the Add vRouter Image page, upload the obtained openEuler image via URL or as a local file.
    4. Click OK.
    Figure 12. Add vRouter Image


  9. Create a vRouter offering.
    1. On the Network Resource menu, click vRouter Offering.
    2. On the vRouter Offering page, click Create vRouter Offering.
    3. On the Create vRouter Offering page, complete the specification settings.
      • Set the vRouter offering name, CPU, and memory.
      • For image, select the VPC vRouter image added in Step 8.
      • For management network and public network, select two separate networks: select the public network created in Step 6 and the management network created in Step 7.
    4. Click OK.
    Figure 13. Create vRouter Offering


  10. Create a VPC vRouter and enable SR-IOV.
    1. On the Network Resource menu, click VPC vRouter.
    2. On the VPC vRouter page, click Create VPC vRouter.
    3. On the Create VPC vRouter page, select Enable SR-IOV, then complete the other vRouter configurations.
    Figure 14. Create VPC vRouter


  11. Create a VPC network.
    1. On the Network Resource menu, click VPC Network.
    2. On the VPC Network page, click Create VPC Network.
    3. On the Create VPC Network page, complete the VPC network configurations.
    4. Click OK.
    Figure 15. Create VPC Network


  12. Attach a VPC vRouter to the VPC network and enable SR-IOV.
    1. On the Network Resource menu, click VPC Network.
    2. On the VPC Network page, locate the VPC network you created in Step 11.
    3. Click Actions > Attach VPC vRouter.
    4. In the Select VPC vRouter drawer, select the VPC vRouter created in Step 10.
    5. Select Enable SR-IOV.
    6. Click OK.
    Figure 16. Attach VPC vRouter and Enable SR-IOV


  13. (Optional) Create a VPC vRouter HA group.
    1. On the main menu of ZStack Cloud, choose Resource Center > Network Resource > VPC vRouter HA Group.
    2. On the VPC vRouter HA Group page, click Create VPC vRouter HA Group.
    3. On the Create VPC vRouter HA Group page, select importing an existing VPC vRouter or creating a new VPC vRouter.
    4. Click OK.
    Figure 17. Create VPC vRouter HA Group


FAQ

Host IOMMU is Enabled, But IOMMU Status is Unavailable

After enabling host IOMMU on a host, you must also ensure its IOMMU state is available. Otherwise, you cannot use the SR-IOV feature normally.

Possible Cause 1

IOMMU was enabled but the host was not rebooted.

Solution

Procedure

  1. Locate the target host and click Actions > Power Control > Reboot.
  2. After acknowledging the risks, click OK.

Possible Cause 2

Incorrect host configuration.

Solution

Procedure

  1. Locate the target host and enter its BIOS.
  2. Enable the Intel VT-d or AMD IOMMU setting to make the IOMMU configuration effective in the kernel.
    BIOS configuration varies across different servers. For specific procedures, consult your hardware vendor's documentation.

Cannot Select Enable SR-IOV When Adding L3 Network to a VM Instance

When creating a VM instance and selecting a L3 network in the network configuration, the Enable SR-IOV checkbox for that L3 network is grayed and unavailable for selection.

Possible Cause

The physical NIC associated with this L3 network has no available VF NICs.

Solution

  • Check if the physical NIC associated with this L3 network has been virtualized.
  • Change to a different L3 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
SR-IOV NIC Virtualization Tutorial | 5.5.38 | ZStack Cloud · ZCF | ZStack Resource Center