quickstart cloud installer 0 quickstart cloud installer guide · 2016. 4. 27. · the quickstart...

Red Hat Cloud Suite DocumentationTeam

QuickStart Cloud Installer 0QuickStart Cloud Installer Guide

Installing the QuickStart Cloud Installer and Deploying Red Hat CloudProducts

QuickStart Cloud Installer 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, MetaMatrix, 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 Enterprise Virtualization, Red HatOpenStack Platform, and Red Hat CloudForms.

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

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

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

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

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

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

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

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

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

Table of Contents

CHAPTER 1. INTRODUCTION1.1. INTRODUCTION1.2. SYSTEM REQUIREMENTS1.3. BETA LIMITATIONS

CHAPTER 2. INSTALLING THE QUICKSTART CLOUD INSTALLER

CHAPTER 3. DEPLOYING RED HAT ENTERPRISE VIRTUALIZATION AND RED HAT CLOUDFORMS3.1. PREPARING FOR THE RED HAT ENTERPRISE VIRTUALIZATION DEPLOYMENT3.2. DEPLOYING RED HAT ENTERPRISE VIRTUALIZATION AND RED HAT CLOUDFORMS3.3. VERIFYING THE RED HAT ENTERPRISE VIRTUALIZATION AND RED HAT CLOUDFORMSDEPLOYMENT

CHAPTER 4. DEPLOYING RED HAT OPENSTACK PLATFORM AND RED HAT CLOUDFORMS4.1. PREPARING FOR THE RED HAT OPENSTACK PLATFORM DEPLOYMENT4.2. DEPLOYING RED HAT OPENSTACK PLATFORM AND RED HAT CLOUDFORMS4.3. VERIFYING THE RED HAT OPENSTACK PLATFORM AND RED HAT CLOUDFORMS DEPLOYMENT

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

APPENDIX A. AVAILABLE SCRIPTS

APPENDIX B. PRODUCT DOCUMENTATION

APPENDIX C. NETWORKING ARCHITECTURE

APPENDIX D. REGISTERING THE QUICKSTART CLOUD INSTALLER

3345

7

101014

19

202025

32

343435

36

37

38

39

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 Enterprise Virtualization, Red Hat OpenStack Platform, and Red Hat CloudForms. You candeploy a single product or multiple products in one deployment. For introductory information on eachproduct, see the Product Guide. See the Planning and Engineering Guide to assess which set ofproducts you want to deploy. For example, select between Red Hat Enterprise Virtualization andRed Hat OpenStack Platform for your private cloud infrastructure. Select whether you need Red HatCloudForms to manage your cloud environment. If you have multiple cloud providers, either multipleinstances of the same provider or a mix of different cloud providers, you can use Red HatCloudForms as a single management tool.

The two common deployment paths are:

Deploy Red Hat Enterprise Virtualization + Red Hat CloudForms:

1. Section 3.1, “Preparing for the Red Hat Enterprise Virtualization Deployment”

2. Section 3.2, “Deploying Red Hat Enterprise Virtualization and Red Hat CloudForms”

3. Section 3.3, “Verifying the Red Hat Enterprise Virtualization and Red Hat CloudFormsDeployment”

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

Deploy Red Hat OpenStack Platform + Red Hat CloudForms:

1. Section 4.1, “Preparing for the Red Hat OpenStack Platform Deployment”

2. Section 4.2, “Deploying Red Hat OpenStack Platform and Red Hat CloudForms”

3. Section 4.3, “Verifying the Red Hat Openstack Platform and Red Hat CloudFormsDeployment”

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.1 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 Enterprise Virtualization 3.5 A traditional private cloudprovider for relatively staticenvironments.

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

Red Hat CloudForms 4.0 A management tool for cloudproviders.

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)

150GB 16GB RAM 2

Red Hat EnterpriseVirtualization Manager

25GB 4GB RAM 2

Red Hat EnterpriseVirtualizationhypervisors

10GB 10GB RAM 4

Red Hat OpenStackPlatform Undercloud

