quickstart cloud installer 1.0 quickstart cloud installer guide · 2016. 10. 7. · the quickstart...

Red Hat Cloud Suite DocumentationTeam

QuickStart Cloud Installer 1.0QuickStart Cloud Installer Guide

Installing the QuickStart Cloud Installer and Deploying Red Hat CloudProducts

QuickStart Cloud Installer 1.0 QuickStart Cloud Installer Guide

Installing the QuickStart Cloud Installer and Deploying Red Hat CloudProducts

Red Hat Cloud Suite Documentation [email protected]

Legal Notice

Copyright © 2016 Red Hat, Inc.

The text of and illustrations in this document are licensed by Red Hat under a Creative CommonsAttribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA isavailable athttp://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you mustprovide the URL for the original version.

Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert,Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinitylogo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and othercountries.

Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.

Java ® is a registered trademark of Oracle and/or its affiliates.

XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United Statesand/or other countries.

MySQL ® is a registered trademark of MySQL AB in the United States, the European Union andother countries.

Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related toor endorsed by the official Joyent Node.js open source or commercial project.

The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marksor trademarks/service marks of the OpenStack Foundation, in the United States and other countriesand are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed orsponsored by the OpenStack Foundation, or the OpenStack community.

All other trademarks are the property of their respective owners.

AbstractThis guide covers how to install and configure the QuickStart Cloud Installer, and use the QuickStartCloud Installer to deploy cloud products such as Red Hat Virtualization, Red Hat OpenStackPlatform, Red Hat CloudForms, and OpenShift Enterprise.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents

CHAPTER 1. INTRODUCTION1.1. INTRODUCTION1.2. SYSTEM REQUIREMENTS1.3. LIMITATIONS1.4. GIVING FEEDBACK

CHAPTER 2. INSTALLING THE QUICKSTART CLOUD INSTALLER

CHAPTER 3. DEPLOYING RED HAT VIRTUALIZATION, RED HAT CLOUDFORMS, AND OPENSHIFTENTERPRISE

3.1. PREPARE3.2. DEPLOY3.3. VERIFY

CHAPTER 4. DEPLOYING RED HAT OPENSTACK PLATFORM AND RED HAT CLOUDFORMS4.1. PREPARE4.2. DEPLOY4.3. VERIFY

CHAPTER 5. TROUBLESHOOTING AND LOGS5.1. KNOWN ISSUES AND TROUBLESHOOTING TIPS5.2. LOG FILES

CHAPTER 6. NEXT STEPS6.1. REGISTERING THE QUICKSTART CLOUD INSTALLER TO ITSELF6.2. REGISTERING RED HAT CLOUDFORMS TO THE QUICKSTART CLOUD INSTALLER6.3. UPDATING CA CERTIFICATES

APPENDIX A. AVAILABLE SCRIPTS

APPENDIX B. PRODUCT DOCUMENTATION

APPENDIX C. NETWORKING ARCHITECTURE

33467

8

14141926

29293645

474748

50505050

51

52

53

Table of Contents

1


2

CHAPTER 1. INTRODUCTION

1.1. INTRODUCTION

The QuickStart Cloud Installer (QCI) provides a web-based graphical user interface to provisioncloud products. The set of products that can be deployed by the QuickStart Cloud Installer includes:Red Hat Virtualization (RHV), Red Hat OpenStack Platform (RHOSP), Red Hat CloudForms, andOpenShift Enterprise (OSE). You can deploy a single product or multiple products in onedeployment. For introductory information on each product, see the Product Guide. See the Planningand Engineering Guide to assess which set of products you want to deploy. For example, selectbetween Red Hat Virtualization and Red Hat OpenStack Platform for your private cloudinfrastructure. Select whether you need Red Hat CloudForms to manage your cloud environment. Ifyou have multiple cloud providers, either multiple instances of the same provider or a mix of differentcloud providers, you can use Red Hat CloudForms as a single management tool. Select OpenShiftEnterprise to deploy a container platform that leverages Docker and the Kubernetes clustermanager.

The two common deployment paths are:

Deploy Red Hat Virtualization + Red Hat CloudForms + OpenShift Enterprise:

1. Section 3.1, “Prepare”

2. Section 3.2, “Deploy”

3. Section 3.3, “Verify”

4. Continue with any additional product-specific tasks. See Appendix B, ProductDocumentation.

Deploy Red Hat OpenStack Platform + Red Hat CloudForms:

1. Section 4.1, “Prepare”

2. Section 4.2, “Deploy”

3. Section 4.3, “Verify”

4. Continue with any additional product-specific tasks. See Appendix B, ProductDocumentation.

Table 1.1. Supported Product Versions

Application Version Description

QuickStart Cloud Installer (RedHat Satellite)

6.2 A single installer for allsupported components.


3

https://access.redhat.com/documentation/en/red-hat-cloud-suite/version-0/product-guide/

https://access.redhat.com/documentation/en/red-hat-cloud-suite/0/planning-and-engineering-guide/chapter-1-introduction-to-red-hat-cloud-suite#choosing_between_red_hat_enterprise_virtualization_and_red_hat_openstack_platform

Red Hat Virtualization 4.0 A traditional private cloudprovider for relatively staticenvironments.

Red Hat OpenStack Platform 8 A private cloud provider fordynamic and scalable workloads.

Red Hat CloudForms 4.1 A management tool for cloudproviders. Deployed as a virtualmachine on the chosen provider.

OpenShift Enterprise 3.2 A container platform forenterprise applicationdevelopment and deployment.Deployed as a virtual machineon the chosen provider.

Application Version Description

1.2. SYSTEM REQUIREMENTS

This section outlines the minimum and recommended hardware requirements, additional hardwarerecommendations, and the required subscriptions.

Table 1.2. Minimum Hardware Requirements

Systems Disk Space Memory CPUs

QuickStart CloudInstaller (Red HatSatellite)

210GB 16GB RAM 2

Red Hat VirtualizationManager

25GB 4GB RAM 2

Red Hat Virtualizationhypervisors

10GB 40GB RAM(Calculation alsoincludes Red HatCloudForms andOpenShift Enterprise.)

12 (Calculation alsoincludes Red HatCloudForms andOpenShift Enterprise.)


4

Red Hat Virtualization(self-hosted engine)

70GB 48GB RAM(Calculation alsoincludes Red HatCloudForms andOpenShift Enterprise.)

12 (Calculation alsoincludes Red HatCloudForms andOpenShift Enterprise.)

Red Hat OpenStackPlatform Undercloud

40GB 16GB RAM 8

Red Hat OpenStackPlatform OvercloudController Node

100GB 32GB RAM 4

Red Hat OpenStackPlatform OvercloudCompute Node

100GB 24GB RAM(Calculation alsoincludes Red HatCloudForms.)

8 (Calculation alsoincludes Red HatCloudForms.)


Table 1.3. Recommended Hardware Requirements


QuickStart CloudInstaller (Red HatSatellite)

250GB 16GB RAM 4

Red Hat VirtualizationManager

50GB 16GB RAM 4

Red Hat Virtualizationhypervisors

100GB 40GB RAM 12

Red Hat Virtualization(self-hosted engine)

70GB 48GB RAM 12


5

Red Hat OpenStackPlatform Undercloud

100GB 16GB RAM 8

Red Hat OpenStackPlatform OvercloudController Node

100GB 32GB RAM 8

Red Hat OpenStackPlatform OvercloudCompute Node

100GB 24GB RAM 8


Additional hardware recommendations can be found in the individual product documentation:

Red Hat OpenStack Platform maximum limits

Red Hat OpenStack Platform minimum requirements

Red Hat Virtualization Manager requirements

Red Hat Virtualization hypervisor requirements

