1. Articles
  2. Public Cloud Services
  3. Networking
  4. Getting Started

Articles in this section

Getting Started with Load Balancer on Public Cloud

Avatar
Stephanie R.
  • Updated

Learn how to configure an OVHcloud Load Balancer with the help of this guide.

Our Public Cloud Load Balancer is based on OpenStack Octavia and is fully integrated into the Public Cloud universe.

NOTE: Load Balancer creation will fail if you have multiple listeners.

 

Requirements

 

Instructions

Creating the Load Balancer

Click a tab to choose a method, OVHcloud Control Panel or OpenStack CLI.

Open your Public Cloud project and click Load Balancer (under Network) in the left menu, then click the Create your Load Balancer button.

If you have not already created a private network, click Discover the Public Cloud Load Balancer, create a private network, and return to the Load Balancer section.

PCI_networking_octaviaLB01**.png

 

Step 1: Select the size

The interface contains a link to the website on which the characteristics/benchmarks of all sizes are provided. Once you have chosen your size, click Next.

PCI_networking_octaviaLB02.png

 

Step 2: Select a region

Only regions on which you have a private network and at least one subnet can be selected. Select the region and click Next.

PCI_networking_octaviaLB03.png

 

Step 3: Attach a public IP (or not)

At this stage, you need to know if your Load Balancer will be receiving public traffic or not (for more details, read our Public Cloud Networking concepts page).

If your Load Balancer is processing public traffic, you have two options:

  • New Public IP: this option will create a new Floating IP for your Load Balancer.
  • If you already have a Floating IP, the interface will offer you to pick one.

If your Load Balancer is processing private traffic, choose No Public IP.

When you have made your selection, click Next.

PCI_networking_octaviaLB04.png

 

Step 4: Select a private network

The interface will inform you if the private network/subnet is not compliant with the prerequisites (see Public Cloud Networking concepts).

PCI_networking_octaviaLB05.png

 

Step 5 (optional): Define the listener(s) and the members

First, choose the listener protocol & the port according to the traffic you will receive. Note that a specific listener called Prometheus is available to monitor your Load Balancer. In that case, it is not possible to add members. For more information on this listener, read this page.

Then, choose the Health Monitor type. Note that since some health monitor types are not compatible with some protocols, the user interface filters those types so that you can only choose compatible items. For more information on the health monitor compatibility, read this page.

Finally, from the instances of your region, choose the member IP & port that will be part of the pool. Note that to simplify the configuration workflow, it is only possible to have a pool with the same protocol as the listener, and that the member can only be chosen from the instance. Those limitations can be bypassed by skipping this part of the configuration and using the pool/member configuration once the Load Balancer is created.

PCI_networking_octaviaLB06.png

 

Step 6: Finalize

You can update the name according to your choice and click on Create a Load Balancer.

PCI_networking_octaviaLB07.png

 

You will be redirected to the Load Balancer listing page. Among the attributes that are displayed, the Operating status and Provisioning status provide information on the state of your load balancer. Find more information on the Load Balancer concepts page.

Configuring your private network

Before creating a Load Balancer, you will need to set up a private network:

openstack network create my_network
openstack subnet create my_subnet --subnet-range <my_private_ip_range/mask> --network my_network --no-dhcp
openstack router create my_router
openstack router add subnet my_router my_subnet
openstack router set --external-gateway Ext-Net my_router

You can now attach your instances to the new network. We recommend following our guide to integrate an instance into vRack. List the addresses of your instances in your network with the following command:

openstack server list

In the next step, configure the network interfaces of your instances according to this output.

 

Creating the Load Balancer

You can view a list of the different Load Balancer flavors we offer with this command:

openstack loadbalancer flavor list

To find your subnet ID, use the following command:

openstack network list

You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer.

openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet

Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address.

 

Attaching a Floating IP address to a Load Balancer

This is how to attach a Floating IP address to a Load Balancer:

openstack floating ip create Ext-Net

openstack floating ip set --port <my_load_balancer_vip_port_id> <floating_ip>
To retrieve the VIP port ID of your Load Balancer, use openstack loadbalancer show my_load_balancer.

 

Configuring your Load Balancer

In this example, we will configure an HTTP Load Balancer. To listen on port 80 of the Load Balancer, create a Listener with this command:

openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer

Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool:

openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP

Add your instances to the Instance Pool:

openstack loadbalancer member create --subnet-id my_subnet --address <private_ip_instance_1> --protocol-port 80 my_pool
openstack loadbalancer member create --subnet-id my_subnet --address <private_ip_instance_2> --protocol-port 80 my_pool

You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network.

 

Public IP

Currently, the Load Balancer details page in the OVHcloud Control Panel doesn't mention the Floating IP associated to a Load Balancer. Instructions for finding this information are in this guide.

 

View or add a health monitor

From the OVHcloud Control Panel:

  1. Select Public Cloud from the top navigation bar.
  2. Click Load Balancer from the left-hand navigation menu.
  3. Select your load balancer's Name.

PCI_networking_octaviaLB08**.png

On the following screen, choose the Pools tab and select your Pool's Name.

PCI_networking_octaviaLB09*.png

On the following screen, select the Health monitor tab. From here you can edit or delete an existing health monitor. For more information about Health monitor, please see our Concepts - Load Balancer guide.

PCI_networking_octaviaLB10*.png

 

Access L7 policies

From the OVHcloud Control Panel:

  1. Select Public Cloud from the top navigation bar.
  2. Click Load Balancer from the left-hand navigation menu.
  3. Select your load balancer's Name.

PCI_networking_octaviaLB08**.png

On the following screen, choose the Listeners tab. To the right of your listener, click the more options ... button and select See L7 policies.

PCI_networking_octaviaLB11*.png

On the following you can view, edit, delete, or create L7 policies. For more information about L7 policies, please see our Concepts - Load Balancer.

 

Go further

For further information about OpenStack Octavia, please see the official documentation of OpenStack Octavia or the Cookbook OpenStack Octavia resource.

For more information and tutorials, please see our other Public Cloud Networking support guides or explore the guides for other OVHcloud products and services.

If you need training or technical assistance to implement our solutions, contact your sales representative or click on this link to get a quote and ask our Professional Services experts for a custom analysis of your project.

Related articles