• Sales: 1-800-961-2888
  • Support: 1-800-961-4454

Installing Rackspace Private Cloud Software on a Single Device with Virtual Machines

NOTE: This documentation is for the Rackspace Private Cloud Software v. 3.0 with OpenCenter. Other v. 3.0 documentation can be found on the Archived Versions page. Documentation for the newest version of Rackspace Private Cloud Software can be found in the Getting Started section.


This chapter discusses the process for installing Rackspace Private Cloud Software in a configuration where OpenCenter server and Chef server are installed on VMs hosted on a single device.

Prepare the Device and VMs

The device should have Ubuntu 12.04, CentOS 6.3, or RHEL 6.3 or 6.4 installed on it and should meet the following requirements:

  • 32 GB RAM
  • 144 GB disk space
  • Single or dual socket CPU with a hex core (for a total of 6-12 cores)

You will need to install KVM on the device and create two guest VMs. Refer to the KVM documentation for detailed instructions for:

  • installing and configuring KVM
  • creating a guest disk image
  • installing a guest operating system
  • running a newly-installed guest

Create two guests and install Ubuntu 12.04, CentOS 6.3, or RHEL 6.3 or 6.4 on them. Ensure that the OS is up to date on the devices.

When the installation process is complete, you will have a host device with two guest VMs, as depicted in the following diagram. In this example, the device is named host-controller, and the VMs are opencenter-vm and chef-vm.

Create the OpenCenter Environment

You can install OpenCenter with the package or script method, as documented in "Installing Rackspace Private Cloud Software". Perform the installation in the following stages.

  1. Log into one of the two VMs and install OpenCenter Server.
  2. Install the OpenCenter UI on the same VM as the OpenCenter server.
  3. Log into the second VM and install OpenCenter Agent.
  4. Log into the host device and install OpenCenter Agent.
  5. Log in to the UI or use the CLI to view the available nodes. The second VM and the host device should appear as available unprovisioned nodes, as in the following example:
    $ opencentercli node list
    id |name            |task |adventure |attrs |facts              |
    1  |workspace       |None |None      |{...} |{u'backends': ...  |
    2  |unprovisioned   |None |None      |{...} |{u'parent_id': ... |
    3  |support         |None |None      |{...} |{u'parent_id': ... |
    4  |chef-vm         |None |None      |{...} |{u'parent_id': ... |
    5  |host-controller |None |None      |{...} |{u'parent_id': ... |
  6. With the operator GUI or the CLI on the OpenCenter server, deploy Chef server on the second VM. (In this example, that would be chef-vm.)
  7. When the Chef server is successfully deployed, create a Nova cluster in the OpenCenter environment.
  8. When the Nova cluster is ready, assign the host device (in this example, host-controller) to the Nova cluster as a Controller node.

You now have an OpenCenter environment deployed on a single device. You can now install the OpenCenter agent on other devices or VMs in the network to create Compute nodes and proceed with using your OpenStack cluster.

© 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