Red Hat CloudForms requirements

OpenShift Enterprise requirements

Red Hat Satellite requirements

Table 1.4. Subscriptions

Subscription Name Description

Red Hat Cloud Infrastructure with SmartManagement

A subscription to deploy Red Hat Virtualization,Red Hat OpenStack Platform, and Red HatCloudForms.

Red Hat Cloud Suite with Smart Management A subscription to deploy Red Hat Virtualization,Red Hat OpenStack Platform, Red HatCloudForms, and OpenShift Enterprise.

Red Hat Satellite Required to optionally register the QuickStartCloud Installer machine.


6

https://access.redhat.com/articles/1436373

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html/Director_Installation_and_Usage/chap-Requirements.html

https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/installation-guide/#Red_Hat_Enterprise_Virtualization_Manager_Requirements

https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/installation-guide/#sect-Hypervisor_Requirements

https://access.redhat.com/node/1548913

https://access.redhat.com/documentation/en/openshift-enterprise/version-3.2/installation-and-configuration/#system-requirements

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/single/installation-guide/#preparing_your_environment_for_installation

1.3. LIMITATIONS

QuickStart Cloud Installer (Red Hat Satellite 6.2)

Isolating networks is not supported.

Capsule servers are not supported.

Concurrent deployments are not supported. You must wait until the deployment has completedbefore beginning another deployment.

The current code limits the number of deployments per QuickStart Cloud Installer instance to255.

Only AMD64 and Intel 64 are supported.

Red Hat Virtualization 4.0

NFS and Gluster storage are the only supported storage types.

Only Red Hat Enterprise Linux hosts are supported hypervisors. Red Hat Virtualization Host(RHVH), a minimal operating system based on Red Hat Enterprise Linux, is not supported.

Only one network interface (ovirtmgmt bridge) is supported.

Power management for hosts is not supported.

The default maximum transmission unit (MTU) value is set to 1500 and cannot be changed.

Adding multiple VLANs to a single network interface is not supported.

Network bonding is not supported.

An ISO domain is not created by default and is not required for the initial setup.

For a self-hosted engine RHV deployment, changing the default data center name and clustername is not supported.

Red Hat OpenStack Platform 8

Local storage and a separate existing Ceph Storage cluster is supported.

Isolating networks is not supported.

High availability is not supported.

OpenShift Enterprise is currently not supported on Red Hat OpenStack Platform.

1.4. GIVING FEEDBACK

If you have any feedback on the QuickStart Cloud Installer, please email [email protected].


7

mailto:[email protected]

CHAPTER 2. INSTALLING THE QUICKSTART CLOUDINSTALLER

The QuickStart Cloud Installer is used to provision cloud environments and allows you to managesystem lifecycles, errata updates, and subscriptions. You can install the QuickStart Cloud Installerby downloading the QuickStart Cloud Installer ISO file or subscribing a Red Hat Enterprise Linux 7system to the required entitlements to obtain the required RPM packages. The QuickStart CloudInstaller ISO file eases the installation process by including all the required packages anddependencies in an image. The RPM installation method allows you to customize your Red HatEnterprise Linux 7 system if required.

Prerequisites:

Prepare a Red Hat Enterprise Linux 7 host machine that meets the QuickStart Cloud Installerrequirements listed in Section 1.2, “System Requirements”. For proof-of-concept installations, avirtual machine can be used. For production environments, you must deploy the QuickStartCloud Installer on a physical machine.

Ensure a minimum of one network interface is available, and ensure the network is enabledautomatically at boot time. Other than the DHCP service the QuickStart Cloud Installer provides,no DHCP or any other provisioning services should be running on this network to avoid IPconflicts. The RPM installation method requires a network interface to have access to externalnetworks such as the Red Hat Content Delivery Network to download RPM packages. You canuse the same network interface or optionally configure a dedicated network for downloadingcontent from the Red Hat Content Delivery Network.

Note

If additional DHCP is required to be running on other interfaces on the QuickStart CloudInstaller, the PEERDNS option for those interfaces must be set to no to prevent DHCPfrom updating the /etc/resolv.conf file on the QuickStart Cloud Installer. The QuickstartCloud Installer uses the /etc/resolv.conf file to resolve the host names of thedeployments.

1. Obtain the QuickStart Cloud Installer packages by downloading the ISO file or using RedHat Subscription Manager to subscribe your system:

a. Download the QuickStart Cloud Installer ISO file fromhttps://access.redhat.com/downloads/content/268/ver=1/rhel---7/1/x86_64/product-software, and create a bootable media device.


8

https://access.redhat.com/downloads/content/268/ver=1/rhel---7/1/x86_64/product-software

i. Launch the ISO, and select Install Red Hat QuickStart Cloud Installer1.0.

ii. The installation process starts with installing a pre-configured Red HatEnterprise Linux 7 system. Set the root password before the installationreaches 100%. Optionally create additional users.

iii. Once the base operating system installation is complete, the systemreboots. Log in as the root user with the password you set in the previousstep. A terminal window opens automatically and initializes the QuickStartCloud Installer.

b. Alternatively, obtain the RPM packages using Red Hat Subscription Manager.

i. Register your system with the Content Delivery Network, entering yourCustomer Portal user name and password when prompted:

# subscription-manager register

ii. Find the Red Hat Cloud Suite or Red Hat Cloud Infrastructuresubscription pool and note down the pool ID:


9

# subscription-manager list --available

iii. Use the pool ID located in the previous step to attach the entitlement to thesystem:

# subscription-manager attach --pool=pool_id

Note

To find out what subscriptions are currently attached, run:

# subscription-manager list --consumed

To list all enabled repositories, run:

# yum repolist

iv. Disable all existing repositories:

# subscription-manager repos --disable=*

v. Enable the required repositories:

# subscription-manager repos --enable=rhel-7-server-rpms# subscription-manager repos --enable=rhel-server-rhscl-7-rpms# subscription-manager repos --enable=rhel-7-server-satellite-6.2-rpms# subscription-manager repos --enable=qci-1.0-for-rhel-7-rpms

vi. Ensure all packages are up to date. Install the qci package anddependencies.

# yum update# yum install qci

Note

Reboot the machine if any kernel related packages have beenupdated.

vii. Run fusor-installer and set the admin password for the Red HatQuickStart Cloud Installer WebUI (Red Hat Satellite Portal):

# fusor-installer --foreman-admin-password=changeme


10

Note

Note that fusor-installer is different from satellite-installer --scenario Fusor.

2. Configure the networking details for the QuickStart Cloud Installer machine:

a. The network interface (option 2) may need to be changed to the provisioningnetwork if more than one network interface is available.

b. Enter 3 (Hostname), and press Enter. Enter a host name, and press Enter. TheForeman URL is auto-generated using the host name and is resolvable by theQuickStart Cloud Installer.

c. Enter 4 (IP address), and press Enter. Enter the IP address (for example: 192.168.155.10) for the QuickStart Cloud Installer machine, and press Enter.

d. Enter 5 (Network mask), and press Enter. Enter the netmask value (for example: 255.255.255.0 or /24), and press Enter.

e. The host gateway, DHCP network address, network range, and gateway will beauto-filled based on the network values that you have filled in so far. Verify theauto-generated fields, and change them if required.

Note

The IP address range specified must cover twice the number of hosts youintend to provision as the range is split between discovered hosts andmanaged hosts. Discovered hosts are converted to managed hostsduring provisioning.

Host gateway | 192.168.155.1DHCP network address | 192.168.155.0 DHCP range start | 192.168.155.11 DHCP range end | 192.168.155.254 DHCP gateway | 192.168.155.1