40GB 16GB RAM 8

Red Hat OpenStackPlatform OvercloudNodes

40GB 10GB RAM 4


4

Table 1.3. Recommended Hardware Requirements

Systems Disk Space Memory CPUs

QuickStart CloudInstaller (Red HatSatellite)

150GB 16GB RAM 4

Red Hat EnterpriseVirtualization Manager

50GB 16GB RAM 4

Red Hat EnterpriseVirtualizationhypervisors

100GB 16GB RAM 4

Red Hat OpenStackPlatform Undercloud

100GB 16GB RAM 8

Red Hat OpenStackPlatform OvercloudNodes

100GB 16GB 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 Enterprise Virtualization Manager requirements

Red Hat Enterprise Virtualization hypervisor requirements

Red Hat CloudForms requirements

Red Hat Satellite requirements

Software Requirements

The product software used during the deployment is provided by subscriptions or a subscriptionmanifest.

1.3. BETA LIMITATIONS

QuickStart Cloud Installer (Red Hat Satellite 6.1)

Isolating networks is not supported.


5

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-US/Red_Hat_Enterprise_Virtualization/3.5/html-single/Installation_Guide/index.html#sect-Red_Hat_Enterprise_Virtualization_Manager_Requirements

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.5/html-single/Installation_Guide/index.html#sect-Hypervisor_Requirements

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

https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html-single/Installation_Guide/index.html#sect-Red_Hat_Satellite-Installation_Guide-Prerequisites

Capsule servers are not supported.

Red Hat Enterprise Virtualization 3.5

NFS storage is the only supported storage type for Red Hat Enterprise Virtualization.

Only Red Hat Enterprise Linux hosts are supported hypervisor hosts. Red Hat EnterpriseVirtualization Hypervisor (RHEV-H), a minimal operating system based on Red Hat EnterpriseLinux, is not supported.

Self-hosted engine is currently not supported.

Only one network interface (ovirtmgmt bridge) is supported.

Power management for hypervisor 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.

Specifying a different ISO domain other than the default one is not supported.

Red Hat OpenStack Platform 7

Isolating networks is not supported.

High availability is not supported.


6

CHAPTER 2. INSTALLING THE QUICKSTART CLOUDINSTALLER

The QuickStart Cloud Installer is available as an ISO file and is used to provision cloudenvironments. The QuickStart Cloud Installer also allows you to manage lifecycles, errata updates,and subscription manifests.

Note

In production environments, all the deployments except Red Hat CloudForms must bedeployed on physical machines.

1. Prepare a host machine that meets the QuickStart Cloud Installer requirements listed inSection 1.2, “System Requirements”.

2. 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.

3. Ensure a minimum of one network interface is available, and ensure the network is enabledautomatically at boot time. No DHCP or any other provisioning services should be runningon this network.

4. Launch the QuickStart Cloud Installer ISO.

5. Select Install Red Hat QuickStart Cloud Installer 1.0.


7

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

6. The installation process starts with installing a pre-configured Red Hat Enterprise Linux 7system. Set the root password before the installation reaches 100%. Optionally createadditional users.

7. Once the base operating system installation is complete, the system reboots. Log in as theroot user with the password set in the previous step.

8. A terminal window opens automatically and initializes the QuickStart Cloud Installer.Configure the networking details for the QuickStart Cloud Installer machine:

