Chapter 2. Requirements

This chapter outlines the main requirements for setting up an environment to provision Red Hat Enterprise Linux OpenStack Platform using the Red Hat Enterprise Linux OpenStack Platform installer, including the requirements for setting up and accessing the installer itself, and the hardware requirements for hosts that installer provisions for OpenStack services.

2.1. RHEL OpenStack Platform Installer System Requirements

A typical deployment of the Red Hat Enterprise Linux OpenStack Platform installer requires:
  • A machine running Red Hat Enterprise Linux 7 to host the installer and its web-based user interface. For this machine, 8 GB of memory is recommended; a minimum of 4 GB memory is required.

    Important

    The installer's host machine requires a fully qualified domain name that satisfies the following criteria:
    • It must be a part of the same domain the installer uses for provisioning. This is because provisioned hosts communicate with the installer using the fully qualified domain name.
    • The domain must be associated with the network the installer uses for provisioning. This is because the installer's DNS service assigns domain names to provisioned hosts.
    • It must not conflict with any existing domains. This is to avoid conflicts in name resolution.
  • A private network accessible to physical machines or virtual machines. The installer deploys the Red Hat Enterprise Linux OpenStack Platform components through this network. Disable any services such as DHCP, DNS, and PXE on this network. The installer uses its own DHCP, DNS, and PXE services and must avoid any conflicts with existing services.

    Important

    The installer's bare metal discovery service requires the network interface connected to this private network have a native (untagged/default) VLAN configuration. The installer does not detect VLAN-tagged interfaces.

    Important

    Network switches must support fallback if configuring the installer interface used for PXE in a network bond. Provisioning fails if bonding is activated on the switches themselves due to the lack of bond during PXE negotiation. If the switches used do not support a fallback mode, a dedicated non-bonding provisioning interface should be used.
  • A machine that is a member of the private network and that can act as a router or gateway to an external network. The machine that hosts the installer can perform this function if required. See Section 3.5, “Configuring a Gateway” for information on how to configure this machine to act as a gateway.
  • Your Customer Portal account details, which you use to subscribe your hosts to the relevant content channels, both for the installer and the deployed hosts. The main details needed include your user name, password, the ID of pools to attach, the names of channels to enable, and the details of any HTTP proxy you might use to connect to the internet.