f. Enter 11 (DNS forwarder), and press Enter. Enter the DNS forwarder IP address(for example: 192.168.155.1), and press Enter. This is normally the same as thehost gateway.

g. Enter 13 (NTP sync host), and press Enter. Enter the NTP clock to use for timesynchronization, and press Enter.

h. Optionally register the QuickStart Cloud Installer to the Customer Portal to receiveupdates. Enter 15 (Register Host For Updates), press Enter, and enter your RedHat login and password.


11

i. Review the networking configuration. To change a value, enter the associatednumber and press Enter. Type in the desired value and press Enter. To proceedwith the configuration and start the installation script, enter 1, and press Enter.

Note

If the installer process is canceled or interrupted, it can be restarted fromthe command line:

# fusor-installer --foreman-admin-password=changeme

3. After the installation script has completed successfully, double-click the Red HatQuickStart Cloud Installer WebUI Firefox icon, and log into the user interface with theusername admin and a password. The default password is changeme for the ISOinstallation method. It may be necessary to trust an untrusted connection to access the site.

Note

If you are using the RPM installation method and a graphical user interface is notinstalled, access the Red Hat QuickStart Cloud Installer WebUI from a machinethat has a graphical user interface installed. Set the DNS to resolve to the DNS ofthe QuickStart Cloud Installer machine, and type https://<sat6-fqdn>/r/#/deployments/new/start in the browser address bar.

4. If the password for the admin user is changeme, change the password by going to the RedHat QuickStart Cloud Installer WebUI. Click Admin User, then My account, enter a newpassword, and click Submit.

5. Optionally register the QuickStart Cloud Installer to receive updates. See Section 6.1,“Registering the QuickStart Cloud Installer to Itself”.


12

Note

If your QuickStart Cloud Installer has access to external networks such as the Red HatContent Delivery Network, you can proceed to deploy products. See Chapter 3, DeployingRed Hat Virtualization, Red Hat CloudForms, and OpenShift Enterprise or Chapter 4,Deploying Red Hat Openstack Platform and Red Hat CloudForms.

If your QuickStart Cloud Installer is in a disconnected environment (with restricted internetaccess), you can configure Inter-Satellite Synchronization (ISS) to allow your QuickStartCloud Installer to synchronize content from another Red Hat Satellite instance which hasaccess to the Red Hat Content Delivery Network. See the Red Hat Satellite 6 InstallationGuide and Synchronizing Content Between Satellite Servers in the Red Hat Satellite 6Content Management Guide for more information on setting up ISS.


13

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/single/installation-guide

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/single/content-management-guide#Using_ISS

CHAPTER 3. DEPLOYING RED HAT VIRTUALIZATION, REDHAT CLOUDFORMS, AND OPENSHIFT ENTERPRISE

3.1. PREPARE

3.1.1. Overview

Ensure that the installation of the QuickStart Cloud Installer is complete before proceeding with thefollowing tasks.

To prepare for a Red Hat Virtualization deployment, you need to:

Plan for networking.

Prepare nodes to be used for the Red Hat Virtualization installation, and ensure the requirednetwork interfaces are automatically enabled on all nodes so the nodes can be successfullydiscovered.

Note

For proof-of-concept installations, virtual machines can be used. For productionenvironments, all the deployments except Red Hat CloudForms and OpenShiftEnterprise must be deployed on physical machines.

Set up shared NFS storage or Gluster storage for Red Hat Virtualization.

Create a subscription management application and attach the required subscriptions for thedeployment.

3.1.2. How to Plan for Networking

The networks required:

A provisioning network that is used by the QuickStart Cloud Installer to discover and provisionhosts. No DHCP or any other provisioning services should be running on this network. It is alsoused to synchronize content from the Red Hat Content Delivery Network. You can optionallyconfigure a dedicated network for downloading content from the Red Hat Content DeliveryNetwork.

Note

If DHCP is running on other interfaces in the environment, the PEERDNS option forthose interfaces must be set to no to prevent the service from updating the/etc/resolv.conf file on the QuickStart Cloud Installer.

A virtual bridge network is automatically created by the Manager and is used by virtual machinesto connect to the provisioning network and any external network.

An example networking diagram:


14

3.1.3. How to Create Red Hat Virtualization Nodes

For a standard Red Hat Virtualization (RHV) deployment, a minimum of two hosts are required.Prepare one host machine that meets the Red Hat Virtualization Manager requirements listed inSection 1.2, “System Requirements”. Prepare one host machine that meets the Red HatVirtualization hypervisor requirements listed in Section 1.2, “System Requirements”. Optionallycreate more nodes to have multiple hypervisors in your environment.

For a self-hosted engine RHV deployment, a minimum of one host is required. The Manager willbe created as a virtual machine hosted on the hypervisor. Prepare a host machine that meetsthe Red Hat Virtualization hypervisor (for self-hosted engine) requirements listed in Section 1.2,“System Requirements”. Optionally create more nodes to have multiple hypervisors in yourenvironment.

Note

Change the host name to a desired host name. If you need to change the host name afteryou have initiated the RHV deployment, you must exclude the domain name from the hostname to avoid deployment errors. See BZ#1367142 for more information.

Proceed to the next section to enable the nodes to be discovered by the QuickStart Cloud Installer.

3.1.4. How to Enable Node Discovery

For nodes to be discovered by the QuickStart Cloud Installer, ensure the QuickStart Cloud Installeris up and running and has one NIC for the provisioning network.

CHAPTER 3. DEPLOYING RED HAT VIRTUALIZATION, RED HAT CLOUDFORMS, AND OPENSHIFT ENTERPRISE

15

https://bugzilla.redhat.com/show_bug.cgi?id=1367142

1. In the host’s BIOS configuration, change the default boot option to boot over the network.

2. Start the host, and select Foreman Discovery from the PXE menu. As part of the process,the host gets the PXE image from the QuickStart Cloud Installer and boots the discoveryimage. The host is registered as a discovered host and can be used in a deployment.

3. In the console, you will see the Foreman Discovery process starts automatically. Once yousee the SUCCESS status, the host has been installed and discovered successfully by theQuickStart Cloud Installer machine.

4. You can also verify that the host has been successfully discovered through the Red HatQuickStart Cloud Installer WebUI. Log in to the QuickStart Cloud Installer as admin with theupdated password. If you did not change the default password, the password is changeme.

5. Click Hosts → Discovered Hosts to see the discovered nodes.


16

3.1.5. How to Set Up Shared Storage

NFS and Gluster storage are currently the only supported storage types for a QuickStart CloudInstaller Red Hat Virtualization deployment.

Table 3.1. Required Storage Domains

Product Number of StorageDomains Required

Description

Red Hat Virtualization(Hypervisor + Engine)

2 A data domain is required to host thevirtual machine data in the RHVenvironment. An export domain is used asa temporary storage device in RHV forimporting the Red Hat CloudFormsappliance and the OpenShift Enterpriseappliance.

Red Hat Virtualization (Self-Hosted Engine)

3 A self-hosted engine data domain isrequired to host the Manager virtualmachine data. A data domain is requiredto host the regular virtual machine data inthe RHV environment. An export domainis used as a temporary storage device inRHV for importing the Red HatCloudForms appliance and the OpenShiftEnterprise appliance.

Red Hat CloudForms N/A The Red Hat CloudForms appliance isimported to RHV using RHV’s ISOdomain.


17

OpenShift Enterprise 1 A domain is required for the OSE dockerregistry.

Product Number of StorageDomains Required

Description

3.1.5.1. How to Set Up Shared NFS Storage

For evaluation purposes, you can use the fusor-local-nfs-setup script to speed up the process. Forproduction environments, create the storage shares manually so you can tailor them to therequirements of your environment.

Note

