Procedure 3.2. Preparing an Installation Medium

1. Go to https://access.redhat.com, and log in to the Red Hat Customer Portal using your customer account details.
2. Click Downloads in the menu bar.
3. Click Red Hat Enterprise Linux to access the product download page.
4. Click RHEL 7.2 Binary DVD.
5. Install the Apache web server on the machine on which to host the installation medium:

   # yum install httpd

6. Start the httpd service, and ensure it starts on boot:
   • On Red Hat Enterprise Linux 6:

     # service httpd start
     # chkconfig httpd on

   • On Red Hat Enterprise Linux 7:

     # systemctl start httpd.service

7. In the root web server directory, create a directory in which to store the files for the installation medium:

   # mkdir /var/www/html/[directory_name]

8. Create a temporary directory into which to mount the ISO file:

   # mkdir /RHEL7

9. Mount the ISO file in the temporary directory:

   # mount -t iso9660 -o loop rhel-server-7.2-x86_64-dvd.iso /RHEL7

10. Copy the contents of the temporary directory to the directory in which to store the files for the installation medium:

    # cp -dpR /RHEL7/* /var/www/html/[directory_name]

11. Unmount the ISO file:

    # umount /RHEL7

12. Remove the temporary directory in which you mounted the ISO file:

    # rmdir /RHEL7

Procedure 3.3. Preparing an Installation Medium using NFS

1. Go to https://access.redhat.com, and log in to the Red Hat Customer Portal using your customer account details.
2. Click Downloads in the menu bar.
3. Click Red Hat Enterprise Linux to access the product download page.
4. Click RHEL 7.2 Binary DVD.
5. Install the nfs-utils package:

   # yum install nfs-utils

6. Create a directory to host the installation medium:

   # mkdir /[directory_name]

7. Add the newly created directory to the /etc/exports file:

   /[directory_name]      *(rw)

8. Export the directory:

   # exportfs -r

9. Start the nfs and rpcbind services, and ensure they start on boot:
   • On Red Hat Enterprise Linux 6:

     # service nfs start
     # service rpcbind start
     # chkconfig nfs on
     # chkconfig rpcbind on

   • On Red Hat Enterprise Linux 7:

     # systemctl start nfs.service
     # systemctl start rpcbind.service
     # systemctl enable nfs.service
     # systemctl enable rpcbind.service

10. Create a temporary directory into which to mount the ISO file:

    # mkdir /RHEL7

11. Mount the ISO file in the temporary directory:

    # mount -t iso9660 -o loop rhel-server-7.2-x86_64-dvd.iso /RHEL7

12. Copy the contents of the temporary directory to the directory in which to store the files for the installation medium:

    # cp -dpR /RHEL7/* /[directory_name]

13. Unmount the ISO file:

    # umount /RHEL7

14. Remove the temporary directory in which you mounted the ISO file:

    # rmdir /RHEL7

Procedure 4.3. Creating an Installation Media Entry

1. From the title bar in the main screen of the user interface, click Hosts → Installation Media.
   ⁠

   

   Figure 4.3. The Installation Media Menu Entry

2. Click New Medium.
3. In the Name text field, enter a name to represent the installation media entry in the user interface.
4. In the Path text field, enter the path of a URL or an NFS share containing the installation tree. The following variables can be used in the path to represent multiple different system architectures and versions:

   $arch

   The system architecture, for example x86_64.

   $version

   The operating system version, for example 7.2.

   $major

   The operating system major version, for example 7.

   $minor

   The operating system minor version, for example 0.

   ⁠

   Example 4.1. HTTP Path

   http://download.example.com/rhel/$version/Server/$arch/os/
   ⁠

   Example 4.2. NFS Path

   nfs://download.example.com:/rhel/$version/Server/$arch/os/
5. Select Red Hat from the Operating system family list.
6. Click Submit.

Procedure 4.4. Specifying the Installation Media Entry for Provisioning

1. From the title bar in the main screen of the user interface, click Configure → Host groups.
2. Click the base_RedHat_7 host group.
3. Click the Operating System tab.
4. Select an installation media entry from the Media list.
5. Click Submit.

