• Sales: 1-800-961-2888
  • Support: 1-800-961-4454

Cloud Networks FAQ


What are the different networks in the Rackspace Cloud?

The Rackspace Cloud consists of the following networks:

  • Public (PublicNet)

    PublicNet connects a Cloud Server to the Internet.  When you create Cloud Servers with PublicNet, your servers get an IPv4 and an IPv6 address.  Outbound public traffic is billed according to published rates.  A Cloud Server can be created without a public network, however, access to operating system updates, Cloud Monitoring remote checks, and so on might not work. For more information about the limitations of not having a public network, see Removing Networks from a Cloud ServerNote: PublicNet is required for RackConnect and Managed Cloud Service Level customers.

  • Private (ServiceNet)

    ServiceNet is an internal, multi-tenant network within each Rackspace Cloud region that provides Cloud Servers access to regional services such as Cloud Files, Cloud Load Balancers, Cloud Databases, and Cloud Backup at no cost.  ServiceNet is currently IPv4 only.  Historically, ServiceNet was used for Cloud Server to Cloud Server communication, but Cloud Networks is now recommended for this purpose.  ServiceNet is also required for Windows Cloud Server activation.  We recommend that Cloud Servers be connected to ServiceNet and all new connections inbound to the server be denied by a software firewall such as iptables or Windows Firewall.  Nonetheless, a Cloud Server can be created without a ServiceNet interface. For more information, see Removing Networks from a Cloud Server. Note: ServiceNet is required for RackConnect and Managed Cloud Service Level customers.

  • Cloud Networks

    Cloud Networks are isolated networks that can be used for secure communication between your Cloud Servers. Cloud Networks are completely private and single tenant and can be either IPv4 or IPv6. Cloud Networks are recommended for all Cloud Server to Cloud Server communication. Like ServiceNet, all bandwidth on Cloud Networks is provided at no charge.

How many Cloud Networks can I create?

Every Rackspace Cloud Infrastructure Service Level account has a default limit of 10 Cloud Networks per region. To request an increase, please submit a ticket in the Cloud Control Panel with details about how you intend to use the additional networks.

Is there a limit on the number of servers that can be attached to a single cloud network?

Yes. A maximum of 250 servers can be attached to a single Cloud Network.

Can I add or remove existing networks from a Cloud Server?

Yes. You can add or remove any network (PublicNet, ServiceNet, or Cloud Networks) from a server with an Infrastructure Service Level. However, Managed Cloud Service Level and RackConnect customers are required to have PublicNet and ServiceNet interfaces. This capability means that you can freely make networking changes to your existing deployments without having to rebuild Cloud Servers. For more information, see the Virtual Interfaces section in the Cloud Networks Developer Guide. Be aware that removing PublicNet or ServiceNet interfaces might impact certain Rackspace services and capabilities.

Can I transfer Cloud Networks IP addresses from one Rackspace Cloud Server to another?

Yes. IP addresses on Cloud Networks are usable by any other Cloud Server on that network.

Can I transfer a PublicNet or ServiceNet IP address from one Rackspace Cloud Server to another?

No. At this time, you cannot transfer a PublicNet or ServiceNet IP address between Cloud Servers. 

What is the network throughput on Cloud Servers?

The amount of network throughput varies based on the Cloud Server flavor. For more details, see the Cloud Servers pricing information.

What is the scope of a Cloud Network?

Cloud Networks are regional in scope and can be attached to any of your Cloud Servers in a given region.

 







© 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