The NFS shares need to be empty and not include data from any previous Red HatVirtualization deployments. Existing data will cause the deployment to fail.

Using the fusor-local-nfs-setup script

1. Install nfs-utils if the package is not already installed:

# yum install nfs-utils

2. On the QuickStart Cloud Installer machine, run the fusor-local-nfs-setup script to set upNFS shares.

# fusor-local-nfs-setup

NFS shares for RHV deployments have been created at:/var/lib/exports/vms/var/lib/exports/exports/var/lib/exports/registryvol/var/lib/exports/self_hosted

3. Note down the storage domain mount points relevant to your deployment. The information isrequired during the deployment.

192.168.155.10:/var/lib/exports/vms (Required by a standard RHV or a self-hostedengine RHV.)

192.168.155.10:/var/lib/exports/exports (Required for RHV to import appliances andcreate virtual machines.)

192.168.155.10:/var/lib/exports/registryvol (Required by OpenShift Enterprise.)

192.168.155.10:/var/lib/exports/self_hosted (Required by a self-hosted engine RHV.)

Creating NFS shares manually


18

See Preparing NFS Storage to create the required domains. An ISO domain stores ISO files (orlogical CDs) used to install and boot operating systems and applications for virtual machines. It is notrequired for the initial setup.

3.1.5.2. How to Set Up Shared Gluster Storage

See the Red Hat Gluster Storage Installation Guide for more information on setting up Glusterstorage.

Update the DNS configuration or /etc/hosts of the QuickStart Cloud Installer to ensure that thename of the Gluster server is resolvable by the QuickStart Cloud Installer. If the host name is notresolvable, a deployment using Gluster storage will fail. See BZ#1375292 for more information onhow to update a DNS entry.

3.1.6. How to Create a Subscription Management Application

A subscription management application groups the required subscriptions for a deployment. Thefollowing procedure shows you how to create a subscription management application so you caneasily select it during a deployment. Note that if your QuickStart Cloud Installer has access to theinternet, you can optionally skip this section and create a subscription management applicationduring the deployment. Both methods are supported.

1. Log into the Customer Portal with your account details.

2. At the top of the page, click Subscriptions.

3. Under Subscription Management Applications, click Satellite.

4. Click Register a Satellite.

5. Enter a name and set the version to Satellite 6.2.

6. Click Register.

7. On the new Satellite entry page, click Attach a subscription.

8. Select Red Hat Cloud Infrastructure with Smart Management or Red Hat Cloud Suitewith Smart Management, and enter the appropriate quantity. The quantity depends on thenumber of products you want to deploy. Click ATTACH SELECTED.

The required subscription management application has been created, and will be available forselection during the deployment.

Proceed to the next section to start a Red Hat Virtualization, Red Hat CloudForms, and OpenShiftEnterprise deployment.

3.2. DEPLOY

1. In the Red Hat QuickStart Cloud Installer WebUI (Red Hat Satellite Portal), selectQuickStart Cloud Installer → New Deployment from the top menu.

2. Select the Red Hat Virtualization, Red Hat CloudForms, and OpenShift Enterprise boxes,and click Select.


19

https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/administration-guide/#Preparing_NFS_Storage

https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html-single/Installation_Guide/index.html


Note

This procedure presents all the available products you can install on Red HatVirtualization in one single deployment. If there is a product you do not want toinstall, do not select the product and skip the relevant steps in this procedure.

3. Configure the Satellite component:

a. Enter a name, and optionally enter a description and a universal password. ClickNext.

b. Select Immediately to publish updates immediately when an update is available.Click Next. Alternatively, select After manually publishing them, click NewEnvironment Path, and enter an environment name. The Label is used as aninternal ID and is identical to the environment name. Optionally enter a description,and click Submit. Click Next.


20

Note

If you select Immediately, the content view for the deployment is in thedefault Library environment, and updates will be available to thedeployment as soon as they are released. If you would like more controlon when a deployment can receive updates, you need to select Aftermanually publishing them, and create a new environment path (forexample: Library > Production). This way, you will be able topromote the content from the default Library environment to a Productionenvironment manually. For more information, see Creating an ApplicationLife Cycle in the Red Hat Satellite 6 Content Management Guide.

c. Optionally select the Enable Red Hat Insights check box. Click Next. Red HatInsights collects and analyzes your system data and provides recommendedperformance and security action items. After the deployment is complete, you canclick Red Hat Insights > Systems to view the monitored status.

4. Configure the Red Hat Virtualization (RHV) component. You can install either a standardRHV (Hypervisor + engine) or a self-hosted engine RHV (Self-hosted).

Note

The Hypervisor + engine option allows the Red Hat Virtualization Manager andthe hypervisor to be installed on different machines. The Self-hosted optionallows the Manager to be installed as a virtual machine on the hypervisor; onlyone machine is required for the initial setup. The advantage of deploying a self-hosted engine with two or more hypervisors is that, if the host running theManager virtual machine goes into maintenance mode, or fails unexpectedly, thevirtual machine will be migrated automatically to another host in the environment.


21

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/single/content-management-guide#Creating_an_Application_Life_Cycle

a. Select Hypervisor + engine or Self-hosted, and click Next.

b. Skip this step for Self-hosted. Select the host to be used as the Red HatVirtualization Manager, also known as the engine. The selected host will default to aname of its MAC address. Click the Host Name field and update the host name asnecessary (for example: engine.example.com). Click Next.

c. Select the host to be used as the hypervisor. The selected host will default to aname of its MAC address. Click the Host Name field and update the host name asnecessary. Optionally click Edit Naming Scheme to change the host namingscheme. Click Next.

d. Set the root password for the hypervisor(s). Set the Engine Admin password forthe Red Hat Virtualization Administration Portal. The password fields areautomatically filled in if a universal password was set during step 3. The passwordsrequire a minimum of 8 characters. The remaining fields can be left as default. ClickNext.


22

e. Enter the NFS data domain and export domain details. For a self-hosted engine, athird domain is required to host the Manager virtual machine. Click Next.

5. Configure the OpenShift component:

a. Select one master node and one worker node.

b. Select the additional storage required for Docker containers on each worker node.

c. View the environment summary and optionally click Custom Edit to edit the systemdetails. Click Next.

d. Enter the Docker registry storage domain details.

e. Leave the user account as default and set a password. The password fields areautomatically filled in if a universal password was set during step 3.


23

f. Set a subdomain name, and optionally select to deploy a sample application as partof the deployment. The subdomain name appears as part of the application URL.

6. Configure the CloudForms component:

a. Select Install CloudForms on Red Hat Virtualization. Click Next.

b. Set the root password for the Red Hat CloudForms virtual machine, the admin userpassword for the Red Hat CloudForms Portal, and the Database password for thedatabase account. The password fields are automatically filled in if a universalpassword was set during step 3. The password requires a minimum of 8characters. Click Next.

7. Configure subscriptions:

a. Enter your Red Hat login and password, and click Next.


24

Important

Your Red Hat login credentials are only saved temporarily in the browsersession, so you will need to click Deploy soon after you have created thedeployment. If the browser session expires, you will need to delete thedeployment and create a new one. This is a known issue and is trackedin BZ#1352968.

b. Select an existing subscription management application. Alternatively, create a newone by clicking New Subscription Management Application, and enter a name.Click Next.

c. Attach subscriptions. If you selected an existing subscription managementapplication in the previous step, check that the required subscription is alreadyattached and click Next to skip this step. If you created a new subscriptionmanagement application, you need to add the required subscription by selectingone or more subscriptions in your account and entering the quantity to consume.

d. Check that the required subscriptions for the deployment are listed. Click Next.

8. Review the installation configuration. Click on any items you want to revisit and update. You

can click the to view the passwords set. Click Deploy.

