Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.


Abiquo 4.7

Skip to end of metadata
Go to start of metadata


The following tables summarize the load balancer functionality in each provider.

Please refer to cloud provider documentation or network manager documentation as the definitive guide to the load balancer feature.




Amazon

Abiquo supports AWS Classic load balancers.

AWS ElementNotes
AWS documentation

http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/SvcIntro.html

Healthy threshold

AWS will assign a previously unhealthy machine a healthy status after a number of successful health checks. Check the value configured for the platform with your system administrator.

Modifications

You cannot change the following attributes in AWS:

  • Name
  • Description
Load balancer Name
  • AWS will only accept the following characters: A-Z, a-z, 0-9 and "-". 
  • You cannot change the name after Abiquo creates the load balancer in AWS (when a valid load balancer is saved with a subnet assigned to it)
Algorithm
  • ROUND_ROBIN only
Abiquo-only load balancers
  • AWS load balancers are created for virtual datacenter networks, which are VPC subnets
  • The platform will not create a load balancer in AWS until it is assigned to at least one subnet
    • You can create a load balancer in Abiquo only, by not supplying a subnet
    • If you delete the load balancer directly in the provider, it will remain in Abiquo only. You can then reuse by adding a subnet so that the platform will create it in the provider
High availability
  • For high availability, create private networks (subnets) in different availability zone in your virtual datacenter
  • Abiquo 4.0+ supports virtual machines in different subnets attached to the same load balancer
Multiple incoming connectionsUse one load balancer with multiple incoming connections to different ports
Routing rules
  • You must create at least one routing rule. There must always be at least one routing rule in the load balancer
  • You can only create one routing rule per protocol and path
Subnet
  • If you do not supply a subnet when creating the load balancer, Abiquo will not create the LB in AWS
  • When you edit the load balancer, you can add new subnets and delete subnets
  • The platform supports VMs in different subnets attached to the same load balancer
Routing rule protocol inAWS accepts HTTP, HTTPS, TCP
Routing rule port inAWS accepts 80, 443 and 1024-65535 inclusive
SSL certificateCan be a new certificate or an existing one registered in AWS with an ARN.
  • To list and upload SSL server certificates to IAM your user requires IAM privileges to manage IAM
  • Abiquo never stores SSL certificates, so you cannot create a routing rule for a secure connection in an Abiquo-only load balancer that is not assigned to a subnet
Health check
  • If you do not create a health check, AWS will create a default health check with the following specifications:
    • Name in the format "PROTOCOL:port", for example, "TCP:80"
    • TCP check to one of the ports specified in a routing rule
  • AWS will only allow you to create one health check per load balancer
Firewalls
  • If a firewall does not display, it may not have been properly synchronized. In this case, you will need to click Cancel, synchronize firewalls and start again creating a new load balancer



Azure

Abiquo supports Basic SKU load balancers. It does not support Standard SKU Load Balancers.

Azure ElementNotes
Azure documentationhttps://docs.microsoft.com/en-us/azure/load-balancer/ 
Load balancer Name

The load balancer name can't have white spaces

Algorithm
  • DEFAULT
  • SOURCEIP
  • SOURCEIPPROTOCOL
Addresses and networks
  • The load balancer must have one and only one public OR private address
  • The load balancer can only be attached to one subnet. Mandatory for private addresses  
Multiple incoming connectionsUse one load balancer with multiple incoming connections to different ports
Routing rules
  • You must create at least one routing rule. There must always be at least one routing rule in the load balancer
  • You can only create one routing rule per incoming port and one rule per outgoing port (i.e. two rules cannot receive traffic on the same port or route it to the same port).
Routing rule protocol inTCP and UDP
Routing rule port inIN and OUT port must be the same
SSL certificateNot yet supported
Health check
  • Only one health check can be configured for the load balancer
      • Protocols supported for healthcheck: TCP, HTTP
      • Health check interval must be between 5 and 2147483646
      • Health check port must be between 1 and 65535
FirewallsAzure NSGs are not yet supported
NodesAzure does not allow you to attach a VM with a Basic hardware profile to a load balancer



Rackspace


Rackspace ElementNotes
Rackspace documentationhttp://docs.rackspace.com/loadbalancers/api/v1.0/clb-devguide/content/
Algorithms
  • The algorithms Rackspace supports are:
    • LEAST_CONNECTIONS
    • RANDOM
    • ROUND_ROBIN
    • WEIGHTED_LEAST_CONNECTIONS
    • WEIGHTED_ROUND_ROBIN
