Create an Isolated Cloud Network
NOTE: Cloud Networks is production ready but is being made available to customers in a phased release. Therefore, it might not be visible when you log into the New Cloud Control Panel. To request access to Cloud Networks now, click here.
Cloud Networks lets you create a virtual Layer 2 network that you can attach to a new next generation Cloud Server. This lets you keep your Cloud Server separate from the Rackspace network, the internet, or both.
Limitations
-
The Cloud Network must exist in the same region as the Cloud Server.
-
You can create up to 3 isolated networks with up to 64 servers attached to each one.
-
A network cannot be renamed after it is created.
Attach an Isolated Network to a Cloud Server
To attach an isolated Cloud Network to a new Cloud Server:
-
In the New Cloud Control Panel, click Servers in the navigation menu.
-
Click Create Server.
-
Enter a name for the server, select the Region, Type and Size.
-
Click Create Network to create a new isolated:
-
In the Create Network popover, enter a name for the network and click Create Network. Note that you cannot rename the network later.
-
(Optional) Click a network in the Networks table to remove it from the server. WARNING: Before you remove ServiceNet or PublicNet from your Cloud Server, we highly recommend that you read Removing Networks from a Cloud Server for a complete description of the limitations that will be placed on this server.
- Click Create Server.
Your new Cloud Server is created and attached to the new isolated Cloud Network.
When the server build is complete, you can scroll down to see the Networks table. The table displays each network the server is atatched to with the corresponding IP address. Here's an example Networks table for a server that is attached to PublicNet (internet), ServiceNet (the Rackspace data center network), and an isolated Cloud Network named My Private Network:
More Information on Cloud Networks
Attach an Isolated Network to an Existing Cloud Server
© 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
5 Comments
limitations
Both numbers should grow!
I'm the network architect for this product. We definitely intend to increase both of these numbers over time. We just launched with limited availability in October and want to make sure everyone gets a consistent, stable experience with our isolated networks, but absolutely understand that there are architectures and applications that would benefit from both larger switches and more of them. Do you have any specific numbers in mind that would meet your needs?
Thank you!
growth
cheers
mike
Brad, getting further into my
thanks
mike
Michael,
Sorry I'm slow to reply this time around. The way our limits are designed, each data center region (metro area) will allow you to create 3 networks so you should be able to create the networks you need. If you find that you end up needing more than you originally thought, I'd recommend getting in touch with the cloud support team. The network count is a soft limit that can be modified, they just like to understand the use cases right now. We haven't settled on what our end state will be, but I expect down the road everyone will be able to create more than three per region without having to get in touch with support.
Add new comment