Learn how to link and configure your OVHcloud Load Balancer in vRack via the APIv6.
The vRack is a dedicated private network that creates a link between all your cloud products. For more information, please visit our vRack page.
Before starting, we suggest reading our Introduction to the OVHcloud Load Balancer guide.
NOTE: Once linked to your vRack, the clusters of your Load Balancer will be unable to communicate with your servers via their public IP addresses. You will then be forced to use their private IP address inside the vRack.
Instructions
Listing Load Balancer services eligible for vRack
You can consult the list of your Load Balancer services that can be connected to a vRack.
The serviceName in the API below is the one for your vRack, e.g., pn-1234.
You will find your Load Balancer services in the index: ipLoadbalancing.
You can also see the eligibility of a particular Load Balancer service through the 'vrackEligibility' attribute of the call response:
Linking a Load Balancer service to a vRack
To attach your Load Balancer service to your vRack, here is the relevant API call:
As previously mentioned, the serviceName here is the name of your vRack, e.g., pn-1234.
Configuring a vRack network
To work, your Load Balancer needs to know the network topology that you use within your vRack and have a range of IP addresses specifically dedicated to it within that network. This IP address range will be used to contact your servers in your vRack. No other IP addresses will be used to communicate with your servers.
Example configuration:
- serviceName: loadbalancer-1234...
- subnet: 192.168.0.0/16
- natIp: 192.168.100.0/24
- vlan: 42
The natIp block must be contained in your subnet.
Once your network is created, you will need to retrieve its vrackNetworkId for the configuration of your clusters.
To find out the minimum range size to be assigned to natIp, an API call is available.
Setting up a server cluster linked to a vRack
You can now create your server cluster in the vRack. To do so, configure your TCP or HTTP cluster as usual, and fill in the vrackNetworkId you previously obtained in the field of the same name.
Continuing the configuration
You can now use the usual API call or even the client area to continue configuring the Load Balancer.
As a reminder, a configuration guide for the Load Balancer is available here.
Go further
For more information and tutorials, please see our other OVHcloud Load Balancer guides or explore the guides for other OVHcloud products and services.