a. The network interface card (option #2) may need to be set for the correctprovisioning network.

b. Enter 3 (Hostname), and press Enter. Enter a host name, and press Enter.

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.

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.


8

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

h. Optionally set option 16 (BMC feature enabled) to true. If your system supportsBaseboard Management Controller (BMC), enabling BMC allows powermanagement on managed hosts using Intelligent Platform Management Interface(IPMI) or a similar protocol. Leave the BMC provider as default or change it to freeipmi depending on your BMC power management provider.

i. Review the networking configuration. To proceed with the configuration and startthe installation script, enter 1, and press Enter. To change a value, enter theassociated number and press Enter. Type in the desired value and press Enter.

Note

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

# launch-fusor-installer

9. After the installation script has completed successfully, double-click the Red Hat CloudInfrastructure WebUI Firefox icon, and log into the user interface with the username adminand the default password changeme. It may be necessary to trust an untrusted connectionto access the site.

10. Change the default password for the administration user of the Red Hat Cloud InfrastructureWebUI by clicking Admin User, then My account. Enter a new password, and click Submit.

Proceed to Chapter 3, Deploying Red Hat Enterprise Virtualization and Red Hat CloudForms orChapter 4, Deploying Red Hat Openstack Platform and Red Hat CloudForms.


9

CHAPTER 3. DEPLOYING RED HAT ENTERPRISEVIRTUALIZATION AND RED HAT CLOUDFORMS

3.1. PREPARING FOR THE RED HAT ENTERPRISEVIRTUALIZATION DEPLOYMENT

3.1.1. Overview

Before you prepare for a deployment, ensure the installation of the QuickStart Cloud Installer iscomplete.

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

Create a node to be used as the Red Hat Enterprise Virtualization Manager.

Create a node to be used as a hypervisor host. Optionally create more nodes to have multiplehypervisor hosts in your environment.

Note

In a production environment, a minimum of two hypervisor hosts is required for thehigh availability of guest machines.

Ensure the required network interfaces are automatically enabled on all nodes so the nodes canbe successfully discovered.

Set up shared NFS storage for Red Hat Enterprise Virtualization.

Create a subscription management application and attach the required subscriptions for thedeployment. Optionally download the manifest for a disconnected environment where yourQuickStart Cloud Installer cannot have direct access to an external network such as the Red HatContent Delivery Network. For a disconnected environment, you need to upload the manifest tothe QuickStart Cloud Installer.

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.

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:


10

3.1.3. How to Create Red Hat Enterprise Virtualization Nodes

A minimum of two hosts is required for a basic Red Hat Enterprise Virtualization deployment.

1. Prepare a host machine that meets the Red Hat Enterprise Virtualization Managerrequirements listed in Section 1.2, “System Requirements”.

2. Prepare a host machine that meets the Red Hat Enterprise Virtualization hypervisorrequirements listed in Section 1.2, “System Requirements”.

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.

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.

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

11

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 QuickStartCloud Installer WebUI. Log in to the QuickStart Cloud Installer as admin with the updatedpassword. If you did not change the default password, the password is changeme.

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


12

3.1.5. How to Set Up Shared NFS Storage

Two NFS shares are required for the deployment. One is to be used as the data domain. The datadomain hosts the virtual machine data in the Red Hat Enterprise Virtualization environment. One isto be used as the export domain and is used as a temporary storage device in the Red HatEnterprise Virtualization environment. For evaluation purposes, you can use the fusor-local-nfs-setup script to speed up the process. For production environments, create the storage sharesmanually so you can tailor them to the requirements of your environment.

Note

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

Using the fusor-local-nfs-setup script

1. On the QuickStart Cloud Installer machine, run the fusor-local-nfs-setup script to set uptwo NFS shares.

$ sudo fusor-local-nfs-setup

NFS shares for RHEV deployments have been created at:/var/lib/exports/vms/var/lib/exports/exports

2. Note down the two storage domain mount points. The information is required during the RedHat Enterprise Virtualization and Red Hat CloudForms deployment.

192.168.155.10:/var/lib/exports/vms

192.168.155.10:/var/lib/exports/exports

Creating the NFS shares manually

See Preparing NFS Storage in the Red Hat Enterprise Virtualization Administration Guide.

3.1.6. How to Create a Subscription Manifest


13

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html/Administration_Guide/sect-Preparing_and_Adding_NFS_Storage.html#Preparing_NFS_Storage

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.

If your QuickStart Cloud Installer is in a disconnected environment (with restricted internet access),complete this section before you start a deployment.

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.1.

6. Click Register.

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

8. Select Red Hat Cloud Infrastructure with Smart Management, enter the appropriatequantity, and click ATTACH SELECTED.

Note

Stop at this step if your QuickStart Cloud Installer can access external networkssuch as the Red Hat Content Delivery Network. The required subscriptionmanagement application has been created, and will be available for selectionduring the deployment. If not, proceed to the next step to download the manifest.

9. At the top of the Satellite entry page, click Download manifest, and save the file to aportable drive.

10. Upload the manifest to the QuickStart Cloud Installer.

Proceed to the next section to start a Red Hat Enterprise Virtualization and Red Hat CloudFormsdeployment.

3.2. DEPLOYING RED HAT ENTERPRISE VIRTUALIZATION ANDRED HAT CLOUDFORMS

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


14

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

3. Configure the Satellite component:

a. Enter a name, and optionally enter a description. Click Next.

b. Select Immediately to publish updates immediately when an update is available.Click Next. Alternatively, select After manually publishing them to manuallypublish any updates to the environment, and select an environment.

c. Select the Enable Red Hat Insights check box. Click Next. Red Hat Insights is alightweight data collection and analysis tool. For more information, seehttps://access.redhat.com/insights/splash/.

4. Configure the Red Hat Enterprise Virtualization component:


15

https://access.redhat.com/insights/splash/

a. Select Hypervisor + engine, and click Next.

b. Select the host to be used as the Red Hat Enterprise Virtualization Manager, alsoknown as the engine. The selected host will default to a name of its MAC address.Click the Host Name field and update the host name as necessary. 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 Enterprise Virtualization Administration Portal. These passwordsrequire a minimum of 8 characters. The remainder of the fields can be left asdefault. Click Next.


16

e. Enter the NFS data domain and export domain details, and click Next. Ensure thereare no trailing spaces in the share path.

5. Configure the CloudForms component:

a. Select Install CloudForms on Red Hat Enterprise Virtualization. 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 requires aminimum of 8 characters. Click Next.

6. Configure subscriptions:

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


17

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.

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.

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 progress bar will remain at 53.8% for two tothree hours and can be safely ignored. The discovered hosts are provisioned with Red HatEnterprise Linux. Puppet will run on the provisioned hosts to install Red Hat EnterpriseVirtualization packages from the QuickStart Cloud Installer machine. Red Hat CloudFormswill be created as a virtual machine hosted in the Red Hat Enterprise Virtualizationenvironment. When all three progress bars are at 100%, the deployment is complete.

8. Click Next to view the Installation Summary. You will see the URLs of the portals toaccess Red Hat Enterprise Virtualization and Red Hat CloudForms. Hover over the blueinformation icon to view the IP address of each portal.

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, otherwise use the IP addresses to connect to the portals.


18

3.3. VERIFYING THE RED HAT ENTERPRISE VIRTUALIZATION ANDRED HAT CLOUDFORMS DEPLOYMENT

Verify that the components are running and accessible.

1. To verify Red Hat Enterprise Virtualization:

a. Open the Red Hat Enterprise Virtualization Administration Portal using the URL orthe IP address shown on the Installation Summary screen.

b. Log in as admin with the password set.

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

Data centers

Storage

Virtual machines

Hosts

The alert in the Red Hat Enterprise Virtualization Administration Portal aboutfailing to verify power management for a given host is normal and can beignored.

2. To verify Red Hat CloudForms:

a. Open the Red Hat CloudForms Portal using the URL or the IP address shown onthe Installation Summary screen.


c. Select Infrastructure → Providers in the top-right menu, and verify that <project-name>RHEV is listed among the providers.


19

CHAPTER 4. DEPLOYING RED HAT OPENSTACKPLATFORM AND RED HAT CLOUDFORMS

4.1. PREPARING FOR THE RED HAT OPENSTACK PLATFORMDEPLOYMENT

4.1.1. Overview

Before you prepare for a deployment, ensure the installation of the QuickStart Cloud Installer iscomplete.

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

Ensure the required network interfaces are available and automatically enabled 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 download the manifest for a disconnected environment where yourQuickStart Cloud Installer does not have direct access to an external network such as the RedHat Content Delivery Network. For a disconnected environment, you need to upload themanifest to the QuickStart Cloud Installer.

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.

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.

Requirements:

For Overcloud nodes, the boot device must have PXE at a higher priority than local drives.

For Overcloud nodes, the PXE Network Interface Card (NIC) must be the one connected to theRed Hat OpenStack Platform provisioning network.

An example networking diagram:


20

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”.

2. 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.

3. Launch the Red Hat OpenStack Platform Undercloud Installer.

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

21

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

4. Select Install Red Hat OSP Undercloud 7.

5. The installation process starts with installing a pre-configured Red Hat Enterprise Linux 7system. Set the root password before the installation reaches 100%. Optionally createadditional users.

Note

The root password can only be set once in Anaconda. This is a known issue. Youcan change the root password as normal after the system has booted. SeeResetting the Root Password of RHEL-7/ systemd for more information.Alternatively, re-install the Red Hat OpenStack Platform Undercloud Installer.

6. After the system reboots, log in as root with root password set in the previous step.

7. Set the FQDN.(For example: undercloud.example.com)

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


22

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

undercloud.example.com

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

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

9. Select the network interface that is connected to your provisioning network. (For example: 1)

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

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

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]

