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

Installation Prerequisites for Rackspace Private Cloud 2.0

NOTE: This documentation is for the Rackspace Private Cloud Software v. 2.0 ISO. Documentation for the newest version of Rackspace Private Cloud Software can be found in the Getting Started section.


This chapter discusses the networking prerequisites for installing Rackspace Private Cloud Software.

Software Requirements

Rackspace Private Cloud Software reformats the node on which it is installed and does not have any specific software requirements.

WARNING! During the installation process, the node will be completely reformatted. Do not install Rackspace Private Cloud Software on a node that has any other data on it.

Network Requirements

Internet access is required to complete the installation, so ensure that the node IP addresses that you use have internet access to download the installation files. Proxies are not currently supported in the Rackspace Private Cloud configuration, but will be addressed in a future release.

Rackspace Private Cloud Software v 1.0 supports single and dual NIC installations and comes with a network bridge defined and configured in advance.

Rackspace Private Cloud Software creates a FlatDHCP network, in which nova-network software is installed and configured on each server that is running nova-compute. Further conceptual information about Flat DHCP networking is available in the OpenStack Compute Administration Manual. Refer to the following topics:

Instance Access Considerations

By default, the instances that you create can only be publicly accessed via NAT by assigning floating IP addresses to them. Before you assign a floating IP address to an instance, you must have a pool of addresses to choose from. Your network security team must provision an address range and assign it to your environment. These addresses need to be publicly accessible. Floating IP addresses are not specified during the installation process; once the controller node is operational, you can add them with the nova-manage floating create --ip_range command. Refer to "Managing Floating IP Addresses".

NAT access to instances on the cloud

You can also make the instances accessible to other hosts in the network by default by configuring the cloud with a network DMZ. The network DMZ range cannot be the same as the nova fixed network range. Specifying a DMZ enables NAT-free network traffic between the virtual machine instances and resources outside of the nova fixed network. For example, if the nova fixed network is and you specify a DMZ of, any devices or hosts in that range will be able to communicate with the instances on the nova fixed network.

To use the DMZ, you must have at least two NICs on the deployment servers. One NIC must be dedicated to the VM instances.

DMZ access to instances on the cloud

NIC Considerations

Rackspace Private Cloud Software v 1.0 supports single- and dual-NIC installations and comes with a network bridge defined and configured in advance.rax-fo keep-with-next During the installation process, you will be prompted to supply NIC information, and if you have more than one NIC, you must designate one as public and one as private. There are several considerations of which you should be aware.

OpenStack compute requires NIC ordering to be the same on all hosts in the nova network. For example, when configuring the controller, you may choose eth1 as your public NIC and eth0 as private. When you configure the compute nodes, you must configure their NICs in exactly the same way.

You cannot mix single-NIC and multi-NIC configurations. If you configure the controller with one NIC, all associated compute nodes must also be single-NIC.
If your server has more than one network card, you cannot perform a single-NIC installation, and will be required to select a public and private NIC during the installation process.

Proxy Considerations

Rackspace Private Cloud Software v 2.0 allows you to enter a proxy gateway address during the installation process. When a proxy is enabled, all internet traffic going to and from the cluster will pass through the proxy, including the Rackspace Private Cloud installation files. After you define the type of node that you want to install, you will be prompted to enter the proxy address. If you do not have one, you can press Enter to leave it blank and skip the step.

Proxy settings can only be configured during the installation process. If you need to change the settings, it is recommended that you re-run the ISO.

Preparing For the Installation

Before you begin, have the following networking information prepared and available:

  • The NIC address or addresses that the nova fixed network will use. If you have more than one NIC address, you must designate one as public and one as private.
  • The IP address that you want to assign to each controller and compute node. This can be an IPv4 address in the format xxx.xxx.xxx.xxx or a CIDR range, and it must be able to access the internet to download installation files.
  • Network subnet mask.
  • Network default gateway. This address is usually a xxx.xxx.xxx.1 address.
  • The IP address of your proxy gateway, if you have one.
  • The address of your nameserver.
  • The server host name. You may be able to define this yourself, or you may need to contact your network administrator for the name.
  • Fully-qualified domain name for the host.
  • The address for the nova fixed network, in CIDR format. Instances created in the OpenStack cluster will have IP addresses in this range.
  • Optional DMZ network address and the gateway address in the fixed network that is on the router that routes to the DMZ. The DMZ network address is in CIDR format.
  • A password for an admin OpenStack user.
  • A password for a non-admin OpenStack user, as well as a username if you do not want to use the default of demo.
  • A full real name, username, and password for an operating system user.

You must also ensure that the server is configured to boot from an ISO. You can monitor the progress of the installation from a console directly connected to the server or via a remote management tool, such as Dell DRAC or HP Ilo. Finally, you should ensure that the server has virtualization support enabled in the BIOS.

© 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