Load balancing (LBaaS)

Load balancing is used to avoid server overloading and efficiently delivering web services from a multi-server architecture. It helps ensure the scalability and availability of services. Balancers with advanced traffic management functionality direct requests more efficiently to the best resources for each end-user.

LBaaS in Beryllium

In Beryllium, Pan-Net cloud features Level 4 Load Balancing based on Juniper Contrail. In a Contrail vRouter, the hypervisor is using Equal Cost Multi Path (ECMP), which assigns flows to paths based on a hash function taking as argument source and destination IP addresses, ports and protocol, supported by an interface-route table.

LBaaS is a Contrail feature offered by Pan-Net as an optional service. It is characterized by

  • Can be used for connectivity within a data center or between data centers

  • Flow hashing based on 5-tuple (source IP, destination IP, protocol, source port, destination port), that is, layer 4

  • Establishes direct connection between components and supports flow stickiness

  • Health checks can be configured on a port basis. The port will be set to down status if the health check fails and will, therefore, be removed from the list of next-hops. Health checks can be configured for ping and HTTP.

More information about the Load Balancing concept can be found under Concepts in Load balancing

LBaaS in Boron

In Boron, the LBaaS is based on Octavia Amphora instances that can be deployed by the customer by OpenStack commands as described in Configure LBaaS

An alternative LBaaS with ECMP support is based on BGPaaS, which is required for route management. For more details, see Configure BGPaaS