11. Enter the IP address of the Red Hat OpenStack Platform Undercloud node. (For example: [192.168.150.254])

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]

12. Enter the IP Address of the network gateway. (For example: [192.168.150.1])

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]

13. 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>]

14. 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 the


23

Undercloud 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 usenameadmin and the password set.

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 Manifest

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.

If your QuickStart Cloud Installer is in a disconnected environment (with restricted internet access),complete this section before you start a deployment.

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


24

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.1.

6. Click Register.

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

8. Select Red Hat Cloud Infrastructure with Smart Management, enter the appropriatequantity, and click ATTACH SELECTED.

Note

Stop at this step if your QuickStart Cloud Installer can access external networkssuch as the Red Hat Content Delivery Network. The required subscriptionmanagement application has been created, and will be available for selectionduring the deployment. If not, proceed to the next step to download the manifest.

9. At the top of the Satellite entry page, click Download manifest, and save the file to aportable drive.

10. Upload the manifest to the QuickStart Cloud Installer.

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

4.2. DEPLOYING RED HAT OPENSTACK PLATFORM AND RED HATCLOUDFORMS

1. In the Red Hat Cloud Infrastructure WebUI (Red Hat Satellite Portal), select QuickStartCloud 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:


25

a. Enter a name, and optionally enter a description. Click Next.

