Limitations of Detaching from Rackspace Networks

When you provision a next generation Cloud Server, you can attach to one or more isolated networks and the Rackspace networks. You can also explicitly opt out of attaching to the Rackspace networks, which introduces certain limitations.

If you do not attach PublicNet to your server, it no longer has access to the Internet and some Rackspace products and services.

If you do not attach ServiceNet to your server, it cannot access certain Rackspace products and services.

The following graphic depicts the services that are not available when you do not attach the Rackspace networks to your server:

To opt out of attaching the Rackspace networks to your server:

  • nova boot command. Specify the optional --no-public and --no-service-net parameters.

  • Cloud Servers API. If you do not specify any networks, ServiceNet and PublicNet are attached by default. However, if you specify an isolated network, you must explicitly specify the UUIDs for PublicNet and ServiceNet to attach these networks to your server.

    The UUID for ServiceNet is 11111111-1111-1111-1111-111111111111, and the UUID for PublicNet is 00000000-0000-0000-0000-000000000000.

    Omit these UUIDs from the request to detach from these networks.

  • Cloud Control Panel. Clear either or both the PublicNet and ServiceNet selections during the server creation process. You are warned that your capabilities might be degraded by this choice.