Versions Compared

Old Version 3

changes.mady.by.user MS

Saved on

compared with

New Version Current

changes.mady.by.user Lou M

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Version published after converting to the new editor

AWS table

...


FirewallsIf 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
vCloud Director elementNotes
vCloud Director documentation
SSL certificates
  • 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 network
Healthy threshold
  • AWS will assign a previously unhealthy machine a healthy status after a number of successful health checks. Check the value configured for your 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
  • Abiquo 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
High availability
  • For high availablility, 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 portsRouting 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
  • Abiquo 4.0+ supports virtual machines in different subnets attached to the same load balancer
Routing rule protocol inAWS accepts HTTP, HTTPS, TCPRouting rule port inAWS accepts 80, 443 and 1024-65535 inclusiveSSL certificateCan be a new certificate or an existing one registered in AWS with an ARNHealth 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
VMware 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 check
  • A health check is required by the platform.
  • During synchronization, the platform will skip load balancers without health checks
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.