Abiquo 6.0 adds support for load balancers in Google Cloud Platform. 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 In GCP, load balancing entities can be regional or global.
...
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.
Here are some examples of typical target groups
- Unmanaged instance group
For the Unmanaged instance group, select the network, location, and availability- Note that you should enter a Name for the receiving Port, which you will also need to enter in the Load balancer's Routing rule tab
- And select the Global network, Subnet, Location, and Availability zone of the VMs that you will add to the target group
- NetworkEndpointType - internet IP port port
- With this global target group, you can load balancer any IP address and 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, in the Location (regional) or Global section.
Abiquo supports load balancer addresses are forwarding rule IP addresses in GCP. Abiquo supports one IP address.
...
Abiquo
...
GCP
...
Comments
...
Algorithm
...
Session affinity
balancers that are internal (using a subnet IP address) and external (using a public IP address). You can select one IP address for your load balancer. If you are creating an internal load balancer with a subnet address, you will need to select a private subnet.
The Algorithm in Abiquo represents the session affinity in GCP. See 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
For the Routing rules, if your target group is an unmanaged instance group, then you will need to supply the same name of the port as the "out name".
In GCP, the Routing rules represent the Forwarding rule protocol and port + target proxy (if proxy based) + url map (if
...
HTTP(s)) + backend service.
And the Forward rule protocol can be 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
...
And you will need to create a health check for each backend service.
...
Firewall
...
None
...
Assigned to the VMs directly.
...
Nodes
...
None
...
Use target groups.
...
SSL Cert.
...
Self managed SSL Cert.
...
After you create a load balancer, you can add nodes to the target groups. The nodes may be IP addresses and ports.
Or they may be VMs.
You can check the health of the VM nodes on the Target Group details panel. After you select the Load balancer from the drop-down in the top-right hand corner, the platform will display the Status of each node.