libra_client --os_auth_url=https://company.com/openstack/auth/url \
--os_username=username --os_password=pasword --os_tenant_name=tenant \
--os_region_name=region create --name=my_load_balancer \
--node 192.168.1.1:80 --node 192.168.1.2:80
This example will create a basic load balancer which will listen on
port 80 and direct traffic in a round-robin fashion to two nodes,
192.168.1.1 and 192.168.1.2. Both these nodes are web servers listening
on port 80. The Libra Client will then return a table similar to the
below:
It is possible for a single logical load balancer to balancer traffic
for both HTTP and HTTPS for a site. For this example we will add an
HTTPS load balancer to the load balancer we created previously:
libra_client --os_auth_url=https://company.com/openstack/auth/url \
--os_username=username --os_password=pasword --os_tenant_name=tenant \
--os_region_name=region create --name=my_load_balancer \
--node 192.168.1.1:443 --node 192.168.1.2:443 --protocol=TCP --port=443 \
--vip=52
We have taken the IP ID which was provided in the original create and
given this as a VIP number in the command. We are also setting to TCP
mode so the SSL termination happens at the web server and set the load
balancer to listen on port 443. The result is as follows:
libra_client --os_auth_url=https://company.com/openstack/auth/url \
--os_username=username --os_password=pasword --os_tenant_name=tenant \
--os_region_name=region node-add --id=1158 --node=192.168.1.3:443
In this example we have take the ID of the load balancer of the
previos example to add a web server to. The result should look something
like this: