Technical Guide – Deploying CloudForms 4.1 in the Dell Red Hat

Technical Guide – Deploying

CloudForms 4.1 in the Dell

Red Hat OpenStack Cloud

Solution - Version 5.0

© 2014-2016 Dell Inc.

Contents | 2

Technical Guide – Deploying CloudForms 4.1 in the Dell Red Hat OpenStack Cloud Solution - Version 5.0

Contents

Trademarks....................................................................................................................................... 4

Notes, Cautions, and Warnings................................................................................................... 5

Executive Summary........................................................................................................................ 6About Red Hat CloudForms...............................................................................................6Intended Audience............................................................................................................... 6

About Red Hat CloudForms......................................................................................................... 7

About This Document................................................................................................................... 8

Background.......................................................................................................................................9

Prepare to Install CloudForms...................................................................................................10Prepare the Environment..................................................................................................10

Network Requirements............................................................................................10Obtain Software and Upload to Glance.............................................................. 10Configure CloudForms Security Group in OpenStack..................................... 12Boot the CloudForms VM.......................................................................................12

Install and Configure CloudForms............................................................................................ 15Prepare the CloudForms VM for SSH Access...............................................................15Deploy DNS..........................................................................................................................16

Configure dnsmasq.................................................................................................. 16Set the CloudForms VM Hostname................................................................................ 17Configure CloudForms Database Storage.....................................................................17Complete the Installation..................................................................................................19Test the Installation............................................................................................................20

Configure DNS Name Resolution on a Client................................................... 20Enter Red Hat Subscription Information.......................................................................20Update the Platform...........................................................................................................21

Configure CloudForms to Manage Providers........................................................................ 22Configure the Infrastructure Provider Undercloud.....................................................22

Add the Undercloud as an Infrastructure Provider........................................... 22Ensure Network Access to Controllers............................................................... 23

Contents | 3


Configure the Cloud Provider Overcloud.....................................................................23Open RabbitMQ Ports............................................................................................. 23Add the Overcloud as a Cloud Provider............................................................. 25

Next Steps...................................................................................................................................... 26

Getting Help...................................................................................................................................27Contacting Dell................................................................................................................... 27References............................................................................................................................ 27

To Learn More...........................................................................................................27

Trademarks | 4


Trademarks

© 2014-2016 Dell Inc. All rights reserved. Reproduction of this material in any manner whatsoeverwithout the express written permission of Dell Inc. is prohibited. For more information, contact Dell.

Trademarks used in this text: Dell™, the DELL logo, PowerEdge™, and Dell Networking™ are trademarksof Dell Inc. Intel® and Xeon® are registered trademarks of Intel Corporation in the U.S. and othercountries. Microsoft® and Windows® are registered trademarks of Microsoft Corporation in the UnitedStates and/or other countries.

Red Hat®, Red Hat Enterprise Linux®, and Ceph are trademarks or registered trademarks of Red Hat, Inc.,registered in the U.S. and other countries. Linux® is the registered trademark of Linus Torvalds in theU.S. and other countries. Oracle® and Java® are registered trademarks of Oracle Corporation and/or itsaffiliates.

DISCLAIMER: The OpenStack® Word Mark and OpenStack Logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States andother countries, and are used with the OpenStack Foundation's permission. We are not affiliated with,endorsed or sponsored by the OpenStack Foundation or the OpenStack community.

Firefox® and the Firefox logo are registered trademarks of the Mozilla Foundation.

The Midokura® name and logo, as well as the MidoNet® name and logo, are registered trademarks ofMidokura SARL.

Other trademarks and trade names may be used in this publication to refer to either the entitiesclaiming the marks and names or their products. Dell Inc. disclaims any proprietary interest intrademarks and trade names other than its own.

Notes, Cautions, and Warnings | 5


Notes, Cautions, and Warnings

A Note indicates important information that helps you make better use of your system.

A Caution indicates potential damage to hardware or loss of data if instructions are not followed.

A Warning indicates a potential for property damage, personal injury, or death.

This document is for informational purposes only and may contain typographical errors and technicalinaccuracies. The content is provided as is, without express or implied warranties of any kind.

Executive Summary | 6


Executive Summary

CloudForms manages container, virtual, private, and public cloud infrastructures by providing a robustsystem of inventory, monitoring, automation, chargeback, and billing.

About Red Hat CloudForms

Red Hat CloudForms is the "Hybrid Cloud Management That Evolves." Managing a complex, hybrid ITenvironment can require multiple management tools, redundant policy implementations, and extrastaff to handle the operations. Red Hat CloudForms simplifies this, providing unified management andoperations in a hybrid environment. As your IT infrastructure progresses from traditional virtualizationtoward an Infrastructure-as-a-Service (IaaS) and Platform-as-a-Service (PaaS) model, CloudFormsevolves, protecting your investments and providing consistent user experience and functionality.

CloudForms provides comprehensive cloud management that accelerates service delivery andreduces operational costs. It has a self-service portal and catalog with automatic provisioning,workload life-cycle management, including reconfiguration and retirement. It also includes resourcequota enforcement, cost allocation, and chargeback capabilities. CloudForms will help you improveoperational visibility and control through continuous discovery, monitoring, and tracking of resourceusage. It focuses on optimization, and capacity planning through entity relationship planning withtimelines and events. CloudForms helps you ensure compliance and governance by providingautomated policy enforcement and remediation. Its segmented user access with approval workflowsmake for easy configuration auditing, change tracking, and drift analysis.

Intended Audience

This technical guide shows the administrator how to build and deploy CloudForms in their Dell RedHat OpenStack Cloud Solution. It provides a simple system for an introudction and training of anCloudForms systems administrator. The end users (other cloud administrators, tenants and customers)are not directly addressed in this document.

Find out more about developing and managing CloudForms by accessing the Red Hat documentationhere: https://access.redhat.com/documentation/en/red-hat-cloudforms/.

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

About Red Hat CloudForms | 7


About Red Hat CloudForms

Red Hat CloudForms is the "Hybrid Cloud Management That Evolves." Managing a complex, hybrid ITenvironment can require multiple management tools, redundant policy implementations, and extrastaff to handle the operations. Red Hat CloudForms simplifies this, providing unified management andoperations in a hybrid environment. As your IT infrastructure progresses from traditional virtualizationtoward an Infrastructure-as-a-Service (IaaS) and Platform-as-a-Service (PaaS) model, CloudFormsevolves, protecting your investments and providing consistent user experience and functionality.

CloudForms provides comprehensive cloud management that accelerates service delivery andreduces operational costs. It has a self-service portal and catalog with automatic provisioning,workload life-cycle management, including reconfiguration and retirement. It also includes resourcequota enforcement, cost allocation, and chargeback capabilities. CloudForms will help you improveoperational visibility and control through continuous discovery, monitoring, and tracking of resourceusage. It focuses on optimization, and capacity planning through entity relationship planning withtimelines and events. CloudForms helps you ensure compliance and governance by providingautomated policy enforcement and remediation. Its segmented user access with approval workflowsmake for easy configuration auditing, change tracking, and drift analysis.

About This Document | 8


About This Document

This document contains code and configuration samples in monospace fonts. While it is tempting forthe user to copy and paste those values from this document into their system, it is inadvisable and notsupported. While we make every effort to ensure that the documentation is correct and complete,documents rendered via some client applications make unpredictable changes to the actual spacing ofthe data elements, and lose fidelity to what a proper code or configuration setting should actually beto work properly. We see very impactful changes, for example, between the Firefox PDF display and theAdobe Acrobat reader PDF display.

Copy and paste from this document only with full understanding of the necessary formatting changesthat you'll have to make. We have made efforts to provide online verbatim copies of the essential data,as well as pointing the user to appropriate external documentation to achieve the proper formatting.

Background | 9


Background

CloudForms is delivered as a VM designed specifically for OpenStack. It is initially configured via asimple command line interface. The running product is accessed through a web GUI. It will be loadedinto Glance and launched by Nova to provide control features to OpenStack tenants. It can helpmanage the Undercloud and the Overcloud of your RHOSP deployment. It will also manage:.

• Your OpenShift deployment• Amazon EC2 and Azure clouds• VMware ESX Server• Microsoft HyperV

CloudForms requires access to the Nova API network (normally vLAN 190 in our solution). As an addedbonus, access to the provisioning network will allow CloudForms to interrogate all of the Undercloudservers in depth. It will also need access to any private tenant network or floating IP networks that thecustomer intends to manage with CloudForms.

Prepare to Install CloudForms | 10


Prepare to Install CloudForms

Note: If you will also be installing OpenShift in this OpenStack deployment, deploy OpenShiftfirst. OpenShift creates an Infrastructure node with DNS that will be useful to the CloudFormsdeployment.

To enable easy upgrade of CloudForms, this solution uses a mix of ephemeral storage and persistentstorage. It uses ephemeral storage for the CloudForms executables and underlying OS; and a separate,persistent Cinder volume for the database.

Prepare the Environment

Perform the following procedures to prepare the CloudForms installation environment:

1. Network Requirements on page 102. Obtain Software and Upload to Glance on page 103. Configure CloudForms Security Group in OpenStack on page 124. Boot the CloudForms VM on page 12

Network Requirements

The virtual machines in this solution require:

• Internet access• Access to the Overcloud's OpenStack API network• SSH (Port 22) access to any VMs to be managed with CloudForms• Access to the Undercloud's OpenStack API network• SSH (Port 22) access to any Undercloud servers to be managed with CloudForms

For more information see Integrating CloudForms 4.1 and OpenShift 3.2 in the Dell Red Hat OpenStackCloud Solution - Version 5.0.

Obtain Software and Upload to Glance

To obtain the VM image and upload it to Glance:

1. Download the latest CloudForms QCOW2 VM image for OpenStack from https://access.redhat.com/downloads/content/167/ver=/cf-me---4.1/4.1/x86_64/product-software.

2. Move the image to the Director Node home directory, via scp, from the directory where youdownloaded it.

3. Log onto the Director Node as either:

• User admin_user, or• The user configured in Table 3: Director Node Configuration Parameters, in the Dell Red Hat

OpenStack Cloud Solution Deployment Guide - Version 5.0.

Note: Glance versions differ, and some of the command line options may have synonyms.Please verify your version and the correct syntax, especially with regards to the --visibility paramter.

4. Check to see if you already have the image in the Overcloud, and note if your version of Glanceis the same. If your version of glance is not the same, check glance --help and ensure that theproper command line arguments, some might have changed names:

$ . ~/overcloudrc

https://access.redhat.com/downloads/content/167/ver=/cf-me---4.1/4.1/x86_64/product-software

https://access.redhat.com/downloads/content/167/ver=/cf-me---4.1/4.1/x86_64/product-software



$ glance --version1.1.1

$ glance image-list

The output will display information similar to that in Table 1: glance image-list Command Output onpage 11:

Table 1: glance image-list Command Output

ID Name DiskFormat

ContainerFormat

Size Status

d587cd54-7dbf-48db-9d10-07a469daf0a0 cirros qcow2 bare 13200896 active

5. If the image does not exist, create it:

$ glance image-create --name "CloudForms 4.1" --disk-format qcow2 \ --container-format bare --visibility public --protected True --file \ ~/cfme-rhos-5.6.0.13-1.x86_64.qcow2

The output will display information similar to that in Table 2: glance image-create Command Outputon page 11:

Table 2: glance image-create Command Output

Property Value

checksum 4a0abe8bb52965b197456f4f24235fb4

container_format bare

created_at 2016-06-30T17:14:35Z

direct_url rbd://e0fcff86-0621-11e6-adf7-525400148930/images/6f3fc39c-8f30-425f-b5ed-2fbe0f4f83e0/snap

disk_format qcow2

id 6f3fc39c-8f30-425f-b5ed-2fbe0f4f83e0

min_disk 0

min_ram 0

name CloudForms 4.1

owner c1b740d8571f4cb5aa66f8ddcfdec015

protected True

size 754253824

status active

tags []

updated_at 2016-06-30T17:14:45Z

virtual_size None

visibility public



6. Configure the CloudForms flavor:

$ nova flavor-create --is-public true "CloudForms 4.1" auto 6144 45 4

The output will display information similar to that in Table 3: nova flavor-create Command Output onpage 12:

Table 3: nova flavor-create Command Output

ID Name Memory_MB

Disk Ephemeral Swap VCPUs RXTX_Factor

Is_public

27081bef-0873-4efc-b2c8-3a0bf953a9dd

CloudForms 4.1 6144 45 0 4 1.0 True

Configure CloudForms Security Group in OpenStack

CloudForms requires special security groups to gather information, and allow us to access it.

To configure the CloudForms security group in OpenStack:

1. Access the OpenStack Dashboard in a web browser.2. Navigate to the Admin Project.3. Create a security group for the CloudForms VM named CloudForms.4. Create rules for the CloudForms group that express:

a. Egress, IPv4b. Egress, IPv6c. Egress, ICMPd. Ingress, ICMPe. Custom TCP Rule, Ingress, Port 22, from the IP address of the Director Nodef. Custom TCP Rule, Ingress, Port 25, from 0.0.0.0/0g. Custom TCP Rule, Ingress, Port 80, from 0.0.0.0/0h. Custom TCP Rule, Ingress, Port 443, from 0.0.0.0/0

When you execute nova boot in the next step, Boot the CloudForms VM on page 12, you willreference this security group by name.

Boot the CloudForms VM

To boot the CloudForms VM on the proper network:

1. Find the ID of whatever "tenant" network is available.

a. Or, see the OpenShift integration guide to locate the proper "fixed_network."

$ nova net-list

The output will display information similar to that in Table 4: nova net-list Command Output on page13:



Table 4: nova net-list Command Output

ID Label CIDR

908a7fbb-db09-4877-be07-9ef1a6054ded nova None

16d9d112-271a-4c4e-8800-6da82f71140f tenant_net None

ecec7dfc-fda3-4709-812c-5f83710be0f8 ossdell-cluster_network-5lvnvfgfxjph None

5531e4f4-064f-441a-8f28-25f884dcc4bc HA network tenantc1b740d8571f4cb5aa66f8ddcfdec015

