When leveraging your Cloud Servers to host an application that scales up and down (e.g., the web tier of an application), it is important to have a method for adding and removing Cloud Servers from their associated load balancer pool(s). If you use an F5 Big-IP Local Traffic Manager with RackConnect, you can specify the load balancer pool name that a Cloud Server should be placed into upon creation. When you delete the Cloud Server, it will automatically be removed from the pool.
With RackConnect, there are two ways that you can automatically associate your Cloud Servers with one or more load balancer pools on your F5:
Option 1 — Metadata: When creating a Cloud Server, leverage the metadata option to specify the pool(s).
Metadata Key: RackConnectLBPool
Metadata Value: (The exact name of the pool as defined on the load balancer; use a semi-colon separated list for more than one pool)
In this example, multiple Metadata Pool values are entered for the Cloud Server
Additionally, you can also specify the metadata values when utilizing the Cloud Servers API to create new cloud servers. Please view the API documentation for further details on how to utilize the API to enter metadata information for a cloud server:
Note: The metadata values are only read by RackConnect when a cloud server is initially created, so changing the metadata values for a cloud server that is already deployed will not have any effect on Load Balancer Pool memberships.
Option 2 — Name Match: Before spinning up your Cloud Servers, provide us with your preferred name and the pool(s) to associate with your Cloud Servers. Currently, you must configure this through a ticket request to your Support team.
Regardless of which option you select:
To get the name of one or more load balancer pools, contact your Support team.
Here is a diagram of the path that inbound (and return) Load Balancer Pool traffic follows to your RackConnected Cloud Servers when utilizing an F5 with RackConnect:
The Brocade ADX can also be used as a load balancer that balances traffic between dedicated and cloud servers. In this case, the RackConnect Connected Device will be an ASA Firewall and any traffic that needs to be load balanced to cloud servers will flow from the ADX to the Firewall to the cloud servers.
Benefits of utilizing a Brocade Load Balancer with RackConnect:
Limitations of utilizing a Brocade Load Balancer with RackConnect:
* A 'sorry server' normally contains a static maintenance page that users are directed to when health checks fail for all the members of a Load Balancer Pool.
** Your Support Team can provide more details on the caveats around maintaining Client Identity.
Here is a diagram of the path that inbound and return Load Balancer Pool traffic follows to your RackConnected cloud servers when utilizing a Brocade with RackConnect:
Please contact your Support Team if you have any questions about using Dedicated Load Balancers with RackConnect.
© 2011-2013 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License