Load balancing multiple
incoming protocols and ports
Use multiple load balancers to the same IP address each with an incoming connection with a different protocol and to a different port
Routing rulesIn Rackspace you must create only one routing rule for incoming traffic per load balancer
Changes to routing rulesYou can only add new rules with same incoming port and protocol and delete rules until there is only 1 rule remaining
Health check protocols
  • Rackspace supports HTTP, HTTPS and CONNECT
  • The health check protocols HTTP and HTTPS can only be used with routing rules for the same protocol
Health check pathRequired by RackSpace for health monitors using HTTP and HTTPS protocols
FirewallsRackspace provides automatic port filtering for load balancers, so no firewalls screen is displayed



Openstack Neutron load balancers table


OSN ElementNotes
OpenStack Neutron documentation
Complete OpenStack Neutron guide:
Docs specific to Load Balancers:
http://docs.openstack.org/liberty/networking-guide/adv-config-lbaas.html
Algorithms
  • The algorithms Neutron supports are:
    • round robin
    • least connections
    • source IP
Load balancing multiple
incoming protocols and ports
Use multiple load balancers to the same IP address each with an incoming connection with a different protocol and to a different port
Routing rule protocols in

Neutron accepts HTTP, HTTPS, TCP

Changes to routing rule protocols-inIf no nodes are assigned, you can change port and protocol to add new rules with same in-port and protocol and delete rules until there is only 1 rule remaining
Routing rule ports in

Neutron accepts 80, 443 and 1024-65535 inclusive

Health check protocols

Neutron supports: PING, TCP, HTTP, HTTPS

Health check protocol
  • The health check protocols HTTP and HTTPS can only be used with routing rules for the same protocol
  • Only one check per protocol and path. The health check protocol must be compatible with the routing rule protocol
Abiquo-only load balancers
  • You cannot create a load balancer without a subnet directly
  • However, you can later modify the load balancer to make it an Abiquo-only load balancer




VMware NSX load balancers table


NSX ElementNotes
NSX documentationhttps://www.vmware.com/support/pubs/nsx_pubs.html
Load balance multiple protocols and portsUse multiple load balancers to the same IP address each with an incoming connection to a different port
Algorithms
  • The algorithms NSX supports are:
    • ROUND_ROBIN
    • IP_HASH
    • LEAST_CONN
    • URI
    • HTTP_HEADER
    • URL
AddressesIn NSX a load balancer must have at least one private address
Routing rule protocols in

NSX accepts HTTP, HTTPS, TCP and UDP

Changes to routing rulesYou can change NSX routing rules after they have been created
Health checkThe health check is not required
Health check protocols

NSX supports: HTTP, HTTPS, TCP, UDP, ICMP



vCloud Director load balancers table


vCloud Director ElementNotes
vCloud Director documentationVMware vCloud Director documentation center
Load balance multiple protocols and portsUse multiple load balancers to the same IP address each with an incoming connection to a different port
Algorithms
  • The algorithms vCloud Director supports are:
    • ROUND_ROBIN
    • IP_HASH
    • LEAST_CONN
    • URI
AddressesIn vCloud Director a load balancer must have a "public address", which is an address on an external network (connected to the Edge, meaning external to the OrgVDC or external routed networks). The platform does not support the use of private subnets for load balancers in vCloud because vCloud cannot use isolated external networks or private networks when creating load balancers. To load balance multiple protocols and ports, you can use multiple load balancers to the same IP address but each with a different port.
Routing rule protocols in

vCloud Director accepts HTTP, HTTPS, TCP

Changes to routing rulesYou can change vCloud Director routing rules after they have been created
Health checkA health check is required by the platform
Health check protocols

vCloud Director supports: HTTP, SSL, TCP. For HTTP routing rules, vCloud supports HTTP or TCP health checks. For HTTPS rules, it supports SSL or TCP. For TCP rules, it only supports TCP.

NodesThe platform will add the nodes to the load balancer pool on the Edge in vCloud when you deploy them. You cannot register a VM to a load balancer if it is not using an IP in an external OrgVDC or routed network.
vCloud vAppsThe platform does not support NSX-Edge Compact or fenced vApps.



  • No labels