None

3a685a32-22d8-4dc2-81cf-de93e8301b74 ossdell-fixed_network-w4y6mxxazcwt None

2. Use the ID to start a CloudForms instance:

$ nova boot --flavor "CloudForms 4.1" --image "CloudForms 4.1" --key-name key_name \--nic net-id=3a685a32-22d8-4dc2-81cf-de93e8301b74 \--security-groups CloudForms CloudForms1

The output will display information similar to that in Table 5: nova boot Command Output on page13:

Table 5: nova boot Command Output

Property Value

OS-DCF:diskConfig MANUAL

OS-EXT-AZ:availability_zone

OS-EXT-SRV-ATTR:host -

OS-EXT-SRV-ATTR:hypervisor_hostname -

OS-EXT-SRV-ATTR:instance_name instance-0000031a

OS-EXT-STS:power_state 0

OS-EXT-STS:task_state scheduling

OS-EXT-STS:vm_state building

OS-SRV-USG:launched_at -

OS-SRV-USG:terminated_at -

accessIPv4

accessIPv6

adminPass f3a6PFwgEhQi

config_drive

created 2016-06-30T18:03:45Z

flavor CloudForms 4.1 (27081bef-0873-4efc-b2c8-3a0bf953a9dd)

hostId

id 71574b7a-2f2a-4418-8c08-f4c661b095ad



Property Value

image CloudForms 4.1 (6f3fc39c-8f30-425f-b5ed-2fbe0f4f83e0)

key_name key_name

metadata {}

name CloudForms1

os-extended-volumes:volumes_attached {}

progress 0

security_groups default

status BUILD

tenant_id c1b740d8571f4cb5aa66f8ddcfdec015

updated 2016-06-30T18:03:45Z

user_id 3d0e3655d9224e5292b5f0cd3646a5ac

3. Create a floating IP address, and associate a floating IP address to your CloudForms node, forexternal access:

$ nova floating-ip-create nova

The output will display information similar to that in Table 6: nova floating-ip-create Command Outputon page 14:

Table 6: nova floating-ip-create Command Output

Id IP Server ID Fixed IP Pool

a47ab8bf-0c14-43da-b285-ff6db80c3755

192.168.191.6 - - nova

$ nova floating-ip-associate CloudForms1 192.168.191.6$ nova floating-ip-list

The output will display information similar to that in Table 7: nova floating-ip-list Command Output onpage 14:

Table 7: nova floating-ip-list Command Output

Id IP Server ID Fixed IP Pool

a47ab8bf-0c14-43da-b285-ff6db80c3755

192.168.191.6 1b1b4d42-faac-4ed0-b672-b52867629897

192.168.201.8 nova

Install and Configure CloudForms | 15


Install and Configure CloudForms

Perform the following procedures to install and configure CloudForms in the Dell Red Hat OpenStackCloud Solution:

1. Prepare the CloudForms VM for SSH Access on page 152. Deploy DNS on page 16

a. Configure dnsmasq on page 163. Set the CloudForms VM Hostname on page 174. Configure CloudForms Database Storage on page 175. Complete the Installation on page 196. Test the Installation on page 20

a. Configure DNS Name Resolution on a Client on page 207. Enter Red Hat Subscription Information on page 208. Update the Platform on page 21

Prepare the CloudForms VM for SSH Access

To prepare the CloudForms VM for SSH access:

1. From the Director Node, connect to a Controller node:

$ ssh cntl0

a. Generate SSH keys if you need them:

$ ls -al ~/.ssh/id_rsa || ssh-keygen

Note: Do not overwrite existing keys.

2. Find the floating IP address of the CloudForms1 VM (192.168.181.7 in this example):

$ nova list | grep CloudForms

The output will display information similar to that in Table 8: nova list Command Output on page15:

Table 8: nova list Command Output

ID Name Status Task State PowerState

Networks

59eb1210-8f10-42d8-887b-52a9059c54ea

CloudForms1 ACTIVE - Running tenant_net=192.168.201.9,192.168.191.7

The Controller nodes should now have access to the floating IP address range. If not, consult yournetwork administrator to gain access to the floating IP address ranges from your Controllers.

3. For easier access, copy the root SSH public key to the CloudForms1 VM:

# ssh-copy-id 192.168.191.7



/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed/bin/ssh-copy-id: INFO: 1 key(s) remain to be [email protected]'s password:Number of key(s) added: 1Now try logging into the machine, with: "ssh '192.168.191.7'"and check to make sure that only the key(s) you wanted were added.

4. Access the CloudForms VM:

# ssh 192.168.201.9Last login: Thu Apr 28 19:47:21 2016 from 192.168.201.1Welcome to the Appliance ConsoleFor a menu, please type: appliance_console[root@host-192-168-201-9~]#