Procedure 4.5. Removing an Installation Media Entry

1. From the title bar in the main screen of the user interface, click Hosts → Installation Media to open the Installation Media page.
2. Click the Delete button that corresponds to the installation media entry to delete.
3. Click OK when prompted.

Procedure 4.6. Creating an Operating System Entry

1. Click Hosts → Operating systems.
2. Click New Operating system.
   ⁠

   

   Figure 4.4. The New Operating System Page

3. Configure general operating system details:
   1. In the Name text field, enter a name to represent the operating system entry in the Red Hat Enterprise Linux OpenStack Platform Installer.
   2. In the Major version, enter the number corresponding to the major version of the operating system.
   3. In the Minor version, enter the number corresponding to the minor version of the operating system.
   4. In the Description text field, enter a description to represent the operating system entry in the Red Hat Enterprise Linux OpenStack Platform Installer.
   5. From the OS Family drop-down menu, select the operating system family to which the operating system belongs.
   6. In the Architectures section, select the check boxes for the architectures that the operating system entry can provision.
4. Configure the partition tables that the operating system entry can access:
   1. Click the Partition table tab.
   2. In the All items list, click the name of a partition table entry to move that partition table entry to the Selected items list.
5. Configure the installation media that the operating system entry can access:
   1. Click the Installation media tab.
   2. In the All items list, click the name of an installation media entry to move that installation media entry to the Selected items list.
6. Click Submit.

Procedure 4.7. Updating the Values of Operating System Entry Parameters

1. Click Hosts → Operating systems.
2. Click RedHat 7.2 to open the details page for the Red Hat Enterprise Linux 7.2 operating system entry.
3. Click the Parameters tab.
4. Update the values of the parameters using the text fields for each parameter.
5. Click Submit.

Procedure 4.8. Removing an Operating System Entry

1. Click Hosts → Operating systems.
2. Click the Delete button for the operating system entry to delete.
3. Click OK when prompted.

Procedure 4.9. Creating a Provisioning Template

1. From the title bar in the main screen of the user interface, click Hosts → Provisioning templates.
2. Click New Template.
3. Configure general provisioning template details:
   1. Enter a name for the provisioning template in the Name field.
   2. Enter the body of the provisioning template in the Template editor text area.
   3. Enter a comment describing the creation of the provisioning template in the Audit Comment field.
4. Configure the provisioning template type:
   1. Click the Type tab.
   2. Select Snippet to designate the provisioning template as a snippet. A snippet is not a standalone provisioning template, but a part of a provisioning template that can be inserted into other provisioning templates.
   3. If you did not select the Snippet check box, select the type of the provisioning template from the Type list:
      • PXELinux: A PXELinux template.
      • PXEGrub: A PXEGrub template.
      • iPXE: An iPXE template.
      • Provision: The main provisioning template, such as a kickstart file for Red Hat Enterprise Linux systems.
      • finish: A post-installation script such as that specified in a kickstart file for Red Hat Enterprise Linux systems.
      • script: A generic script that can be run during the provisioning process, such as that specified in a kickstart file for Red Hat Enterprise Linux systems.
      • user_data: A user_data block.
      • ZTP: A zero touch provisioning template.
5. Configure the provisioning template associations:
   1. Click the Associations tab.
   2. From the All items list in the Applicable Operating Systems section, click the name of an operating system entry to move that operating system entry to the Selected items list and make the provisioning template available to that operating system entry.
   3. Optionally, click Add combination and select a host group from the Host Group list or an environment from the Environment list to make the provisioning template available to the specified combination of host groups and environments.
6. Click Submit.

Procedure 4.10. Locking a Provisioning Template

1. From the title bar in the main screen of the user interface, click Hosts → Provisioning templates.
2. Click the disclosure arrow next to the Clone button for the provisioning template.
3. Click Lock.
   ⁠

   

   Figure 4.5. The Lock button

4. Click OK when prompted.

Procedure 4.11. Removing a Provisioning Template