b. Select Immediately to publish updates immediately when an update is available.Click Next. Alternatively, select After manually publishing them to manuallypublish any updates to the environment, and select an environment. Click Next.

c. Select the Enable Red Hat Insights check box. Red Hat Insights is a lightweightdata collection and analysis tool. For more information, seehttps://access.redhat.com/insights/splash/.

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.


26

https://access.redhat.com/insights/splash/

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.

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

i. For the driver, select pxe-ipmi for a bare metal machine and pxe_ssh for avirtual machine.

ii. Enter the IP address.

iii. Enter root as the IPMI User.

iv. Enter the root user password, and click Next to start the auto-detection ofavailable nodes.

v. Deselect all nodes other than the two nodes you created to be used asOvercloud nodes.

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

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.


27

vii. Click Register. It takes up to 5 minutes to register one node.

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

c. Click + Assign Role, and select the Compute role. Five roles are available:Compute, Controller, Ceph-Storage, Cinder-Storage, and Swift-Storage.

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.


28

i. Enter the interface that is connected to your Red Hat OpenStack Platformpublic network. (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)

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.

5. Configure the CloudForms component:

a. Select Install CloudForms on Red Hat Enterprise Linux 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 requires aminimum of 8 characters. Click Next.

6. Configure subscriptions:


29

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

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.

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


30

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.

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. Hover over the blue information icon to view the IP address of eachportal.

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, otherwise use the IP addresses to connect to the portals.