Deploy DNS

CloudForms requires DNS. This solution requires some specific DNS entries. Please see the followingnotes to ensure that DNS is configured correctly for this solution.

Some important points about deploying DNS:

• If you plan to install OpenShift, then you should do so now before proceeding further in thisdocument.

• If OpenShift is already deployed, see DNS Configuration in Integrating CloudForms 4.1 and OpenShift3.2 in the Dell Red Hat OpenStack Cloud Solution - Version 5.0.

• Execute those commands for setting up the DNS properly.• Skip Configure dnsmasq on page 16 in this document; return at Set the CloudForms VM

Hostname on page 17, and proceed from there.• If you have installed DNS as a Service in OpenStack (codename Designate,) please configure it

appropriately based on the DNS record settings detailed below for dnsmasq.• If you do not plan to install OpenShift, proceed to Configure dnsmasq on page 16 .

Configure dnsmasq

The CloudForms VM requires DNS resolution to manage assets.

To configure dnsmasq network services:

1. Gather some information about your systems, from the Director Node:

a. Get the Undercloud OpenStack AUTH URL from the /root/stackrc file.b. Get the Overcloud OpenStack AUTH_URL from the /home/osp_admin/overcloudrc file.

2. Create a file called /etc/dnsmasq.d/00-example.conf.

a. Use the settings below.b. Be sure to add the floating IP address for this node, that you associated to it in Boot the

CloudForms VM on page 12.

strict-orderdomain-neededlocal=/example.com/bind-dynamicresolv-file=/etc/resolv.conf.upstreamaddress=/cloudforms.example.com/<cloudforms Floating IP>address=/undercloud.example.com/<IP address of the UnderCloud OpenStack AUTH URL>



address=/overcloud.example.com/<IP address of the OverCloud OpenStack AUTH URL>log-queries

3. Enable the dnsmasq service:

# systemctl enable dnsmasqCreated symlink from / etc/systemd/system/multi-user.target.wants/dnsmasq.service to /usr/lib/systemd/system/dnsmasq.service.# ^enable^start^# systemctl start dnsmasq

4. Set /etc/hosts to reflect the known hosts, the resolv.conf, and resolve.conf.upstream:

# cp /etc/resolv.conf /etc/resolve.conf.upstream

5. Edit the /etc/resolv.conf file to prefer localhost's dnsmasq, by replacing the file's contents with this:

search example.comnameserver 127.0.0.1

6. Write-protect the /etc/resolv.conf file from DHCP client overwrites:

# chattr +i /etc/resolv.conf

Set the CloudForms VM Hostname

To set the CloudForms VM's hostname:

1. On the CloudForms, execute the following command:

[root@host-192-168-201-9~]# hostnamectl set-hostname cloudforms.example.com

2. Log out and log back in, to ensure that the hostname was set properly. It should appear on yourcommand prompt, instead of the IP address as in Step 1 above.

[root@host-192-168-0-11 ~]# logoutConnection to 192.168.191.22 closed.[heat-admin@tan-controller-0 ~]$ ssh [email protected] to the Appliance ConsoleFor a menu, please type: appliance_console[root@cloudforms ~]#

Configure CloudForms Database Storage

To configure storage for the CloudForms database:

1. From the Director Node, get the ID of your CloudForms1 VM:

$ nova list

The output will display information similar to that in Table 9: nova list Command Output on page18:



Table 9: nova list Command Output

ID Name Status Task State PowerState

Networks

59eb1210-8f10-42d8-887b-52a9059c54ea

CloudForms1 ACTIVE - Running tenant_net=192.168.201.9,192.168.191.7

2. Create a 100 GB Cinder volume for its persistent storage, and note its ID:

$ cinder create --display-name cloudforms1 100

The output will display information similar to that in Table 10: cinder create Command Output onpage 18:

Table 10: cinder create Command Output

Property Value

attachments []

availability_zone nova

bootable false

consistencygroup_id None

created_at 2016-04-29T22:37:22.000000

description None

encrypted False

id 82da887d-88f6-4b23-a2bf-41c90b1f1077

metadata {}

migration_status None

multiattach False

name cloudforms1

os-vol-host-attr:host rbd:volumes@tripleo_ceph#tripleo_ceph

os-vol-mig-status-attr:migstat None

os-vol-mig-status-attr:name_id None

os-vol-tenant-attr:tenant_id c1b740d8571f4cb5aa66f8ddcfdec015

os-volume-replication:driver_data None

s-volume-replication:extended_status None

replication_status disabled

size 100

snapshot_id None

source_volid None

status creating



Property Value

user_id 3d0e3655d9224e5292b5f0cd3646a5ac

volume_type None

3. Attach the two IDs in proper order: <serverId> <volumeId>:

