Rackspace has developed Rackspace Private Cloud Software, a fast, free, and easy way to download and install a Rackspace Private Cloud powered by OpenStack in any data center. Rackspace Private Cloud Software is suitable for anyone who wants to install a stable, tested, and supportable OpenStack private cloud, and can be used for all scenarios from initial evaluations to production deployments.
Rackspace Private Cloud Software v 3.0 supports the Folsom release of OpenStack.
This document describes the updates in Rackspace Private Cloud Software v 3.0 and any known issues in the product. You should already be familiar with Rackspace Private Cloud Software and have prior knowledge of OpenStack and cloud computing, basic Linux administration skills, and a side of bacon. :)
This version of the Rackspace Private Cloud Software Release Notes replaces and obsoletes all previous versions. The most recent changes are described in the table below:
|Revision Date||Summary of Changes|
|March 6, 2013||
|March 20, 2013||
For more information about sales and support, contact us at
>. For feedback on the product and the documentation, contact us at
>. For the documentation, you can also leave a comment at the Knowledge Center.
Rackspace Private Cloud Software v 3.0 has the following new features and documentation.
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.
OpenCenter has three components:
The following user documentation is available for Rackspace Private Cloud Software via the Rackspace Knowledge Center:
Note: Rackspace recommends that you run OpenCenter behind a firewall, as it is not considered secure at this time.
Rackspace Private Cloud Software has the ability to implement support for high availability for all Nova service components and APIs, Cinder, and Keystone, and Glance, as well as the scheduler, rabbitmq, and mysql. HA functionality is powered by Keepalived and HAProxy.
High Availability is implemented when you create two Controller nodes in a Nova cluster. When the second node is created, it discovers the IP address of the first node and begins replication; in turn, when Chef client runs on the first node, it discovers the second and begins replication.
The following known issues have been identified in Rackspace Private Cloud Software v. 3.0.
Users may experience collectd failures with monitoring processes or after performing a failover to a standby node. In the event of a failure, kill any active collectd process and run
chef-client on the node again.
Occasionally, dragging a node into the Infrastructure container may appear to briefly fail, with the node appearing to return to the Available Nodes container. OpenCenter is actually in the process of creating the adventure. If you wait briefly, the node will appear in the Infrastructure container.
Cookie issues associated with the admin user may cause the user to randomly switch between the demo project and the admin project. You may also experience connectivity issues if you do not log out correctly. This is related to a known issue in OpenStack.
To work around this issue, do not create instances when logged in as the admin user. To create new instances, use the demo project or a new project as a non-admin user.
In an environment with HA Infrastructure nodes, instance VNC in the Horizon dashboard will not work.
If you are installing Rackspace Private Cloud Software on devices with Ubuntu and KVM, you should use a base install of Ubuntu 12.04 or 12.04.1 where the latest available kernel version is 3.2.n (as of March 2013).
You should avoid a base install of Ubuntu where the default kernel version is greater than 3.2.n, which are currently point releases 12.04.2 and later. You can safely upgrade your base install of 12.04 or 12.04.1 to the latest point release as long as the kernel version remains 3.2.n. This is related to a known issue in OpenStack.
The following issues have been resolved in Rackspace Private Cloud Software v 3.0.
Errors previously generated by clicking on the Rackspace logo in the Rackspace custom Horizon dashboard no longer occur.
© 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