The installation begins. Click the Details tab to view individual task progress. RPMpackages are downloaded from the Content Delivery Network to the Red Hat Satellitemachine. This may take several hours. The discovered hosts are provisioned with Red HatEnterprise Linux. Puppet will run on the provisioned hosts to install Red Hat Virtualization


25


packages from the QuickStart Cloud Installer machine. Red Hat CloudForms will be createdas a virtual machine hosted in the Red Hat Virtualization environment. When all threeprogress bars are at 100%, the deployment is complete.

9. Click Next to view the Installation Summary. You will see the URLs of the portals toaccess Red Hat Virtualization, OpenShift Enterprise, and Red Hat CloudForms.

Important

The URL uses the fully qualified domain name of the system. If you areconnecting from a machine other than the QuickStart Cloud Installer machine,you will need to configure your DNS to resolve to the DNS of the QuickStart CloudInstaller machine.

3.3. VERIFY

Verify that the components are running and accessible.

1. To verify Red Hat Virtualization:

a. Open the Red Hat Virtualization Administration Portal using the URL shown on theInstallation Summary screen. If you are accessing the portal from a machine otherthan the QuickStart Cloud Installer, ensure that the host name is resolvable byupdating the DNS configuration or /etc/hosts.

b. Log in as admin with the password you set.

c. Verify that the deployed items in the following tabs have a green triangle next tothem:

Data centers

Storage

Virtual machines

Hosts


26

The alert in the Red Hat Virtualization Administration Portal about failing toverify power management for a given host is normal and can be ignored.

Note

To access virtual machines hosted on Red Hat Virtualization using thevirtual machine console, you will need to install the Remote Viewerapplication (virt-viewer) on systems you wish to access from. SeeInstalling Console Components in the Red Hat Virtualization VirtualMachine Management Guide.

2. To verify OpenShift Enterprise:

a. Open the OpenShift Enterprise web console using the URL shown on theInstallation Summary screen. Log in as cloudesuite-install with the passwordyou set. If you deployed a sample application, you can click on the application toview the details.

Note

Click Add to project to create additional applications. Click toopen the OpenShift Enterprise documentation.

b. Alternatively, verify by command line and SSH into the Master node:

# ssh -i /usr/share/foreman/.ssh/openshift/deployment-name/id_rsa master-node-fqdn

c. Verify that the current user is cloudesuite-install:

# oc whoami

d. If you selected to deploy a sample application (for example: Hello World) as part ofthe deployment, verify that the application is available:

# oc get pods

e. Change user to admin:

# oc login -u system:admin

f. Change to the default project:

# oc project default


27

https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/virtual-machine-management-guide#sect-Installing_Console_Components

g. Verify that the registry pod and router pod are running:

# oc get pods

h. View the details of the storage domain for the docker registry:

# oc describe pv registry-volume

3. To verify Red Hat CloudForms:

a. Open the Red Hat CloudForms Portal using the URL shown on the InstallationSummary screen.


c. Select Compute → Infrastructure → Providers in the menu, and verify that theRHV Manager (<project-name>RHV) is listed among the providers.

Note

There are currently no items in the Red Hat CloudForms self-serviceconsole. For more information on using the self-service console, seeIntroduction to the Self Service User Interface Guide.


28

https://access.redhat.com/documentation/en/red-hat-cloudforms/4.1/single/introduction-to-the-self-service-user-interface/

CHAPTER 4. DEPLOYING RED HAT OPENSTACKPLATFORM AND RED HAT CLOUDFORMS

4.1. PREPARE

4.1.1. Overview

Ensure that the installation of the QuickStart Cloud Installer is complete before proceeding with thefollowing tasks.

To prepare for a Red Hat OpenStack Platform deployment, you need to:

Plan for networking, and ensure the required network interfaces are available and automaticallyenabled on boot.

Create one node to install the Red Hat OpenStack Platform Undercloud Installer.

Create two or more nodes to be used as Red Hat OpenStack Platform Overcloud nodes. Aminimum of two is required to get the environment up and running.

Create a subscription management application and attach the required subscriptions for thedeployment.

Optionally prepare a Ceph Storage cluster to be used with the Overcloud.

4.1.2. How to Plan for Networking

The networks required:

A provisioning network that is used by the QuickStart Cloud Installer to discover and provisionhosts. No DHCP or any other provisioning services should be running on this network. It is alsoused to synchronize content from the Red Hat content delivery network. You can optionallyconfigure a dedicated network for downloading content from the Red Hat Content DeliveryNetwork.

Note

If DHCP is running on other interfaces in the environment, the PEERDNS option forthose interfaces must be set to no to prevent the service from updating the/etc/resolv.conf file on the QuickStart Cloud Installer.

An OSP public network that is used by the nodes to communicate externally.

An OSP provisioning network that is used by the Undercloud node to provision Overcloud nodes.No DHCP or any other provisioning services should be running on this network.

A private virtual network (tenant network) used by the instances to connect to the public network.This is created by the Red Hat OpenStack Platform installer automatically.

Overcloud node requirements:

The boot device must have PXE at a higher priority than local drives.

The PXE Network Interface Card (NIC) must be the one connected to the Red Hat OpenStack

CHAPTER 4. DEPLOYING RED HAT OPENSTACK PLATFORM AND RED HAT CLOUDFORMS

29

Platform provisioning network.

An example networking diagram:

4.1.3. How to Install the Red Hat OpenStack Platform Undercloud Installer

1. Prepare a host machine that meets the Red Hat OpenStack Platform Undercloudrequirements listed in Section 1.2, “System Requirements” and the networking requirementsin Section 4.1.2, “How to Plan for Networking”.

2. Obtain the Red Hat OpenStack Platform Undercloud packages by downloading the ISO fileor using Red Hat Subscription Manager to subscribe your system:

a. Download the Red Hat OpenStack Platform Undercloud Installer ISO fromhttps://access.redhat.com/downloads/content/268/ver=1/rhel---7/1/x86_64/product-software, and create a bootable media device.


30

https://access.redhat.com/downloads/content/268/ver=1/rhel---7/1/x86_64/product-software

i. Launch the ISO, and select Install Red Hat OSP Undercloud 8.

ii. The installation process starts with installing a pre-configured Red HatEnterprise Linux 7 system. Set the root password before the installationreaches 100%. Optionally create additional users.

Note

The root password can only be set once in Anaconda. This is aknown issue. You can change the root password as normal afterthe system has booted. See Resetting the Root Password ofRHEL-7/ systemd for more information. Alternatively, re-install theRed Hat OpenStack Platform Undercloud Installer.

iii. After the system reboots, log in as root with the root password you set inthe previous step.

b. Alternatively, obtain the RPM packages using Red Hat Subscription Manager.


31

https://access.redhat.com/solutions/918283

i. Register your system with the Content Delivery Network, entering yourCustomer Portal user name and password when prompted:

# subscription-manager register

ii. Find the Red Hat Cloud Suite or Red Hat Cloud Infrastructuresubscription pool and note down the pool ID:

# subscription-manager list --available

iii. Use the pool ID located in the previous step to attach the entitlement to thesystem:

# subscription-manager attach --pool=pool_id

Note

To find out what subscriptions are currently attached, run:

# subscription-manager list --consumed

To list all enabled repositories, run:

# yum repolist

iv. Disable all existing repositories:

# subscription-manager repos --disable=*

v. Enable the required repositories:

# subscription-manager repos --enable=rhel-7-server-rpms# subscription-manager repos --enable=rhel-7-server-extras-rpms# subscription-manager repos --enable=rhel-7-server-rh-common-rpms# subscription-manager repos --enable=rhel-server-rhscl-7-rpms# subscription-manager repos --enable=rhel-7-server-satellite-6.2-rpms# subscription-manager repos --enable=qci-1.0-for-rhel-7-rpms# subscription-manager repos --enable=rhel-7-server-openstack-8-director-rpms# subscription-manager repos --enable=rhel-7-server-openstack-8-rpms