1. From the title bar in the main screen of the user interface, click Hosts → Provisioning templates.
2. If the provisioning template is locked, you must first unlock it:
   1. Click the disclosure arrow next to the Clone button for the provisioning template.
   2. Click Unlock and click OK when prompted.
      ⁠

      

      Figure 4.6. The Unlock button

3. Click the disclosure arrow next to the Clone button.
4. Click Delete and click OK when prompted.

Procedure 4.12. Creating a Partition Table Entry

1. Click Hosts → Partition tables.
2. Click New Partition Table.
3. In the Name text field, enter a name to represent the partition table in the user interface.
4. In the Layout text area, enter the layout for the disk partition:
   ⁠

   Example 4.3. Red Hat Enterprise Linux Partition Table

   zerombr
   clearpart --all --initlabel
   autopart

   Note

   The format of the layout must match that for the intended operating system to which the partition table is applied. For Red Hat Enterprise Linux 6.6 and Red Hat Enterprise Linux 7.2, the layout must match that of a kickstart file.
5. From the Os family drop-down menu, select the operating system family to which the partition table applies.
6. Click Submit

Procedure 4.13. Removing a Partition Table Entry

1. Click Hosts → Partition tables.
2. Click the Delete button for the partition table entry to delete.
3. Click OK when prompted.

Procedure 4.14. Creating a Subnet

1. From the title bar in the main screen of the user interface, click Infrastructure → Subnets.
2. Click New Subnet.
3. Configure general subnet details:
   1. Enter a name for the subnet in the Name field.
   2. Enter the network address of the subnet in the Network address field.
   3. Enter the network mask for the subnet in the Network mask field.
   4. Enter the address of a gateway in the Gateway address field.
   5. Enter the address of the primary DNS server in the Primary DNS server field.
   6. Enter the address of the secondary DNS server, if any, in the Secondary DNS server field.
   7. Select the IP address management source from the IPAM list. If the subnet contains a DHCP server, select DHCP. If no DHCP capability exists on the subnet, select Internal DB and the Installer manages the IP address assignment and records IP addresses in its internal database. Select None for no IPAM management.
   8. Optionally, enter the start of the IP address range that the installer can auto-suggest for hosts in the Start of IP range field.
   9. Optionally, enter the end of the IP address range that the installer can auto-suggest for hosts in the End of IP range field.
   10. Optionally, enter the ID of a VLAN for the subnet.
   11. Select the default boot mode for interfaces assigned to the subnet from the Boot mode list. This sets the boot protocol for client network interfaces. Select DHCP to use the DHCP protocol or Static to manually assign IP address either manually through the host's network interface settings or using the Installer's IPAM Internal Database option.
4. Configure domain membership:
   1. Click the Domains tab.
   2. Select the check box for all domains of which the subnet is a member.
5. Click the Capsules tab to view the capsule settings. A capsule acts as a proxy for certain Installer services, such as DHCP, TFTP, and DNS.
   The Capsule settings are only required for the default subnet. This is because the Installer uses this subnet for host provisioning and deployment of Red Hat OpenStack Platform services. Any new subnets added to the Installer do not require Capsule settings.
6. Click Submit.

Procedure 4.15. Removing a Subnet

1. From the title bar in the main screen of the user interface, click Infrastructure → Subnets.
2. Click the Delete button for the subnet to delete.
3. Click OK when prompted.

Procedure 4.16. Adding a User

1. Click Administer → Users.
2. Click the New User button to open the new user window.
   ⁠

   

   Figure 4.7. The New User Window

3. In the Username text field, enter the user name by which the user logs in to the user interface.
4. In the First name and Surname text fields, enter the real first name and surname of the user.
5. In the Email address text field, enter an email address by which the user can be contacted.
6. From the Language drop-down menu, select the language by which the user interface is displayed to the user.
7. Set a password for the user:
   1. From the Authorized by drop-down menu, select the directory by which the user will be authenticated.
   2. Enter an initial password for the user in the Password text field and again in the Verify text field.
8. Click Submit.

Procedure 4.17. Removing a User

1. Click Administer → Users.
2. Click the Delete button for the user to delete.
3. Click OK when prompted.

Procedure 4.18. Adding a User Group