31

4.3. VERIFYING THE RED HAT OPENSTACK PLATFORM AND REDHAT CLOUDFORMS DEPLOYMENT

Verify that the components are running and accessible.

1. To verify Red Hat OpenStack Platform:

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


c. Verify that you can see a successful overcloud deployment on the top-right corner.

d. Open the Overcloud Portal using the Overcloud URL or the IP address shown onthe Installation Summary screen.

e. Log in as admin with the password set.


32

f. 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 or the IP addressshown on the Installation Summary screen.


c. Select Cloud → Providers in the top-right menu, and verify that <project-name>RHOS is listed among the providers.


33

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 Content in the Red Hat Satellite Installation Guide to synchronize thecontent manually. After content synchronization is complete, perform a new deployment. If thefailure persists, contact the Red Hat Global Support Team.

The progress bar for the RHEV deployment hangs at 95.5%

When deploying Red Hat Enterprise Virtualization and Red Hat CloudForms, if the progress barfor the Red Hat Enterprise Virtualization deployment hangs at 95.5%, it indicates an error withconfiguring the data center for Red Hat Enterprise Virtualization. See /var/log/messages for errorlogs. NFS-related issues are the most common reason for a deployment failure. Verify thefollowing 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 hypervisor 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 Enterprise 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 OpenStack

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.

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


34

https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/chap-Red_Hat_Satellite-Installation_Guide-Populating_Red_Hat_Satellite_with_Content.html#sect-Red_Hat_Satellite-Installation_Guide-Connected_Satellite-Synchronizing_Content_from_Source_Repositories_to_Red_Hat_Satellite

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

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.

5.2. LOG FILES

Table 5.1. QuickStart Cloud Installer Log Files

Component Log File Description

QuickStart Cloud Installerinstallation

/var/log/katello-installer/katello-installer.log

Installation-related logs anderrors.

QuickStart Cloud Installerdeployments

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

Deployment-related logs anderrors.

Foreman Proxy /var/log/foreman-proxy/proxy.log Information about servicesassociated with the QuickStartCloud Installer, such as DHCP,TFTP, and Puppet.

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

Messages and errors related tosystem registration, attachingsubscriptions, and managingsubscriptions for products.

CHAPTER 5. TROUBLESHOOTING AND LOGS

35

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

APPENDIX A. AVAILABLE SCRIPTS

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

Script Name Description

fusor-installer Automatically triggered upon boot. Prompts usersfor networking information, and installs theQuickStart Cloud Installer instance.

fusor-local-nfs-setup Sets up a local NFS share on the QuickStart CloudInstaller machine to be used by Red Hat EnterpriseVirtualization. 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.


36


Red Hat Enterprise Virtualization product documentation

Red Hat OpenStack Platform product documentation

Red Hat CloudForms product documentation

Red Hat Satellite product documentation


37

https://access.redhat.com/documentation/en/red-hat-enterprise-virtualization/?version=3.5

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/red-hat-satellite/

APPENDIX C. NETWORKING ARCHITECTURE

The following image illustrates the networking architecture for a three-product deployment (Red HatEnterprise Virtualization + Red Hat OpenStack Platform + Red Hat CloudForms). Note that Red HatCloudForms is only required to be deployed once, either as a virtual machine hosted on Red HatEnterprise Virtualization or Red Hat OpenStack Platform.


38

APPENDIX D. REGISTERING THE QUICKSTART CLOUDINSTALLER

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 Registering a Satellite to Itself in the Red Hat Satellite Installation Guide.

APPENDIX D. REGISTERING THE QUICKSTART CLOUD INSTALLER

39

https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/chap-Red_Hat_Satellite-Installation_Guide-Configuring_a_Self_Registered_Satellite.html#sect-Red_Hat_Satellite-Installation_Guide-Setting_Up_a_Self_Registered_Satellite-Registering_a_Satellite_to_Itself

quickstart cloud installer 0 quickstart cloud installer guide · 2016. 4. 27. · the quickstart...

Documents