6.2. Creating a Deployment for an Advanced Environment

This process creates a deployment for provisioning an advanced RHEL OpenStack Platform environment. This process runs through the relevant options for this environment. For more information on the options available for configuring networking and services, see Appendix B, New Deployment Settings.
To start the creation of a new deployment, navigate to OpenStack InstallerNew deployment.
The Deployment Settings page requires some initial settings for your advanced environment.
  1. Enter a name for the deployment in the Name field. For example, Advanced Deployment.
  2. Enter a description in the Description field.
  3. Select Neutron Networking in the Networking section.
  4. Select RabbitMQ as the message broker in the Messaging Provider section.
  5. Ensure Red Hat Enterprise Linux OpenStack Platform 6 with RHEL 7 is selected in the Platform section.
  6. Select Generate random password for each service in the Service Password section to generate a random password for each service, or select Use single password for all services and enter a password in the Password and Confirm fields to set the same password for all services.
  7. Optionally, enter a list of custom repositories in the Custom repos text area. Multiple custom repositories must be added on separate lines, and each custom repository must take the form of a base URL.
  8. Click Next.
The Deployment Settings step

Figure 6.3. The Deployment Settings step

The Network Configuration page maps OpenStack's network traffic types to the subnets in your environments.

Procedure 6.2. Configuring Network Traffic

  1. Drag the External network traffic type onto the External subnet (e.g. created in Section 4.2.1, “Creating an External Subnet”.
  2. Drag the Tenant, Management, Cluster Management, Admin API, Public API, Storage, and Storage Clustering network traffic types onto the OpenStack Services subnet (e.g. created in Section 4.2.2, “Creating an OpenStack Services Subnet”.
  3. Leave the Provisioning/PXE network traffic type in the default subnet (e.g.
  4. Click Next.
The Network Configuration step

Figure 6.4. The Network Configuration step


By default, all network traffic types except External and Tenant are assigned to the default subnet. The External network traffic type cannot be assigned to the same subnet as other network traffic types and requires a dedicated subnet for this network traffic type. Drag and drop network traffic types to subnets as required, or to the Available Network Traffic Types box to disable optional network traffic types.
The Services Overview page provides an opportunity to review the list of services to be provisioned. Click Next to move to the next page.
The Services Overview step

Figure 6.5. The Services Overview step

The Services Configuration page provides options to configure OpenStack's Neutron, Glance, and Cinder services.
  1. Accept the default options for Neutron configuration.
    Neutron configuration options

    Figure 6.6. Neutron Configuration Options


    By default, the L2 population option in the Neutron tab is not selected. Due to an incompatibility in L3 high availability and L2 population, you must ensure this option remains deselected in environments with more than one controller such as this scenario. However, in environments with one controller node where OpenStack networking is used, you must manually select this option.
  2. Select the following options for Glance:
    1. Select NFS from the Choose Driver Backend section. This displays a field for the NFS URI. Enter this URI in the following form:
      For example:
    Glance configuration options

    Figure 6.7. Glance configuration options

  3. Select the following options for Cinder
    1. Check NFS in the Choose Driver Backend section. This displays a field for the NFS URI. Enter this URI in the following form:
      For example:
    Cinder configuration options

    Figure 6.8. Cinder configuration options

  4. Click Submit.
This completes the deployment creation process. The next step in the creation of the advanced environment involves assigning the discovered hosts to specific deployment roles.