1. Click Administer → User Groups.
2. Click the New User Group button.
   ⁠

   

   Figure 4.8. The New User Group Window

3. In the Name text field, enter a name by which to identify the user group in the user interface.
4. From the list of check boxes in the User Groups section, select the check boxes to include the corresponding user groups in the new user group.
5. From the list of check boxes in the Users section, select the check boxes to include the corresponding users in the new user group.
6. Click the Roles tab.
7. Select the Admin check box to grant administrator privileges to the users in the user group.
8. From the list of roles in the All items list, click the name of a role to apply that role to the user group.
9. Click Submit.

Procedure 4.19. Removing a User Group

1. Click Administer → Users.
2. Click the Delete button for the user group to delete.
3. Click OK when prompted.

Procedure 4.20. Creating a Role

1. Click Administer → Roles.
2. Click New Role.
   ⁠

   

   Figure 4.9. The New Role Window

3. In the Name text field, enter a name by which to identify the role in the user interface.
4. Click Submit.

Procedure 4.21. Adding Permissions to a Role

1. Click Administer → Roles.
2. Click New Role.
3. From the Filters and permissions list for the role to edit, click Add permission to open the New Filter page.
   ⁠

   

   Figure 4.10. The New Filter Page

4. From the Resource type list, select the resource type to edit.
5. From the list of permissions in the All items list, select the permissions to add to the role.
6. Optionally, clear the Unlimited? check box and use the Search text field to specify a filter using search syntax.
7. Click Submit.

Procedure 4.22. Removing Permissions from a Role

1. Click Administer → Roles.
2. Click the Filters and permissions list for the role to edit to open the Filters page.
3. From the Edit list for the permission to remove, click Delete.
4. Click OK when prompted.

Procedure 4.23. Removing a Role

1. Click Administer → Roles.
2. From the Filters and permissions list for the role to remove, click Delete.
3. Click OK when prompted.

Procedure 5.1. Adding a Host via Discovery

1. Start the host, and elect to start over the network from the boot options menu to start the host using the PXE service that 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 user interface.
   ⁠

   

   Figure 5.1. The Foreman Discovery Screen

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

      

      Figure 5.2. The Discovered Host Details Page

Procedure 6.1. Creating a Deployment

1. Click OpenStack Installer → New deployment.
2. Configure deployment settings:
   ⁠

   

   Figure 6.2. The Deployment Settings step

   1. Enter a name for the deployment in the Name field.
   2. Enter a description in the Description field.
   3. Select either Controller / Compute or High Availability Controllers / Compute in the High Availability section.
   4. Select either Neutron Networking or Nova Network in the Networking section.
   5. Select either RabbitMQ or Qpid as the message broker in the Messaging Provider section.

      Note

      As of Red Hat Enterprise Linux OpenStack Platform 5, RabbitMQ replaces QPid as the default (and recommended) message broker.
   6. Ensure Red Hat Enterprise Linux OpenStack Platform 5 with RHEL 7 is selected in the Platform section.
   7. 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 Verify fields to set the same password for all services.
   8. 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.
   9. Click Next.
3. Configure network traffic:
   ⁠

   

   Figure 6.3. The Network Configuration step

   1. Drag and drop the available network traffic types into the section for a subnet.
   2. Create new subnets if you require a new subnet to which to assign a network traffic type:
      1. Click New Subnet.
      2. Enter a name to represent the subnet in the user interface in the Name field.
      3. Select External DHCP or No existing DHCP from the DHCP server list.
         Setting DHCP server to External DHCP means an external DHCP server exists on the subnet and the Installer sets the boot mode of clients on this subnet to use DHCP.
         Setting DHCP server to No existing DHCP means no DHCP server exists on the subnet and the Installer assigns static IP addresses to clients on the subnet. These static IP addresses are recorded in the Installer's database, which gives the Installer a DHCP-like capability. If you select No Existing DHCP and the subnet is to carry the Public API network traffic type, you must enter the address of a machine that can act as a gateway in the Gateway field. If you select No existing DHCP, you can also specify the IP Range Start and the IP Range End.
      4. Enter the network address in the Network Address field. This address must be in CIDR notation. For example, XX.XX.XX.0/24.
      5. Optionally, enter a VLAN ID for the subnet in the VLAN field.
      6. Click Create Subnet.
   3. Click Next.

   Note

   By default, all network traffic types except External is assigned to the default subnet. Because the External network traffic type is required and cannot be assigned to the same subnet as other network traffic types, you must create a dedicated subnet for this network traffic type. You can then drag and drop network traffic types to subnets as required, or to the Available Network Traffic Types section to disable optional network traffic types.
