Rackspace Private Cloud v. 4.0 Release Notes
Rackspace has developed a fast, free, and easy way to install a Rackspace Private Cloud powered by OpenStack in any data center. This method is suitable for anyone who wants to install a stable, tested, and supportable OpenStack-powered private cloud, and can be used for all scenarios from initial evaluations to production deployments.
Rackspace Private Cloud v 4.0 supports the Grizzly release of OpenStack.
Note: Rackspace Private Cloud has been updated to v 4.1.2. Refer to the v 4.1.2 release notes for information about the changes made in that release.
This document describes the updates in Rackspace Private Cloud v 4.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 Release Notes replaces and obsoletes all previous versions. The most recent changes are described in the table below:
|Revision Date||Summary of Changes|
|June 25, 2013|
|July 1, 2013|
|September 4, 2013|
- Rackspace Private Cloud Software Home Page
- Rackspace Private Cloud Knowledge Center
- Rackspace Private Cloud Forums
For more information about sales and support, contact us at email@example.com. For feedback on the product and the documentation, contact us at RPCFeedback@rackspace.com. For the documentation, you can also leave a comment at the Knowledge Center.
Rackspace Private Cloud v 4.0 has the following new features.
- Installing Rackspace Private Cloud
- OpenStack Grizzly
- OpenStack Networking
- OpenStack Identity v2 with Active Directory and LDAP
- OpenStack Block Storage Third-Party Vendors
- VMWare VMDK Image Import
- Cloud Files with OpenStack Image Storage
- OpenStack Ceilometer
Rackspace Private Cloud v 4.0 is deployed through a series of bash scripts in the following stages:
- Install Chef server on a node in the environment.
- Download the latest cookbooks to the Chef server.
- Install chef-client on each node that will be managed by Chef in your OpenStack cluster.
- Use Chef to create Controller nodes, Compute nodes, and more.
For a detailed description of the prerequisites and process, refer to Installation Prerequisites and Concepts and Installing OpenStack With Rackspace Private Cloud Tools.
The OpenCenter installer scripts are still available; however, OpenCenter only supports the Folsom release. An environment installed with OpenCenter can be upgraded to Grizzly, but the results have not been tested. For more information, refer to Upgrading Your Private Cloud.
Rackspace Private Cloud Software now installs and supports the OpenStack Grizzly release. Existing Folsom environments installed with the Rackspace Private Cloud cookbooks can also be updated to Grizzly with the procedure documented in Upgrading Your Private Cloud.
For detailed information about what is included in Grizzly, refer to the Grizzly release notes.
Rackspace Private Cloud Software now supports OpenStack Networking (Neutron, formerly Quantum). The Networking configuration provided by the Rackspace Private Cloud cookbooks allows you to choose between VLAN or GRE isolated networks, both provider- and tenant-specific. From the provider side, an administrator can also create a flat network. Concepts and configuration are described in Configuring OpenStack Networking.
Currently, you cannot use Neutron routers, and the quantum-server service is not HA.
Rackspace Private Cloud Software now supports using Active Directory and LDAP as a backend for OpenStack Identity (Keystone). For instructions about configuring your environment for Active Directory and LDAP, refer to Active Directory and LDAP Integration.
Rackspace Private Cloud Software supports using OpenStack Block Storage (Cinder) with the following third-party storage vendors:
For instructions about configuring your environment for these vendors, refer to Configuring OpenStack Block Storage.
Rackspace has developed a tool to convert single-disk Linux VMDK images to OpenStack-compatible qcow2 images. The conversion is accomplished by means of a Python script available at
https://github.com/rcbops/support-tools/tree/master/vmdk-conversion. For instructions about using the tool, refer to Converting VMDK Linux Images.
Multi-disk and Windows image conversions are not available at this time.
Amazon AMI images can also be imported into Glance. For instructions about importing AMI images, refer to Uploading AMI Images.
You can configure Rackspace Cloud Files as a backend for OpenStack Image Storage (Glance). For instructions about configuring your environment for Cloud Files, refer to Configuring OpenStack Image Storage.
The Rackspace Private Cloud installation includes OpenStack Ceilometer for the OpenStack cluster. In this installation, Ceilometer is only accessible through the API. For information about the Ceilometer API, refer to the Ceilometer Developer Documentation. Ceilometer is automatically included when you create your Controller and Compute nodes, and no additional configuration is required.
NOTE: The Ceilometer API cannot co-exist on a node with haproxy.
The following issues have been identified in Rackspace Private Cloud v. 4.0 and v 4.1.2.
Updating Cookbooks with knife cookbook upload -a -o
When updating to the v 4.0.0 cookbooks, Chef Server might fail to upload the cookbooks on the first attempt. If this happens, run
knife cookbook upload -a -o again. This is related to known Chef issue CHEF-4330.
RHEL and CentOS Challenges With Advanced OpenStack Networking
When using OpenStack Networking (Neutron), Controller nodes with Networking features and standalone Networking nodes require namespace kernel features that are not available in the default kernel shipped with RHEL 6.4, CentOS 6.4, and older versions of these operating systems. More information about Neutron limitations is available in the OpenStack documentation, and more information about RedHat-derivative kernel limitations is provided in the RDO FAQ.
If you require OpenStack Networking using these features, Rackspace recommends that you consider the RHEL and CentOS patches, or use Ubuntu 12.04 for the Controller and Networking nodes.
Setting volume_clear in
cinder_conf to shred or zero will cause snapshot deletion to fail in OpenStack Grizzly installations on CentOS. Rackspace recommends you set volume_clear to none until this issue is resolved in OpenStack.
OpenStack Service Timeouts
OpenStack service timeouts cannot be configured, which makes it possible for an OpenStack client to remain connected to a failed service for a longer period than is desirable. If you cannot wait for the connection to close, you can restart the service that is holding the connection. For example, if the nova compute service has failed, restart it with service nova-compute restart on Ubuntu or service openstack-nova-compute restart on CentOS.
The following issues have been resolved in Rackspace Private Cloud v 4.0 and v 4.1.2.
An issue with MySQL replication that was caused by logging has been resolved. (Issue #327)
An issue that prevented successful HA Glance replication has been resolved. (Issue #328)
Cookie issues associated with the admin user were resolved in the Grizzly release of OpenStack.
Issues with intermittent collectd failures with monitoring processes or after performing a failover have been resolved, that these failures should no longer occur.
An issue that caused Nova, Cinder, and Glance APIs to attempt to connect to Keystone on an invalid IP has been resolved. (Issue #368 and #369)
Issues with OpenStack Ubuntu and KVM where a kernel version of 3.2.n was required for Ubuntu 12.04 and 12.04.1 have been resolved. This issue was related to Ubuntu bug #1029430.
Instance VNC in the Horizon dashboard now works correctly in environments with HA Infrastructure nodes.
© 2015 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