| Excerpt | ||
|---|---|---|
| ||
Abiquo 6.0 adds support for load balancers in the Google Cloud Platform. Abiquo supports regional and global load balancers, with new sections in the user interface. Abiquo supports external and internal load balancers on Google's VPC networks. The supported load balancer backends include unmanaged instance groups and GCE network endpoint groups. |
Abiquo 6.0 adds support for load balancers in Google Cloud Platform. For more details see https://cloud.google.com/load-balancing/docs/features
In GCP, load balancing entities can be regional or global.
In the the myCloud view view, there is a new new Load balancers page in the the Global section section to manage global entities, in addition to the page in the the Locations section 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.
...
- Unmanaged instance group
- Note that you should enter a a Name for for the receiving receiving Port, which you will also need to enter in the Load balancer's s Routing rule tab tab
- And select the the Global network, Subnet, Location, and and Availability zone of of the VMs that you will add to the target group
- Google Compute Engine VM NetworkEndpointType - GCE IP port
- To With this target group, you can load balance IPs in Google Compute Engine, which can be public IPs or subnet IPsaddresses and ports in Google Cloud Platform networks
- Note: This screenshot shows Internet IP port, which only works with Classic load balancers
After you create the target group, you can create a load balancer, in the the Location (regional) or or Global section section.
Abiquo supports load 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 in Abiquo represents the session affinity in GCP. See https://cloud.google.com/load-balancing/docs/backend-service#session_affinity
For the the Routing rules, if your target group is an unmanaged instance group, then you will need to supply the same name of the port from the target group as the "out name".
In GCP, the Abiquo Routing rules represent the Forwarding the Forwarding rule protocol and port + target proxy (if proxy based) + url URL map (if HTTP(s)) + backend service.And the Forward rule protocol can be used to identify LB type.
| GCP | Abiquo |
|---|---|
| Forward rule protocol |
...
| , port |
...
Routing rule protocol |
...
, Port In |
| Backend service protocol |
...
| , named port |
...
| Routing rule protocol OUT |
...
| , port name out ( |
...
| for proxy based |
...
| load balancers) |
...
| Backend service backends |
...
Forward action, target groups target of the default conditional action |
...
: Balancing mode |
...
:
See https://cloud.google.com/load-balancing/docs/backend-service#balancing-mode |
And you You will need to create a health check for each backend service.
After you create a load balancer, you can add nodes to the target groups.
The nodes may be IP addresses and portsVMs.
Or the nodes may be VMsIP addresses and ports.
You can check the health of the VM nodes on the the Target Group details panel. After you select the the Load balancer from the drop-down in the top-right hand corner, the platform will display the Status Status of each node.
To add or change a target group, edit the load balancer, go to Routing rules, select the routing rule, and click Edit conditional actions.
To edit the conditional action, click the pencil edit button, make your changes, and click Accept. When you finish editing, save the routing rule with the load balancer.
The Weight represents the maximum connections per instance/endpoint for CONNECTION protocols, and the maximum rate per instance/endpoint for RATE protocols. See https://cloud.google.com/load-balancing/docs/backend-service#target_capacity.