4. In the Services Overview step, review the list of services to be provisioned, and click Next.
   ⁠

   

   Figure 6.4. The Services Overview step

5. Configure service options:
   ⁠

   

   Figure 6.5. The Services Configuration step

   • Neutron

     Options for this service are only available if you selected Neutron Networking in the Deployment Settings step.
     1. Select a Tenant Network Type.
     2. Select a Core Plugin Type.

   • Nova

     Options for this service are only available if you selected Nova Network in the Deployment Settings step.
     1. Select a Tenant Network Type.
     2. Enter a Floating IP range for external network.
     3. Enter a Fixed IP range for tenant networks.

   • Glance

     1. Select a driver backend from the Choose Driver Backend radio boxes.

   • Cinder

     1. Select one or more driver backends from the Choose Driver Backend check boxes.
6. Click Submit.

Procedure 6.2. Editing a Deployment

1. Click OpenStack Installer → Deployments to open the OpenStack Deployments page.
2. Click the name of a deployment to open the details page for that deployment.
3. Click the name of the deployment to edit the name, and click Save when complete to make the change persistent.
4. Click the description of the deployment to edit the description, and click Save when complete to make the change persistent.
5. Optionally, click the Revisit Setup Wizard button to open the setup wizard and configure further options such as the messaging broker and the password with which to authenticate services.

Procedure 6.3. Removing a Deployment

1. Click OpenStack Installer → Deployments.
2. Click the Delete button for the deployment to remove.
3. Click OK when prompted.

Procedure 6.4. Assigning Hosts to Deployment Roles

1. Click OpenStack Installer → Deployments.
2. Click the name of the deployment to which to assign hosts to open the details page for that deployment.
   ⁠

   

   Figure 6.6. The deployment details page

3. In the Deployment Roles section, click + for a deployment role to display the Free Hosts section for that deployment role:

   Controller

   Provides key services such as the MySQL database for storing data about your environment, Horizon, Keystone, and Glance.

   Compute

   A host that acts as a hypervisor, providing the processing capabilities required for running virtual machines in the environment. You can add more Compute nodes to your environment at any time by assigning additional hosts to this deployment role and repeating the provisioning process; the installer ignores all hosts that have already been provisioned and provisions only the new host.

   Neutron Networking

   Provides Neutron networking services. This deployment role is only available when you select Neutron networking as the networking back end for your deployment and have selected not to use high availability.

   Ceph Storage Node (OSD)

   A generic Red Hat Enterprise Linux 7.2 host that can be manually configured after deployment to act as a Ceph storage server node. This deployment role is optional.

   Generic RHEL 7

   A generic Red Hat Enterprise Linux 7.2 host that can be manually configured after deployment to provide services not defined by any of the pre-existing deployment roles. This deployment role is optional.

4. Select the check box for a host in the Free Hosts section.
5. Click Assign Hosts to assign the host to the selected deployment role.

Procedure 6.5. Unassigning Hosts from Deployment Roles

1. Click OpenStack Installer → Deployments.
2. Click the name of the deployment from which to unassign hosts to open the details page for that deployment.
   ⁠

   

   Figure 6.7. The Deployment Details Page

3. In the Deployment Roles section, click the assigned hosts ( ) button for a deployment role to display the Assigned Hosts section for that deployment role.
4. Select the check box for a host in the Assigned Hosts section.
5. Click Unassign Hosts to unassign the host from the selected deployment role.

Procedure 6.6. Configuring Networking on a Host

