Abiquo and Google Cloud Load Balancers

For more details see https://cloud.google.com/load-balancing/docs/features

Abiquo 6.0 adds support for load balancers in Google Cloud Platform. GCP load balancing entities can be regional or global.

In the myCloud view, there is a new Load balancers page in the Global section to manage global entities, in addition to the page in the Locations section to manage regional entities.

To use a load balancer in GCP, first create a target group. Depending on the type of target group you select, different UI fields will display.

NOTE: You cannot create target groups in Abiquo of type: MANAGED_INSTANCE_GROUP and REGIONAL_MANAGED_INSTANCE_GROUP. However, you can onboard these target groups into Abiquo.

Unmanaged instance group

For the Unmanaged instance group, select the network, location, and availability zone of the VMs that you will add to the target group.
NetworkEndpointType - internet IP port

With this global target group, you can load balancer any IP address and port.

After you create the target group, you can create a load balancer.

Abiquo load balancer addresses are forwarding rule IP addresses in GCP. Abiquo supports one IP address.

Abiquo	GCP	Comments
Algorithm	Session affinity	https://cloud.google.com/load-balancing/docs/backend-service#session_affinity
Addresses	Forwarding rule IP	Can be an IP from a subnet (internal LB) or a public IP (external LB). Although it’s possible to create more than one forwarding rule IP inside a LB from GCP, only 1 IP address is supported by abiquo since we cannot relate addresses to routing rules. Used to identify if a LB is internal or external.
Subnets	Internal LB address subnet	A subnet used to create the forwarding rule IP in case of internal LB.
Routing rules	Forwarding rule protocol and port + target proxy (if proxy based) + url map (if http(s)) + backend service	Forward rule protocol used to identify LB type. Forward rule protocol/ port -> Routing rule protocol/port IN Backend service protocol/ named port -> routing rule protocol OUT/ port name out (Only for proxy based LBs). Backend service backends -> Forward action target groups target of the default conditional action. Balancing mode will be “Rate” for HTTP(S) LBs and “Connection” for other LBs. See https://cloud.google.com/load-balancing/docs/backend-service#balancing-mode
Health check	Backend service health check	A health check is needed for each backend service.
Firewall	None	Assigned to the VMs directly.
Nodes	None	Use target groups.
SSL Cert.	Self managed SSL Cert.	Needed for HTTPS and SSL Proxy LBs.