RackConnect Key Terms


APPLIES TO: RackConnect v3.0, RackConnect v2.0

We have created this article to cover many of the key terms you will encounter with RackConnect—to help you better understand how RackConnect works. Next to each term, in parenthesis, we have noted whether the term applies to RackConnect v2.0 (v2.0), RackConnect v3.0 (v3.0), or both (v2.0, v3.0).

Access Lists (v2.0, v3.0)

Used on network devices to control what network traffic is allowed between network segments. Access lists are also known as ACLs.

Automation Features (v2.0)

Automation features control which actions the RackConnect automation systems will and will not take against your environment. In certain cases, the settings may differ between your cloud account and your individual cloud servers. The cloud account settings will be used for all new servers you build in the future, while the existing cloud server settings will be used if you perform a rebuild or make other changes to your cloud server.


Automation features configuration example

Note: It is not currently possible for you to adjust automation features settings; they are displayed for informational purposes only.  Please contact your support team if you need to modify these settings.

Cloud Networks (v2.0, v3.0)

Isolated networks that you can create and attach to your cloud servers, as network interfaces, that only allow traffic between cloud servers that are part of the same isolated network. In essence, they are secure networks whose traffic is restricted to only the cloud servers that you allow. In the case of RackConnect v3.0, they are also used to communicate with your dedicated networks.

Connected Network Device Role (v2.0, v3.0)

The dedicated network device that provides a physical connection and path to the cloud-side of your RackConnect environment.  This device can be a firewall or a load balancer. RackConnect gateway IP addresses live on this device. Additionally, a single network device can function in both the edge and connected network device roles.

Edge Network Device Role (v2.0, v3.0)

The outermost dedicated network device in your RackConnect configuration—it is the device that directly connects to the Internet. This is typically a firewall, but it can also be a load balancer in certain deployment scenarios. Additionally, a single network device can function in both the edge and connected network device roles

Network Policies (v2.0):Define network access allowed in one of five RackConnect traffic scenarios:

  • Traffic from Cloud Servers to Dedicated
  • Traffic from Cloud Servers to the Internet
  • Traffic from Cloud Servers to Cloud Servers (for example, traffic between a web tier and an application tier, both hosted on Cloud Servers)
  • Traffic from Dedicated to Cloud Servers
  • Traffic from the Internet to Cloud Servers

Network policies provide you with the ability to match network traffic based on certain criteria—(hosts, networks, and cloud server name matches)—in order to limit access to only allowed protocols and ports (or port ranges).

Network Policy Templates (v2.0)

Provide an easy way of getting started with RackConnect network policies; they allow you select from among some of the most common RackConnect network policy options. For example, the “Basic Access Configuration Template,” if applied, allows you to have unrestricted network access between your dedicated and cloud servers.

PublicNet (v2.0, v3.0)

A network that may be added to your cloud servers, as a network interface, to allow traffic directly with the public Internet. If enabled, it is very important to secure this network, as this network is vulnerable to attacks from the Internet.

QoS (v3.0)

Stands for quality of service. With RackConnect v3.0, it is used to limit the amount of bandwidth allowed between your cloud and dedicated networks via RackConnect.

RackConnect Configuration (v2.0, v3.0)

Represents a single deployment of a RackConnect solution.  A configuration is comprised of dedicated network devices that function in the RackConnect edge and connected network device roles, along with the stored settings needed to make these devices function with RackConnect. You may have multiple RackConnect configurations. A configuration is normally associated with one or more cloud accounts.

ServiceNet (v2.0, v3.0)

Cloud ServiceNet is a shared network within each region that may be added to your cloud servers, as a network interface. It is normally utilized to allow cloud servers to take advantage of other Public Cloud products, such as Cloud Files, to communicate between your cloud servers in a given region, or in the case of RackConnect v2.0, to communicate with your dedicated network. If enabled, it is very important to secure this network, as other Rackspace Public Cloud customers are also on this network.

Edge Network Device Role (v2.0, v3.0)

The outermost dedicated network device in your RackConnect configuration—it is the device that directly connects to the Internet. This is typically a firewall, but it can also be a load balancer in certain deployment scenarios. Additionally, a single network device can function in both the edge and connected network device roles

Connected Network Device Role (v2.0, v3.0)

The dedicated network device that provides a physical connection and path to the cloud-side of your RackConnect environment.  This device can be a firewall or a load balancer. RackConnect gateway IP addresses live on this device. Additionally, a single network device can function in both the edge and connected network device roles.

Network Policy Templates (v2.0)

Provide an easy way of getting started with RackConnect network policies; they allow you select from among some of the most common RackConnect network policy options. For example, the “Basic Access Configuration Template,” if applied, allows you to have unrestricted network access between your dedicated and cloud servers. 

We hope that you have found this article helpful, but if you have any further questions, we are always here to help, so please reach out to us; contact information is available on the Contact Us page.



Was this content helpful?




© 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


See license specifics and DISCLAIMER