$ nova volume-attach 59eb1210-8f10-42d8-887b-52a9059c54ea 82da887d-88f6-4b23-a2bf-41c90b1f1077

The output will display information similar to that in Table 11: nova volue-attach Command Output onpage 19:

Table 11: nova volue-attach Command Output

Property Value

device /dev/vdb

id 82da887d-88f6-4b23-a2bf-41c90b1f1077

serverId 59eb1210-8f10-42d8-887b-52a9059c54ea

volumeId 82da887d-88f6-4b23-a2bf-41c90b1f1077

4. Ensure that the volume is available on the VM.

a. Connect via ssh to the CloudForms VM:

$ ssh [email protected]

b. Execute the following command in order to make sure that there is a vdb device.

# dmesg | grep vd

[ 1.037213] vda: vda1 vda2[ 4.194885] XFS (vda1): Mounting V4 Filesystem[ 5.085088] XFS (vda1): Ending clean mount[ 5.085105] SELinux: initialized (dev vda1, type xfs), uses xattr[ 4960.461795] vdb: unknown partition table

Note: The message, vdb: unknown partition table, is desired.

Complete the Installation

To complete the CloudForms installation:

1. From the CloudForms VM, execute the following command:

# appliance_console

2. Select "8) Configure Database".

a. Notice that it selects the proper mount point, likely /dev/vdb.3. Select an Internal Database.4. Enter 1 for a region number.5. Accept all of the remaining default prompts.6. Select "14) Start EVM Server Processes" to start the service.



