Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I recently got a chance to work on both lbaas and lbaasv2... So it goes like this

  1. lbaas - it uses HAProxy inside. This runs as a process inside the network namespace. This namespace is present in the network node of the openstack setup. When the user hits the lbaas IP it goes to the network namespace where HAproxy is running and then its al HAproxy working with its pools, members and crazy load balancing stuff

  2. lbaasv2- Ot uses an image known as Amphora inside. When we talk about image its actually a VM getting created on the compute node. This entire project is known as Octavia. In layman terms a virtual machine is created instead of a network namespace. Inside this VM the LBAAS service is running and will have its pools, members and crazy load balancing stuff

Why have we done it :-

  • This is an operator grade LbaaS
  • Suppose you see that the performance of load balancer is not good and you require more resources. This can be easily done by providing a new flavor to the VM.