vi. Ensure all packages are up to date. Install the qci-tripleo package anddependencies.


32

# yum update# yum install qci-tripleo

Note

Reboot the machine if any kernel related packages have beenupdated.

vii. Ensure port 80 is open:

# firewall-cmd --permanent --add-port=80/tcp

viii. Run fusor-undercloud-installer:

# fusor-undercloud-installer

3. Set the FQDN (for example: undercloud.example.com), and press Enter.

net.ipv4.ip_forward = 1Set your resolvable Fully Qualified Domain Name: undercloud.example.com

4. Enter the DNS Nameserver IP address, or accept the default 127.0.0.1 to only resolvehost names locally. Press Enter.

Enter the DNS nameserver to use for the Overcloud: x.x.x.x

5. Select the network interface that is connected to your provisioning network (for example: 1),and press Enter.

1: eth0, MAC Addr: 52:54:00:31:4a:4bPlease select the Network Interface that is connected to your provisioning network [1]:

6. Enter the IP address block (for example: [192.168.150.0/24]), and press Enter.

We require a block of IP Addresses that we can assign on your network.Please specify this block using standard slash notation: [192.168.150.0/24]

7. Enter the IP address of the Red Hat OpenStack Platform Undercloud node (for example: [192.168.150.254]), and press Enter.

Please specify the IP address of the Openstack Director. Be sure that this IP is on the correct subnet and does not interfere with the block given above. [192.168.150.254]

8. Enter the IP Address of the network gateway (for example: [192.168.150.1]), and pressEnter.


33

Please specify the IP Address of the network gateway.This is preferably the router that leads out to the larger network but will default to this machine if not changed,making this machine a critical piece of your OpenStack infrastructure. [192.168.150.1]

9. Set the admin user password for the Undercloud Portal, and press Enter.

Please specify the admin password for this undercloud. When the installation is complete you will be able to log in to this undercloud with user "admin" and this password. If you leave it blank one will be randomly generated, and you can look it up later with "hiera admin_password". [<generate>]

10. Type N to skip configuring the advanced network and password options, and press Enter.

Would you like to specify advanced network and password configuration?(else defaults will be accepted and installation will begin) [y/N] N

The Undercloud installation takes about 20 minutes. The red warning messages in thescreen output can be safely ignored. When you see Installation complete!, proceed to thenext section to deploy two Red Hat OpenStack Platform nodes. You can also verify that theUndercloud has been installed successfully by logging into the Undercloud Portal. Open aweb browser on your host machine, type in the host address, and log in with usernameadmin and the password you set.


34

Note

If the installer process is canceled or interrupted, it can be restarted from thecommand line:

# fusor-undercloud-installer

4.1.4. How to Create Red Hat OpenStack Platform Overcloud Nodes

Prepare a host machine that meets the Red Hat OpenStack Platform Overcloud Node requirementslisted in Section 1.2, “System Requirements”. Only physical hosts that support IPMI drivers aresupported in a production environment. You need at least two nodes to complete a basic Red HatOpenStack Platform deployment. Note down the host name for each node. The information isrequired during the registration step in the deployment procedure.

4.1.5. How to Create a Subscription Management Application

A subscription management application groups the required subscriptions for a deployment. Thefollowing procedure shows you how to create a subscription management application so you caneasily select it during a deployment. Note that if your QuickStart Cloud Installer has access to theinternet, you can optionally skip this section and create a subscription management applicationduring the deployment. Both methods are supported.

1. Log into the Customer Portal with your account details.

2. At the top of the page, click Subscriptions.

3. Under Subscription Management Applications, click Satellite.

4. Click Register a Satellite.

5. Enter a name and set the version to Satellite 6.2.

6. Click Register.

7. On the new Satellite entry page, click Attach a subscription.

8. Select Red Hat Cloud Infrastructure with Smart Management or Red Hat Cloud Suitewith Smart Management, and enter the appropriate quantity. The quantity depends on thenumber of products you want to deploy. Click ATTACH SELECTED.

The required subscription management application has been created, and will be available forselection during the deployment.

4.1.6. How to Create a Ceph Storage Cluster

You can optionally use a Ceph Storage cluster as the storage back-end for your Overcloud. TheCeph Storage cluster needs to be installed and configured on a separate machine other than theQuickStart Cloud Installer and the Red Hat OpenStack Platform Undercloud Installer.

For more information on setting up a Ceph Storage cluster, see Red Hat Ceph Storage InstallationGuide for Red Hat Enterprise Linux.


35

https://access.redhat.com/documentation/en/red-hat-ceph-storage/2/single/installation-guide-for-red-hat-enterprise-linux

For more information on configuring a Ceph Storage cluster for Red Hat OpenStack Platform, seethe following sections:

Configuring the Existing Ceph Storage Cluster

Initializing the Stack User

Enabling Integration with the Existing Ceph Storage Cluster

The following Ceph Storage information is required during the deployment:

Ceph External Mon Host (The IP address of the Monitor node)

Ceph Cluster FSID

Ceph Client Username

Ceph Client Key

Nova RBD Pool Name (The default pool name is vms)

Cinder RBD Pool Name (The default pool name is volumes)

Glance RBD Pool Name (The default pool name is images)

Proceed to the next section to start a Red Hat OpenStack Platform and Red Hat CloudFormsdeployment.

4.2. DEPLOY

1. In the Red Hat QuickStart Cloud Installer WebUI (Red Hat Satellite Portal), selectQuickStart Cloud Installer → New Deployment from the top menu.

2. Select the Red Hat OpenStack Platform and Red Hat CloudForms boxes, and click Select.

3. Configure the Satellite component:


36

https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/single/red-hat-ceph-storage-for-the-overcloud#configuring_the_existing_ceph_storage_cluster

https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/single/red-hat-ceph-storage-for-the-overcloud#initializing_the_stack_user_2

https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/single/red-hat-ceph-storage-for-the-overcloud#enabling_integration_with_the_existing_ceph_storage_cluster

a. Enter a name, and optionally enter a description and a universal password. ClickNext.

b. Select Immediately to publish updates immediately when an update is available.Click Next. Alternatively, select After manually publishing them, click NewEnvironment Path, and enter an environment name. The Label is used as aninternal ID and is identical to the environment name. Optionally enter a description,and click Submit. Click Next.

Note

If you select Immediately, the content view for the deployment is in thedefault Library environment, and updates will be available to thedeployment as soon as they are released. If you would like more controlon when a deployment can receive updates, you need to select Aftermanually publishing them, and create a new environment path (forexample: Library > Production). This way, you will be able topromote the content from the default Library environment to a Productionenvironment manually. For more information, see Creating an ApplicationLife Cycle in the Red Hat Satellite 6 Content Management Guide.

c. Optionally select the Enable Red Hat Insights check box. Click Next. Red HatInsights collects and analyzes your system data and provides recommendedperformance and security action items. After the deployment is complete, you canclick Red Hat Insights > Systems to view the monitored status.


37

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/single/content-management-guide#Creating_an_Application_Life_Cycle

4. Configure the Red Hat OpenStack Platform component:

a. Enter the Undercloud IP (for example: 192.168.150.254), the SSH User (forexample: root), and the SSH Password, and click Detect Undercloud. Click Nextafter you see Undercloud has been successfully detected.

Note

