Chapter 5. Deployment Scenario 1: Basic Environment

The object of this deployment scenario is to create a basic Red Hat Enterprise Linux OpenStack Platform environment using the following specifications:
  • Three nodes:
    • One Controller node
    • Two Compute nodes
  • Nova networking
  • Three networks:
    • A network for the installer's provisioning network (This example uses
    • A network for OpenStack services (This example uses
    • A network for external access (This example uses
  • Local Controller storage for Glance
  • Local Controller storage for Cinder

5.1. Discovering Hosts for a Basic Environment

The basic environment scenario requires three hosts to provision as Red Hat Enterprise Linux OpenStack Platform nodes. The installer initially discovers these hosts through a PXE-based discovery service. Users run a PXE boot on their bare metal hosts over the provisioning subnet (e.g. The installer automatically includes them in the list of available hosts for provisioning.

Procedure 5.1. Adding a Host via Discovery

  1. Start the host and elect to start over the network from the boot options menu. This starts the host using the PXE service the installer provides.
  2. Select Foreman Discovery from the PXE boot options menu. The host starts into the Foreman Discovery screen and is automatically registered in the installer.
    The Foreman Discovery screen

    Figure 5.1. The Foreman Discovery Screen

  3. Log in to the user interface and confirm that the host has been registered:
    1. Click HostsDiscovered hosts.
    2. Click the name of the newly registered host to open the details page for the host, and review the details.
      The discovered host details page

      Figure 5.2. The Discovered Host Details Page

The host is automatically included in the list of unassigned hosts when you assign hosts to a deployment. The host is also automatically added to the discovery environment, which is the default Puppet environment for discovered hosts. This environment acts as a holding area that identifies hosts that have not yet been provisioned.


All network interfaces on the discovered host are active. However, DNS is only active on the interface the installer defines as the primary network interface. Make sure to use the provisioning network for the primary network interface when provisioning your host. Alternatively, set the foreman.url and foreman.ip parameters for each host before provisioning.