OVHcloud Public Cloud networking: private networks, vRack, Gateway, Floating IP and Load Balancer

1. Public and private networks #

Two types of connectivity.

Principles #

An instance can get an interface on the public network (direct public address) and/or on private networks created in the project's vRack. The vRack can connect several regions and Bare Metal servers.

2. Creating the network #

With the OpenStack CLI.

Commands #

openstack network create prive
openstack subnet create --network prive --subnet-range 10.0.0.0/24 --dns-nameserver 213.186.33.99 prive-sub
openstack router create gw && openstack router set gw --external-gateway Ext-Net
openstack router add subnet gw prive-sub
openstack security group create web
openstack security group rule create --protocol tcp --dst-port 443 --remote-ip 0.0.0.0/0 web
openstack server create --flavor b3-8 --image "Ubuntu 24.04" --network prive --security-group web --key-name ma-cle web-1

Floating IP #

A Floating IP is a public address attached to a resource on the private network (instance or Load Balancer) and movable from one to another.

3. Load balancing #

Managed Load Balancer.

Load Balancer #

The Public Cloud Load Balancer is based on OpenStack Octavia: HTTP, HTTPS or TCP listeners, member pools, health checks, TLS termination.

openstack loadbalancer create --name lb-web --vip-subnet-id prive-sub --flavor small
openstack loadbalancer listener create --name https --protocol HTTPS --protocol-port 443 --default-tls-container-ref <secret> lb-web
openstack loadbalancer pool create --name pool-web --lb-algorithm ROUND_ROBIN --listener https --protocol HTTP
openstack loadbalancer member create --address 10.0.0.11 --protocol-port 80 pool-web
openstack loadbalancer healthmonitor create --delay 5 --timeout 3 --max-retries 3 --type HTTP --url-path /healthz pool-web

Good practice: On Managed Kubernetes, a Service of type LoadBalancer automatically creates this Load Balancer.