If you have destroyed and recreated the Undercloud virtual machine, butyou are using the same QuickStart Cloud Installer virtual machine, youwill see the error: FINGER PRINT DOES NOT MATCH. To resolve thisissue, on the QuickStart Cloud Installer machine, remove the old keyentry in /usr/share/foreman/.ssh/known_hosts.


38

b. Click Register Nodes to open the Node Registration window.

i. Enter the BMC (baseboard management controller) IP address or the IPaddress of the host that hosts the virtual machines to be provisioned.

ii. For the driver, select IPMI Driver for a bare metal machine or PXE + SSHfor a virtual machine.

iii. Enter the IPMI user or the SSH user (for example: root), and enter thepassword.

iv. Click the Auto-Detect button to enable auto-detection of available nodeson the provided IP address, and click Next to start the auto-detection ofavailable nodes. Alternatively, enter the MAC address(es) of the nodes touse.

Note

The IPMI auto-detection for Dell systems only detects onboardNICs. Since the IPMI interface does not provide informationabout NICs not on the system board, those NICs cannot be auto-detected by the QuickStart Cloud Installer.

v. Select the two nodes you created to be used as Overcloud nodes.

vi. Select the the provisioning network interface for each node.


39

Note

If you are using Virtual Machine Manager for your test instances,locate the MAC address of the provisioning network by selecting

an Overcloud node. Click Open → , and check the NIC forthe provisioning network.

vii. Click Register.


40

viii. Click Next after both nodes have been successfully registered.

c. Click + Assign Role, and select the Compute role. Four roles are available:Compute, Controller, Block Storage (Cinder), and Object Storage (Swift).

d. Click + Assign Role, and select the Controller role.

e. Verify that you have 1 displayed for both the Compute and Controller roles, andclick Next.

f. Configure the Overcloud:

Note

Also see Section 4.1.2, “How to Plan for Networking” for thecorresponding networking diagram.

i. Enter the interface that is connected to your Red Hat OpenStack Platformpublic network. Note that the QuickStart Cloud Installer does not validatethat the interface is available (for example: nic2).

ii. Enter a private network in CIDR format. This can be any network that iscurrently not in use (for example: 192.168.254.0/24).


41

iii. Enter a floating IP network in CIDR format (for example: 192.168.253.0/24) and the floating IP network gateway (for example: 192.168.253.1).

iv. Enter an Admin Password, and click Next. The password fields areautomatically filled in if a universal password was set during step 3.

v. Optionally attach an existing Ceph Storage cluster for your Overcloud.

5. Configure the CloudForms component:

a. Select Install CloudForms on Red Hat OpenStack Platform, and click Next.

b. Set the root password for the Red Hat CloudForms virtual machine and the adminuser password for the Red Hat CloudForms Portal. The password fields areautomatically filled in if a universal password was set during step 3. The passwordrequires a minimum of 8 characters. Click Next.


42

6. Configure subscriptions:

a. Enter your Red Hat login and password, and click Next.

Important

Your Red Hat login credentials are only saved temporarily in the browsersession, so you will need to click Deploy soon after you have created thedeployment. If the browser session expires, you will need to delete thedeployment and create a new one. This is a known issue and is trackedin BZ#1352968.

b. Select an existing subscription management application. Alternatively, create a newone by clicking New Subscription Management Application. Enter a name, andclick Next.

c. Attach subscriptions. If you selected an existing subscription managementapplication in the previous step, check that the required subscription is alreadyattached and click Next to skip this step. If you created a new subscriptionmanagement application, you need to add the required subscription by selectingone or more subscriptions in your account and entering the quantity to consume.


43


d. Check that the required subscriptions for the deployment are listed. Click Next.

7. Review the installation configuration. Click on any items you want to revisit and update. You

can click the to view the passwords set. Click Deploy.

Note

You will see Syncing OpenStack for a minute or two while the QuickStart CloudInstaller is performing validation against the Undercloud instance.

8. After all three progress bars have reached 100%, click Next to view the InstallationSummary. You will see the URLs of the portals to access Red Hat OpenStack Platform andRed Hat CloudForms.


44

Important

Some of the URLs use the fully qualified domain name of the system. If you areconnecting from a machine other than the QuickStart Cloud Installer machine,you will need to configure your DNS to resolve to the DNS of the QuickStart CloudInstaller machine.

4.3. VERIFY

Verify that the components are running and accessible.

1. To verify Red Hat OpenStack Platform:

a. Open the Overcloud Portal using the Overcloud URL shown on the InstallationSummary screen.


c. Verify that you can see the associated Red Hat OpenStack Platform project.

2. To verify Red Hat CloudForms:

a. Open the Red Hat CloudForms Portal using the URL shown on the Installation


45

Summary screen.


c. Select Compute → Clouds → Providers in the menu, and verify that theOvercloud Controller node (<project-name>RHOS) is listed among the providers.

d. Select Compute → Infrastructure → Providers in the menu, and verify that theUndercloud node (<project-name>RHOS-Director) is listed among the providers.

Note

There are currently no items in the Red Hat CloudForms self-serviceconsole. For more information on using the self-service console, seeIntroduction to the Self Service User Interface Guide.


46

https://access.redhat.com/documentation/en/red-hat-cloudforms/4.1/single/introduction-to-the-self-service-user-interface/

CHAPTER 5. TROUBLESHOOTING AND LOGS

5.1. KNOWN ISSUES AND TROUBLESHOOTING TIPS

Content synchronization errors

If you click View Content Sync Status and see an error message related to package downloadfailures, see Synchronizing Red Hat Repositories in the Red Hat Satellite 6 Installation Guide tosynchronize the content manually. After content synchronization is complete, perform a newdeployment. If the failure persists, contact the Red Hat Global Support Team.

Connection aborted BadStatusLine Error

See the workaround in https://access.redhat.com/articles/2321771.

The progress bar for the RHV deployment hangs at 95.5%

When deploying Red Hat Virtualization and Red Hat CloudForms, if the progress bar for the RedHat Virtualization deployment hangs at 95.5%, it indicates an error with configuring the datacenter for Red Hat Virtualization. See /var/log/messages for error logs. NFS-related issues arethe most common reason for a deployment failure. Verify the following items:

The NFS shares are set up with the appropriate permissions. The shares should be ownedby user vdsm and group kvm with the permission set to 0755.

Firewall rules are not preventing hosts from mounting the NFS shares.

The NFS shares should not have existing data. Ensure the shares do not have content from aprevious Red Hat Virtualization deployment.

If you see the following error message, it means that the NFS service failed to restart whenthe engine-setup script was first run. On the Manager machine, rerun the engine-setupscript manually, and the deployment will continue. Expect 30 to 45 minutes of time for the restof the configuration to complete before you see the progress bars updated.

/Stage[main]/Ovirt::Engine::Setup/Exec[engine-setup]/returns) [ ERROR ] Failed to execute stage 'Closing up': Command '/sbin/service' failed to execute

FINGERPRINT DOES NOT MATCH Error for Red Hat OpenStack Platform

This can happen if you have previously destroyed an Undercloud instance and recreated it, butare using the same QuickStart Cloud Installer machine. To resolve this issue, remove the oldkey entry in the /usr/share/foreman/.ssh/known_hosts file on the QuickStart Cloud Installermachine.

Connection Errors with Red Hat OpenStack Platform

For deployments done on virtual machines, ensure you can ping and manually SSH into theUndercloud from the QuickStart Cloud Installer machine. If you cannot, restart the libvirtdservice.

# systemctl restart libvirtd

The underlying cause is that sometimes firewall rules are not populated with the virtual networks.Restarting libvirtd helps to regenerate the firewall rules.


47

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/single/content-management-guide#Importing_Red_Hat_Content-Synchronizing_Red_Hat_Repositories

https://access.redhat.com/articles/2321771

BZ#1252551 Error: A plugin is needed to display this content