1. Click OpenStack Installer → Deployments.
2. Click the name of a deployment to open the details page for that deployment.
3. Click the Hosts tab.
4. Click the Assigned sub-tab.
5. Select the check box for a host and click Configure Networks.
6. Drag and drop subnets between the sections for network interfaces to change the network traffic carried by those interfaces.
   ⁠

   

   Figure 6.8. The Configure Networks Screen

7. Optionally, configure a bond between two network interfaces:
   1. Click the bonding button for a network interface and click the name of a network interface to bond the two network interfaces.
   2. Select the bonding mode from the Bonding Mode list.
8. Click Done.

Procedure 6.7. Configuring Fencing on High-Availability Nodes

1. From the title bar in the main screen of the user interface, click Hosts → All hosts.
2. Click the name of the host to configure.
3. Click Edit.
4. Click the Fencing tab.
   ⁠

   

   Figure 6.9. The Fencing tab

5. If the message Fencing is disabled. To enable, first you need to add a BMC interface to the Host is displayed, you must manually configure the details of a baseboard management controller network interface controller attached to the host:
   1. Click the Network tab.
   2. Click Add Interface.
   3. Select BMC from the Type list.
   4. Enter the MAC address for the network interface controller in the MAC address field.
   5. Click the Fencing tab.
6. Select Enable Fencing.
7. Select IPMI from the Type list.
8. Enter the IP address of the fencing device in the IP Address field.
9. Enter the name of the IPMI user on the fencing device in the Username field.
10. Enter the password by which to authenticate the above user in the Password field.
11. Select Expose Lanplus to use the lanplus interface.
12. If you selected the Expose Lanplus check box, enter any options in the Lanplus Options field.
13. Click Submit.

Procedure 6.8. Viewing the Configuration of a Deployment

1. Click OpenStack Installer → Deployments.
2. Click the name of a deployment.
3. Click Advanced Configuration.
4. Click the name of a service to view the parameters for that service.
5. Click Back to Deployment to return to the deployment details page when finished.

1. Click OpenStack Installer → Deployments.
2. Click the name of a deployment.
3. Click Advanced Configuration.
4. Click Edit.
5. Click the name of a service to view the parameters for that service.
6. Enter a new value for the parameter in the text field for that parameter.
7. Click Apply

Procedure 6.9. Importing a Deployment Configuration

1. Click OpenStack Installer → Deployments.
2. Click the name of a deployment to open the details page for that deployment.
3. Click Advanced Configuration.
4. Click Import to open the Import Config pop-up window.
5. Click Browse and search your local system for the configuration file to upload.
6. Click Import Config.

Procedure 6.10. Exporting a Deployment Configuration

1. Click OpenStack Installer → Deployments.
2. Click the name of a deployment.
3. Click Advanced Configuration.
4. Click Export from the Configuration list.

Procedure 6.11. Provisioning Red Hat Enterprise Linux OpenStack Platform

1. Click OpenStack Installer → Deployments.
2. Click the name of the deployment to provision.
   ⁠

   

   Figure 6.10. The deployment details page

3. Click Deploy to open the deployment confirmation screen.
   ⁠

   

   Figure 6.11. The deployment confirmation screen

4. Click Deploy.

Procedure 6.12. Retrieving Service Details

1. Click OpenStack Installer → Deployments.
2. Click the name of a deployment you have provisioned.
3. Review the details of the deployment.
   ⁠

   

   Figure 6.12. The service details page

4. Optionally, click the Access all details button to display the All details window, which displays a list of the passwords for all services in your environment.

Procedure 7.1. Changing the Report Interval

1. From the main title bar, click Administer → Settings.
2. Click the Puppet tab.
3. Click the edit icon next to the value of the puppet_interval setting.
4. Enter a new report interval in minutes.
5. Click Save.

Procedure 7.2. Deleting Reports

1. Log in to the machine on which the user interface is installed as the root user.
2. Delete all reports more than [days] number of days old:

   # foreman-rake reports:expire days=[days]

Procedure 7.3. Deleting a Report

1. From the title bar in the main screen of the user interface, click Monitor → Reports.
2. Click Delete for the report to delete.
3. Click OK when prompted.