CloudForms is now configured, and is ready for web access on the floating IP address(http://192.168.191.7), using these credentials:

• Username - admin• Password - smartvm

Test the Installation

Now that CloudForms is installed you can test that DNS is fully functional.

Perform the following procedure to test DNS functionality:

• Configure DNS Name Resolution on a Client on page 20

Configure DNS Name Resolution on a Client

If you have already installed OpenShift, then your Infrastructure node's DNS server should alreadybe in your client (or bastion host) naming configurations. You should be able to browse to https://cloudforms.example.com/.

If OpenShift has not been installed, then follow the procedures in this topic.

To configure DNS name resolution on a client:

1. In Windows, navigate to Network and Sharing Center, then select Change Adapter Settings.2. Right-click on the adapter that you use to connect to the OpenShift console (usually the public

network), then choose Properties.3. Double-click on Internet Protocol Version 4, then change the Preferred DNS Server to the public IP

address of the Infra VM.4. Click on OK, then on OK again to close the Network Properties dialogue box and ensure that the

setting was saved.5. Run cmd.exe to display a command console.6. Ensure that the DNS server was accepted by the configuration, and applied to the Network settings,

by executing the following command:

C:\> ipconfig /all

7. Ensure network connectivity by executing the following command:

C:\> ping <infra host IP address>

8. Execute the following command to return the IP address of the load balancer (typically lb-delloss.example.com):

C:\> nslookup <lb FQDN>

Enter Red Hat Subscription Information

You will need to ensure that your platform receives Red Hat updates, using your Red Hat subscription.

To enter your Red Hat subscription information:

1. From the CloudForms web interface, navigate to Settings > Configuration > CFME Region: Region 1> Red Hat Updates.

Note: In our example, the CloudForms web interface is located at http://cloudforms.example.com.



2. Select Edit Registration.3. At the bottom of the page, enter your Red Hat Network's username and password to log into the

Red Hat Subscription Management service.

a. If the response is Customer Information Succesfully Saved, then you can proceed to thenext step.

b. If the response is Error 70, then do you do not have a subscription for CloudForms. ContactRed Hat to obtain that subscription, then try again.

4. On the page that next displays, select the checkbox next to the EVM Appliance, and then click onRegister.

Update the Platform

Now that your Red Hat subscription information has been successfully entered you can update theplatform with the latest Red Hat updates:

1. Wait for a few minutes for the registration to complete.2. Refresh the display.3. When you see a Platform Update Available message, update the platform as instructed.

You can now proceed to Configure CloudForms to Manage Providers on page 22.

Configure CloudForms to Manage Providers | 22


Configure CloudForms to Manage Providers

You can configure CloudForms to manage infrastructure and cloud providers. Procedures discussedinclude:

1. Configure the Infrastructure Provider Undercloud on page 222. Configure the Cloud Provider Overcloud on page 23

Configure the Infrastructure Provider Undercloud

To configure the Undercloud as an infrastructure provider, follow these procedures:

1. Add the Undercloud as an Infrastructure Provider on page 222. Ensure Network Access to Controllers on page 23

Add the Undercloud as an Infrastructure Provider

To add the Undercloud as an infrastructure provider:

1. Open the CloudForms web GUI.2. Navigate to Compute > Infrastructure > Providers > Configuration > Add New Infrastructure

Provider.3. Select OpenStack Platform Director, and enter the required information:

• Name — UnderCloudDellOSS• Type — OpenStack Platform Director• API Version — Keystone v2• Zone — Default

4. Go through the tabs in turn, entering the appropriate information, and clicking on Validate beforemoving to the next:

• Default Tab — UnderCloud

• Hostname — undercloud.example.com• API Port — 5000• Security Protocol — Non-SSL• Username — Undercloud username from stackrc on the Director Node.• Password — Undercloud password from stackrc on the Director Node. Execute the sudo

hiera admin_password command, if it is found in the file, to obtain the proper password.• Confirm Password — Undercloud password from stackrc on the Director Node.

• Events Tab

• Select AMPQ• Hostname — undercloud.example.com• API Port — 5672• Security Protocol — Non-SSL• Username — Generated for Rabbit by automation, and found on the Director Node in /etc/

rabbitmq/rabbitmq.config.• Password — Generated for Rabbit by automation, and found on the Director Node in /etc/

rabbitmq/rabbitmq.config.• RSA Key Pair Tab

• The heat-admin user's ssh keys.



1. Copy, via scp, from the Director Node's /home/osp_admin/.ssh/id_rsa file, to your bastionhost.

2. Upload it through the CloudForms web GUI.3. Click on Add.

Ensure Network Access to Controllers

The CloudForms VM may not be able to access the Controller nodes on vLAN 120. Instead, use the 190network.

To ensure network access to the Controller nodes:

1. Open the CloudForms web GUI.2. Navigate to Compute > Infrastructure > Any problematic node > Configuration > Edit.

Note: Problematic nodes have exclamation marks (!) in their icons, which indicateauthentication problems.

3. Note the IP address of the node (for example, 192.168.120.104). This is what you will change.4. From the Director Node, ssh into that node and note the IP address on the 190 network:

[osp_admin@director ~]$ ssh [email protected] login: Wed May 11 15:43:26 2016 from 192.168.120.61[heat-admin@tan-controller-1 ~]$ ip a | grep 19019: vlan190: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN inet 192.168.190.126/24 brd 192.168.190.255 scope global vlan190

5. Use the address from the 190 network (192.168.190.126 in this example) in the CloudForms web GUI.6. Validate the credentials.

a. If the credential validate, then click on Save.b. If they do not validate (the spinner does not stop), press [Esc], correct the information, and try

again.7. Click on Configuration > Perform Smart Analysis for the node.

a. The exclamation mark will eventually change to a check mark, indicating success.8. Repeat the process for all Controller nodes that display an exclamation mark instead of a check

mark.

Configure the Cloud Provider Overcloud

To configure the Overcloud as a cloud provider, follow these procedures:

1. Open RabbitMQ Ports on page 232. Add the Overcloud as a Cloud Provider on page 25

Open RabbitMQ Ports

CloudForms works with the OpenStack message queue to help interrogate systems. In our defaultconfiguration, RabbitMQ is not accessible by CloudForms.

To change RabbitMQ to listen on all Controller node interfaces:

1. On the Director Node, execute the following command:

Note: Your IP addresses will vary from the examples given.

$ for x in cntl0 cntl1 cntl2; do echo $x; ssh $x grep \ NODE_IP_ADDRESS /etc/rabbitmq/rabbitmq-env.conf; done



cntl0NODE_IP_ADDRESS=192.168.140.106cntl1NODE_IP_ADDRESS=192.168.140.108cntl2NODE_IP_ADDRESS=192.168.140.107

2. To change those settings, execute the following command:

$ for x in cntl0 cntl1 cntl2; do echo $x; ssh $x \ sudo sed -i '/^NODE_IP_ADDRESS/\cNODE_IP_ADDRESS=0.0.0.0' \ /etc/rabbitmq/rabbitmq-env.conf; done

cntl0cntl1cntl2

3. Ensure that the changes are correct by executing the following command:

$ for x in cntl0 cntl1 cntl2; do echo $x; ssh $x grep NODE_IP_ADDRESS /etc/rabbitmq/rabbitmq-env.conf; done

Note: The output will look exactly the same as the following example.

cntl0NODE_IP_ADDRESS=0.0.0.0cntl1NODE_IP_ADDRESS=0.0.0.0cntl2NODE_IP_ADDRESS=0.0.0.0

4. Connect via ssh to the first Controller node, and use Pacemaker Corosync System to restart theclustered RabbitMQ processes:

$ ssh cntl0

Last login: Thu May 26 15:05:59 2016 from 192.168.120.61[heat-admin@tan-controller-0 ~]$ sudo -i[root@tan-controller-0 ~]# pcs resource restart rabbitmqWarning: using rabbitmq-clone... (if a resource is a clone or master/slave you must use the clone or master/slave name)

It may take some time for pcs to restart RabbitMQ completely.5. Ensure that RabbitMQ is listening on all interfaces (*) by executing the following command:

Note: The output should indicate *:5672, and not a particular IP address.

$ for x in cntl0 cntl1 cntl2; do echo $x; ssh $x sudo ss -lntp | grep 5672; done

cntl0LISTEN 0 128 *:5672 *:* users:(("beam.smp",pid=8319,fd=19))LISTEN 0 128 *:35672 *:* users:(("beam.smp",pid=8319,fd=8))cntl1LISTEN 0 128 *:5672 *:* users:(("beam.smp",pid=7929,fd=17))LISTEN 0 128 *:35672 *:* users:(("beam.smp",pid=7929,fd=8))cntl2LISTEN 0 128 *:5672 *:* users:(("beam.smp",pid=8045,fd=20))LISTEN 0 128 *:35672 *:* users:(("beam.smp",pid=8045,fd=8))



Add the Overcloud as a Cloud Provider

To add the Overcloud as a cloud provider:

1. Open the CloudForms web GUI.2. Navigate to Compute > Clouds > Providers > Configuration > Add New Cloud Provider.3. Select OpenStack, and enter the required information:

• Name — OverCloudDellOSS• Type — OpenStack• API Version — Keystone v2• OpenStack Infra Provider — UnderCloudDellOSS• Zone — Default

4. Go through the tabs in turn, entering the appropriate information, and clicking on Validate beforemoving to the next:

• Default Tab — You can get all of these settings from the overcloudrc file on the Director Node.

• Hostname — overcloud.example.com• API Port — 5000• Security Protocol — Non-SSL• Username — OS_USERNAME from overcloudrc on the Director Node• Password — OS_PASSWORD from overcloudrc on the Director Node• Confirm Password — OS_PASSWORD from overcloudrc on the Director Node

• Events Tab

• Select AMPQ• Hostname — overcloud.example.com• API Port — 5672• Security Protocol — Non-SSL• Username — default_user=guest from /etc/rabbitmq/rabbitmq.conf on cntl0• Password — default_pass value from /etc/rabbitmq/rabbitmq.conf on cntl0• Confirm Password — default_pass value from /etc/rabbitmq/rabbitmq.conf on cntl0

5. Validate these credentials:

• Admin (Overcloud OpenStack admin user and password)• AMPQ (guest user and password)

6. Click on Add.

Red Hat CloudForms is now deployed in the Dell Red Hat OpenStack Cloud Solution.

Next Steps | 26


Next Steps

Now that CloudForms is deployed in the Dell Red Hat OpenStack Cloud Solution, follow theinstructions in the guide listed below to further integrate CloudForms with OpenShift:

• Integrating CloudForms 4.1 and OpenShift 3.2 in the Dell Red Hat OpenStack Cloud Solution -Version 5.0

Getting Help | 27


Getting Help

This appendix details contact and reference information for the Dell Red Hat® OpenStack CloudSolution with Red Hat OpenStack Platform.

Contacting Dell

For customers in the United States, call 800-WWW-DELL (800-999-3355).

Note: If you do not have an active Internet connection, you can find contact information onyour purchase invoice, packing slip, bill, or Dell product catalog.

Dell provides several online and telephone-based support and service options. Availability varies bycountry and product, and some services may not be available in your area. To contact Dell for sales,technical support, or customer service issues:

1. Visit dell.com/support.2. Click your country/region at the bottom of the page. For a full listing of country/region, click All.3. Click All Support from the Support menu.4. Select the appropriate service or support link based on your need.5. Choose the method of contacting Dell that is convenient for you.

References

Additional information can be obtained at http://www.dell.com/en-us/work/learn/openstack-cloud or by e-mailing [email protected].

If you need additional services or implementation help, please contact your Dell sales representative.

To Learn More

For more information on the Dell Red Hat® OpenStack Cloud Solution visit http://www.dell.com/learn/us/en/04/solutions/red-hat-openstack.

© 2014-2016 Dell Inc. All rights reserved. Trademarks and trade names may be used in this documentto refer to either the entities claiming the marks and names or their products. Specifications are correctat date of publication but are subject to availability or change without notice at any time. Dell and itsaffiliates cannot be responsible for errors or omissions in typography or photography. Dell’s Terms andConditions of Sales and Service apply and are available on request. Dell service offerings do not affectconsumer’s statutory rights.

Dell, the DELL logo, the DELL badge, and PowerEdge are trademarks of Dell Inc.

http://www.dell.com/support

http://www.dell.com/en-us/work/learn/openstack-cloud

mailto:[email protected]

http://www.dell.com/learn/us/en/04/solutions/red-hat-openstack

http://www.dell.com/learn/us/en/04/solutions/red-hat-openstack

Documents

Technical Guide – Deploying CloudForms 4.1 in the Dell Red Hat