Connecting to the Red Hat CloudForms Portal using the Firefox browser on the QuickStart CloudInstaller machine fails if the Adobe Flash plug-in is not installed. Seehttps://access.redhat.com/solutions/20920 for more information on installing the Adobe Flashplug-in.

Internet Explorer 11 is currently not a supported browser version.

BZ#1258615 Validation failed: IP address has already been taken

If you reuse a host from a previous deployment and run into the IP address has already beentaken error, you can run hammer host list to see if a host in the current deployment got the sameIP as one host from a previous deployment. To work around this issue, delete the old host byrunning:

# hammer host delete --id <ID>

BZ#1344910 Error: Failed to destroy a compute RHV instance xxx.example.com: Cannotremove VM. VM is running.

Deleting a virtual machine on Red Hat Virtualization (RHV) that was deployed through a computeresource returns the Cannot remove VM. VM is running error. To work around the issue, loginto the RHV Administration Portal and stop the virtual machine. Then, from the Red Hat SatellitePortal, click Hosts → All hosts. Select the virtual machine, click Delete, and click OK.

BZ#1367762 RHV Deployment fails at 82.1%

Some RHV deployments fail at 82.1% due to errors related to the Red Hat Insights plug-in. Towork around the issue, wait for some time, and then try resuming the failed task by navigating toRed Hat QuickStart Cloud Installer WebUI → Monitor → Tasks, and click Resume. In/var/log/messages, you will see errors similar to:

puppet-agent[4587]: (/Stage[main]/Access_insights_client/Exec[/usr/bin/redhat-access-insights --register]/returns) change from not run to 0 failed: /usr/bin/redhat-access-insights --register returned 1 instead of one of [0]

BZ#1367584 Warning about RAM is overcommitted.

If you are deploying OpenShift Enterprise on Red Hat Virtualization (RHV) and Red HatCloudForms on Red Hat OpenStack Platform (RHOSP) in a single deployment, when configuringthe OpenShift component, the QuickStart Cloud Installer calculates the available resourcesbased on RHV and does not take RHOSP into account, and may provide a false warning tousers about lack of resources.

If the Red Hat OpenStack Platform Undercloud is installed on a virtual machine running on a RedHat Enterprise Linux 7.2 or older system, the introspection and deployment boot process issusceptible to an issue with iPXE which causes it to fail. See the workaround inhttps://bugzilla.redhat.com/show_bug.cgi?id=1302420#c8.

BZ#1324023 Running memtest86 on libvirt virtual machines fails.

5.2. LOG FILES


48


https://access.redhat.com/solutions/20920





https://bugzilla.redhat.com/show_bug.cgi?id=1302420#c8


Table 5.1. QuickStart Cloud Installer Log Files

Component Log File Description

QuickStart Cloud Installerinstallation

/var/log/fusor-installer/fusor-installer.log Installation-related logs anderrors.

QuickStart Cloud Installerdeployments

/var/log/messages/var/log/foreman/production.log/var/log/foreman/deployments/<deployment_name>

Deployment-related logs anderrors.

Foreman Proxy /var/log/foreman-proxy/proxy.log Information about servicesassociated with theQuickStart Cloud Installer,such as DHCP, TFTP, andPuppet.

Subscriptions /var/log/candlepin/candlepin.log /var/log/foreman/deployments/<deployment_name>

Messages and errors relatedto system registration,attaching subscriptions, andmanaging subscriptions forproducts.


49

CHAPTER 6. NEXT STEPS

6.1. REGISTERING THE QUICKSTART CLOUD INSTALLER TOITSELF

Registering the QuickStart Cloud Installer (Red Hat Satellite) to itself to receive updates currentlyrequires additional manual steps. Ensure you have a Red Hat Satellite subscription, and follow thesteps in Configuring a Self-Registered Satellite in the Red Hat Satellite Server Administration Guide.

6.2. REGISTERING RED HAT CLOUDFORMS TO THE QUICKSTARTCLOUD INSTALLER

The Red Hat CloudForms instance deployed by the QuickStart Cloud Installer is not registered bydefault. Register the Red Hat CloudForms instance to the QuickStart Cloud Installer (Red HatSatellite 6) to receive updates and to enable Red Hat Insights on the instance. To register Red HatCloudForms, see Registering and Updating Red Hat CloudForms in the Red Hat CloudFormsGeneral Configuration Guide.

6.3. UPDATING CA CERTIFICATES

The QuickStart Cloud Installer and the products deployed uses a self-signed certificate. When youconnect to any of the portals with the default self-signed certificate, you are asked to trust anuntrusted connection to access the site. To update the default certificate with your company’s CAcertificate, refer to the individual product documentation for more information:

For the QuickStart Cloud Installer (Red Hat Satellite), see Configuring Satellite with a CustomServer Certificate.

For Red Hat Virtualization, see Replacing the Red Hat Virtualization Manager SSL Certificate.

For OpenShift Enterprise, see Using a Re-encrypting Route.

For Red Hat CloudForms, see Generating SSL Certificates for Your Appliance and Database.


50

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/server-administration-guide/chapter-3-configuring-a-self-registered-satellite

https://access.redhat.com/documentation/en/red-hat-cloudforms/4.1/single/general-configuration/#registering_and_updating_red_hat_cloudforms

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/single/installation-guide#configuring_satellite_custom_server_certificate

https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/paged/administration-guide/appendix-d-red-hat-virtualization-and-ssl

https://access.redhat.com/documentation/en/openshift-enterprise/version-3.2/installation-and-configuration/#metrics-reencrypting-route

https://access.redhat.com/documentation/en/red-hat-cloudforms/4.1/appliance-hardening-guide/#chap_red_hat_cloudforms_security_guide_ssl_certs


Table A.1. Available Scripts Provided by the QuickStart Cloud Installer ISO File

Script Name Description

launch-fusor-installer Automatically triggered upon boot and calls thefusor-installer script.

fusor-installer Prompts users for networking information, andinstalls the QuickStart Cloud Installer instance.

fusor-local-nfs-setup Sets up a local NFS share on the QuickStart CloudInstaller machine to be used by Red HatVirtualization. For evaluation purposes only.

Table A.2. Available Scripts Provided by the Red Hat OpenStack Platform Installer ISO File

Script Name Description

fusor-undercloud-installer Automatically triggered upon boot. Prompts usersfor networking information, and sets up an Red HatOpenStack Undercloud instance which interactswith the QuickStart Cloud Installer to provision RedHat OpenStack nodes.


51

APPENDIX B. PRODUCT DOCUMENTATION

Red Hat Virtualization product documentation

Red Hat OpenStack Platform product documentation

Red Hat CloudForms product documentation

OpenShift Enterprise product documentation

Red Hat Satellite product documentation


52

https://access.redhat.com/documentation/en/red-hat-virtualization/

https://access.redhat.com/documentation/en/red-hat-openstack-platform/

https://access.redhat.com/documentation/en/red-hat-cloudforms/

https://access.redhat.com/documentation/en/openshift-enterprise/

https://access.redhat.com/documentation/en/red-hat-satellite/


The following diagram illustrates the networking architecture for a four-product deployment (Red HatVirtualization + Red Hat OpenStack Platform + Red Hat CloudForms + OpenShift Enterprise). Notethat Red Hat CloudForms is only required to be deployed once, either as a virtual machine hostedon Red Hat Virtualization or Red Hat OpenStack Platform. In Red Hat Virtualization, the virtualnetworks are bridged to the physical networks. In Red Hat OpenStack Platform, a virtual router isused to route traffic between the private and the public network.


53


54

quickstart cloud installer 1.0 quickstart cloud installer guide · 2016. 10. 7. · the quickstart...

Documents