If your cloud is hosted at a Rackspace data center, we'll manage the hardware and the network infrastructure. However, we won't administer your cloud or its contents—just the equipment that it's hosted on.
If your cloud is hosted in your own data center, supporting your hardware and infrastructure will be your responsibility too.
No. Escalation Support only covers the configuration and components that are installed by Rackspace Private Cloud Software. Any OpenStack customizations and configuration that you apply beyond the out-of-the-box configuration are not covered by Escalation Support. More information is available at the Rackspace Private Cloud web page.
You can access the Rackspace Private Cloud Software user forum for free. The forum is hosted by Rackspace and moderated by Rackspace OpenStack specialists.
You can also purchase an Escalation Support package that supports the configuration and components of Rackspace Private Cloud Software. More information is available at the Rackspace Private Cloud web page.
Rackspace Private Cloud Software v 3.0 introduces OpenCenter, a deployment and management framework that enables users to quickly deploy an OpenStack cluster configured according to the recommendations of Rackspace OpenStack specialists. OpenCenter uses Chef to deploy Rackspace Private Cloud Software cookbooks.
OpenCenter enables cloud administrators to manage the architecture of their OpenStack private cloud through a GUI dashboard, command line interface (CLI), or API. With OpenCenter, you can perform the following tasks:
You can deploy Rackspace Private Cloud Software on Ubuntu 12.04, CentOS 6.3, or RHEL 6.3 or 6.4. The installation is performed by means of RPM and Debian packages.
Future releases of Rackspace Private Cloud Software will include support for the Folsom release of OpenStack, as well as Object Storage (Swift) and monitoring.
Rackspace Private Cloud Software v 3.0 uses the Folsom code base of OpenStack for Compute (Nova), Image Service (Glance), Dashboard (Horizon), and Identity (Keystone).
Object Storage (Swift), and Block Storage (Cinder) can be configured manually via the Rackspace Private Cloud Software cookbooks. OpenStack Networking (Quantum) is not currently supported.
Rackspace Private Cloud Software is an OpenStack configuration that has been developed, tested, and packaged by Rackspace OpenStack specialists. We've developed an OpenStack offering that is easy to install, with a configuration that comes from our expertise in developing OpenStack clouds for our customers.
You can deploy Rackspace Private Cloud Software in your own data center or in a Rackspace-managed data center. It's suitable for all scenarios, ranging from initial evaluations to production deployments.
Rackspace Private Cloud Software is suitable for anyone who wants to install a stable, tested, and supportable OpenStack private cloud.
When a new version of Rackspace Private Cloud Software is ready, upgrade packages will be made available.
There is no method for a direct upgrade from a v 1.0 cluster or v 2.0 cluster to a v 3.0 cluster; instead, you will have to create a new cluster with OpenCenter. If you want Rackspace assistance in managing and migrating backup images to a v 3.0 cluster, please email us at email@example.com.
When a patch or fix is available, updated packages will be available along with documentation for downloading it and applying it. If you have Escalation Support, we can work with you to help you apply the patch.
(Note that this question only applies to installations performed with the v.2.0 ISO.)
These operating system updates and patches may be safely applied. However, as a best practice in a production environment, Rackspace strongly recommends that you configure a mirror of your production environment in which you apply and test new OS patches and updates before applying them in production.
Rackspace Private Cloud Software includes a CIRROS image and a Ubuntu 12.04 (Precise) image. For more information about downloading and creating additional images, refer to the following OpenStack documentation.
Note that you can only upload images through the CLI. The dashboard does not include image upload functionality.
Congratulations! You can create a project, generate keypairs, add users, edit security settings, and, of course, launch instances. Refer to the Getting Started Guide for more information. Once you have the basic setup tasks complete, your cloud will be ready to use.
If you need more than 20 nodes, contact us at firstname.lastname@example.org; we'd be glad to help you scale your cloud.
Rackspace recommends a minimum of four nodes: one OpenCenter server, one Chef server, one Controller, and one Compute. This version of the installer has been tested for up to up to 20 nodes.
The Rackspace Private Cloud Software OpenCenter framework does not allow you to build an all-in-one node, but you can use the ISO to do so. Rackspace recommends that you install an all-in-one node for testing purposes only.
No. The only way we can access your cloud is if you are an Escalation Support customer and have provided us with credentials for troubleshooting.
No. The install script does not send any information to Rackspace. The only information we get from you is the information you enter on the product download page.
Rackspace Private Cloud Software downloads Ubuntu installation files as part of the installation process to ensure that you have the most up-to-date operating system that works with our software. If the node doesn't have internet access, the installation process will fail. You may also experience issues if the node is behind a firewall.
Rackspace Private Cloud Software v. 3.0 does not install any operating system. It is offered in Debian and RPM packages, and can be installed on Ubuntu 12.04, CentOS 6.3, or RHEL 6.3 or 6.4.
Rackspace strongly recommends that you install Rackspace Private Cloud Software on physical hardware nodes running Ubuntu 12.04, CentOS 6.3, or RHEL 6.3 or 6.4. Installation on virtual platforms should only be performed for evaluation purposes. You can create a single node with virtual machines to host the Chef server and and OpenCenter by following the instructions provided here.
Rackspace recommends that the OpenCenter server meets the following minimum requirements:
The Chef server hardware should meet the following requirements:
Rackspace recommends the following minimum requirements for a Controller node and a Compute node.
CPU overcommit is set at 16:1 VCPUs to cores, and memory overcommit is set to 1.5:1. Each physical core can support up to 16 virtual cores; for example, one dual-core processor can support up to 32 virtual cores. If you require more virtual cores, adjust your sizing appropriately.