Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

Excerpt
hiddentrue

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.

...

Here are some examples of typical target groups

  • Unmanaged instance group

    • 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 networkSubnetLocation, and Availability zone of the VMs that you will add to the target group

      Image Modified


  • NetworkEndpointType - GCE IP port

    • With this target group, you can load balance addresses and ports in Google Cloud Platform networks 

  • Note: This screenshot shows Internet IP port, which only works with Classic load balancers 

    Image RemovedImage Added

After you create the target group, you can create a load balancer, in the Location (regional) or Global section.

...

The Algorithm in Abiquo represents the session affinity in GCP. See https://cloud.google.com/load-balancing/docs/backend-service#session_affinityImage Removed

...

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 from the target group as the "out name".

In GCP, Abiquo Routing rules represent the Forwarding rule protocol and port + target proxy (if proxy based) + URL map (if HTTP(s)) + backend service.

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:

  • RATE: HTTP, HTTPS, HTTP2

  • CONNECTION: SSL, TCP, UDP

See https://cloud.google.com/load-balancing/docs/backend-service#balancing-mode

...

You will need to create a health check for each backend service.Image Removed

...

After you create a load balancer, you can add nodes to the target groups.

...

Or the nodes may be IP addresses and ports.Image Removed

...

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.Image Removed

...

To add or change a target group, edit the load balancer, go to Routing rules, select the routing rule, and click Edit conditional actions.Image Removed

...

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.Image Removed

...

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.