Load Balancing

A VPC network uses custom ESX Virtual IP addresses (VIPs) or system ESX VIPs to provide load balancing services.
  • The load balancing service can distribute inbound traffics from a public vCenter IP address to a group of backend vCenter VM instances. It automatically detects and isolates unavailable vCenter VM instances during traffic distribution. This helps to improve the availability and service capability of your business.
  • A load balancer supports HTTP and TCP protocols.
  • A load balancer allows you to flexibly configure multiple forwarding policies to achieve advanced forwarding controlling.
This topic falls into the following parts:

Create a Load Balancer

The steps of creating a load balancer in a vCenter environment are basically the same as that in a KVM environment. The basic workflow is as follows, you can refer to User Guide for more details.
  1. Create a load balancer.
    On the main menu of ZStack Cloud, choose Resource Center > Network Service > Basic Network Service > Load Balancing. On the Load Balancing page, click Create Load Balancer. Then, the Create Load Balancer page is displayed. On the displayed page, set the parameters.
    Note:
    • If you choose to create a new VIP to provide load balancing service, select the public network that you created in the vCenter for Network.
    • If you choose to use an existing VIP to provide load balancing service, select an existing custom ESX VIP or system ESX VIP for VIP.
  2. Create a listener.

    On the main menu of ZStack Cloud, choose Resource Center > Network Service > Basic Network Service > Load Balancing. On the Load Balancing page, click a load balancer to enter its details page. On the Listener tab page, click Create Listener. Then, the Create Listener page appears. You can set the parameters on this page.

  3. Attach a backend server group to the listener.

Load Balancer Actions

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

The following table lists the actions that you can perform on a load balancer.
Action Description
Create Load Balancer Create a load balancer.
Edit Load Balancer Edit the name and description of the load balancer.
Delete Load Balancer Deleting a load balancer will automatically delete all associated listeners and the load balancing service. The corresponding VIP and other services associated with the VIP will not be affected.

Listener Actions

On the main menu of ZStack Cloud, choose Resource Center > Network Service > Basic Network Service > Load Balancing. On the Load Balancing page, click a load balancer to enter its details page. Click Listener. Then, the Listener tab page is displayed.

The following table lists the actions that you can perform on a listener.
Action Description
Create Listener Create a new listener.
Edit Edit the name and description of the listener.
Bind Certificate If the protocol of your listener is HTTPS, bind a certificate or a certificate link to your listener. Note that this action is not supported if the listener type is TCP, HTTP, or UDP.
Disassociate Certificate If the protocol of your listener is HTTPS, you can disassociate a certificate from the listener. Note that this action is not supported if the listener type is TCP, HTTP, or UDP.
Attach Backend Server Group Attach a backend server group to the selected listener.
Disassociate Backend Server Group Disassociate a backend server group from a listener.
Configure Forwarding rule Configure the forwarding rule of the selected listener on the Forwarding Rule page.
Note: Only HTTP and HTTPS protocols support forwarding rule configuration.
Delete Listener Deleting a load balancer listener also deletes the corresponding load balancing service.

Notes

  • A load balancer supports multiple listeners.
  • The VM NICs attached to the load balancer listener must share the same L3 network.
  • If the protocol of your listener is HTTPS, you can bind only one certificate to your listener at a time. To change your certificate, unbind the current one first.