All next generation Cloud Servers automatically receive three IP addresses upon creation:
The following screenshot shows the Server Details section in the New Cloud Control Panel for a server name Zippy:
Note: First generation Cloud Servers receive only 2 IP addresses: a public v4 IP address and the internal Rackspace Network IP address. In the existing New Control Panel, the Rackspace Network is called ServiceNet.
If your Cloud Server (also known as a node within the Cloud Load Balancers product) and Cloud Load Balancer are set up in the same region, they can send traffic over the Rackspace Network without traversing the Internet, and therefore incur zero bandwidth charges. This not only saves you money, but speeds up performance of the load balancer. However, if the node is in the Chicago region and your Load Balancer is set up in Dallas, traffic cannot go across the Rackspace Network only. It must traverse the internet, which incurs normal bandwidth charges that will appear on your monthly invoice.
The following diagram illustrates this concept. The traffic between the nodes and load balancer in the Dallas region incur zero bandwidth charges, while the traffic between the node in Chicago and the load balancer in Dallas will incur normal bandwidth charges:
To take advantage of this cost savings and performance feature, you'll need to match the location of your Cloud Load Balancer with the node. The following screenshot shows you Configuration area of the Create Load Balancer page in the New Cloud Control Panel. This is where you select the Region:
Note: If you're load balancing an external node (one that is external to the Rackspace Cloud), choose the region that is geographically closest to the external node.
© 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