OpenStack Documentation Team
Red Hat Enterprise Linux OpenStack
Platform 6
Deploying OpenStack: Enterprise
Environments (Red Hat Enterprise
Linux OpenStack Platform Installer)
Deploying Red Hat Enterprise Linux OpenStack Platform in an enterprise
environment
Red Hat Enterprise Linux OpenStack Platform 6 Deploying OpenStack:
Enterprise Environments (Red Hat Enterprise Linux OpenStack Platform
Installer)
Deploying Red Hat Enterprise Linux OpenStack Platform in an enterprise
environment
OpenStack Do cumentatio n Team
Red Hat Custo mer Co ntent Services
rho s-do [email protected] m
Co pyright © 20 15 Red Hat, Inc.
This do cument is licensed by Red Hat under the Creative Co mmo ns Attributio n-ShareAlike 3.0
Unpo rted License. If yo u distribute this do cument, o r a mo dified versio n o f it, yo u must pro vide
attributio n to Red Hat, Inc. and pro vide a link to the o riginal. If the do cument is mo dified, all Red
Hat trademarks must be remo ved.
Red Hat, as the licenso r o f this do cument, waives the right to enfo rce, and agrees no t to assert,
Sectio n 4 d o f CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shado wman lo go , JBo ss, MetaMatrix, Fedo ra, the Infinity
Lo go , and RHCE are trademarks o f Red Hat, Inc., registered in the United States and o ther
co untries.
Linux ® is the registered trademark o f Linus To rvalds in the United States and o ther co untries.
Java ® is a registered trademark o f Oracle and/o r its affiliates.
XFS ® is a trademark o f Silico n Graphics Internatio nal Co rp. o r its subsidiaries in the United
States and/o r o ther co untries.
MySQL ® is a registered trademark o f MySQL AB in the United States, the Euro pean Unio n and
o ther co untries.
No de.js ® is an o fficial trademark o f Jo yent. Red Hat So ftware Co llectio ns is no t fo rmally
related to o r endo rsed by the o fficial Jo yent No de.js o pen so urce o r co mmercial pro ject.
The OpenStack ® Wo rd Mark and OpenStack Lo go are either registered trademarks/service
marks o r trademarks/service marks o f the OpenStack Fo undatio n, in the United States and o ther
co untries and are used with the OpenStack Fo undatio n's permissio n. We are no t affiliated with,
endo rsed o r spo nso red by the OpenStack Fo undatio n, o r the OpenStack co mmunity.
All o ther trademarks are the pro perty o f their respective o wners.
Abstract
This guide explains ho w to install Red Hat Enterprise Linux OpenStack Platfo rm 6 o n Red Hat
Enterprise Linux in an enterprise enviro nment using the Red Hat Enterprise Linux OpenStack
Platfo rm Installer.
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents
Chapt er 1 . Int roduct ion Chapt er 2 . Requirement s
2.1. RHEL O p enStack Platfo rm Installer System Req uirements 2.2. Client Bro wser Req uirements
2.3. Ho st Req uirements
Chapt er 3. Inst alling t he RHEL O penSt ack Plat form Inst aller
3.1. Preco nfig uring the Netwo rk
3.2. Sub scrib ing to the Req uired Channels Using Sub scrip tio n Manag er 3.3. Running the Co nfig uratio n Scrip t
3.4. Prep aring the Installatio n Med ium 3.5. Co nfig uring a G ateway
Chapt er 4 . Planning your Environment
4.1. Ho sts 4.2. Netwo rking 4.3. Sto rag e
4.4. Dep lo yment Scenario s
Chapt er 5. Deployment Scenario 1 : Basic Environment
5.1. Disco vering Ho sts fo r a Basic Enviro nment 5.2. Creating a Dep lo yment fo r a Basic Enviro nment 5.3. Assig ning Ho sts to Dep lo yment Ro les
5.4. Co nfig uring Ho st Netwo rking 5.5. Co nfig uring External Brid g e
5.6 . Pro visio ning Red Hat Enterp rise Linux O p enStack Platfo rm 5.7. Mo nito ring Pro g ress o f the Dep lo yment
5.8 . Co mp leting Dep lo yment fo r a Basic Enviro nment
Chapt er 6 . Deployment Scenario 2 : Advanced Environment wit h NFS St orage
6 .1. Disco vering Ho sts fo r an Ad vanced Enviro nment 6 .2. Creating a Dep lo yment fo r an Ad vanced Enviro nment 6 .3. Assig ning Ho sts to Dep lo yment Ro les
6 .4. Co nfig uring Ho st Netwo rking 6 .5. Co nfig uring External Brid g e
6 .6 . Co nfig uring Fencing o n Hig h-Availab ility No d es
6 .7. Pro visio ning Red Hat Enterp rise Linux O p enStack Platfo rm 6 .8 . Mo nito ring Pro g ress o f the Dep lo yment
6 .9 . Co mp leting Dep lo yment fo r an Ad vanced Enviro nment
Chapt er 7 . Deployment Scenario 3: Advanced Environment wit h Red Hat Ceph St orage
7.1. Disco vering Ho sts fo r an Ad vanced Enviro nment 7.2. Creating a Dep lo yment fo r an Ad vanced Enviro nment 7.3. Assig ning Ho sts to Dep lo yment Ro les
7.4. Co nfig uring Ho st Netwo rking 7.5. Co nfig uring External Brid g e
7.6 . Mo d ifying Ad vanced Cep h Setting s
7.7. Co nfig uring Fencing o n Hig h-Availab ility No d es
7.8 . Pro visio ning Red Hat Enterp rise Linux O p enStack Platfo rm 7.9 . Mo nito ring Pro g ress o f the Dep lo yment
7.10 . Co mp leting Dep lo yment fo r an Ad vanced Enviro nment
3 4 4 5 5 8 8 9 10 17 18 2 0 21 22 25 26 2 7 27 29 34 36 37 37 38 39 4 2 42 44 49 51 52 52 54 54 56 59 59 6 1 6 6 6 8 6 9 6 9 71 73 73 75 T able of Cont ent s
. . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapt er 8 . Scaling t he Environment
8 .1. Disco vering a New Ho st fo r Scaling
8 .2. Assig ning the Ho st to an Existing Dep lo yment Ro le 8 .3. Co nfig uring Ho st Netwo rking
8 .4. Dep lo ying New Ho sts fo r Red Hat Enterp rise Linux O p enStack Platfo rm
Chapt er 9 . T roubleshoot ing
9 .1. Defining the Pro visio ning Pro cess
9 .2. Tro ub lesho o ting Issues when Build ing Ho sts 9 .3. Tro ub lesho o ting Issues when Co nfig uring Ho sts
Chapt er 1 0 . Next St eps Appendix A. Firewall Rules
Appendix B. New Deployment Set t ings
B.1. Netwo rk Co nfig uratio n Setting s B.2. Services Co nfig uratio n Setting s
Appendix C. Configuring t he RHEL O penSt ack Plat form Inst aller
C.1. Installatio n Med ia C.2. O p erating Systems C.3. Pro visio ning Temp lates C.4. Partitio n Tab les
C.5. Sub nets C.6 . Users
C.7. User G ro up s C.8 . Ro les
Appendix D. Revision Hist ory
7 8 78 79 8 0 8 0 8 2 8 2 8 3 8 4 8 6 8 7 8 8 8 8 8 8 9 2 9 2 9 4 9 7 9 9 10 0 10 1 10 2 10 4 1 0 6
Chapter 1. Introduction
The Red Hat Enterprise Linux OpenStack Platform installer is an application to manage the
installation, configuration, and scalability of OpenStack environments. The application achieves this through detecting bootable hosts and mapping OpenStack services to them through a web interface. This simplifies the process of installing and configuring Red Hat Enterprise Linux OpenStack
Platform while providing a means to scale in the future.
This guide provides an instruction set to guide you through all Red Hat Enterprise Linux OpenStack Platform installer processes, including:
Installing the Red Hat Enterprise Linux OpenStack Platform installer
Deploying Basic OpenStack environments using Nova networking and local storage
Deploying Advanced OpenStack environments using Neutron networking and Ceph storage Scaling your Red Hat Enterprise Linux OpenStack Platform environment
Troubleshooting Red Hat Enterprise Linux OpenStack Platform deployments
Note
For an overview of the OpenStack components and their interfaces, see the "Component Overview"(
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/).
Chapter 2. Requirements
This chapter outlines the main requirements for setting up an environment to provision Red Hat Enterprise Linux OpenStack Platform using the Red Hat Enterprise Linux OpenStack Platform
installer, including the requirements for setting up and accessing the installer itself, and the hardware requirements for hosts that installer provisions for OpenStack services.
2.1. RHEL OpenSt ack Plat form Inst aller Syst em Requirement s
A typical deployment of the Red Hat Enterprise Linux OpenStack Platform installer requires: A machine running Red Hat Enterprise Linux 7 to host the installer and its web-based user interface. For this machine, 8 GB of memory is recommended; a minimum of 4 GB memory is required.
Important
The installer's host machine requires a fully qualified domain name that satisfies the following criteria:
It must be a part of the same domain the installer uses for provisioning. This is because provisioned hosts communicate with the installer using the fully qualified domain name. The domain must be associated with the network the installer uses for provisioning. This is because the installer's DNS service assigns domain names to provisioned hosts.
It must not conflict with any existing domains. This is to avoid conflicts in name resolution.
A private network accessible to physical machines or virtual machines. The installer deploys the Red Hat Enterprise Linux OpenStack Platform components through this network. Disable any services such as DHCP, DNS, and PXE on this network. The installer uses its own DHCP, DNS, and PXE services and must avoid any conflicts with existing services.
Important
The installer's bare metal discovery service requires the network interface connected to this private network have a native (untagged/default) VLAN configuration. The installer does not detect VLAN-tagged interfaces.
Important
Network switches must support fallback if configuring the installer interface used for PXE in a network bond. Provisioning fails if bonding is activated on the switches themselves due to the lack of bond during PXE negotiation. If the switches used do not support a fallback mode, a dedicated non-bonding provisioning interface should be used.
A machine that is a member of the private network and that can act as a router or gateway to an external network. The machine that hosts the installer can perform this function if required. See
Section 3.5, “ Configuring a Gateway” for information on how to configure this machine to act as a gateway.
Your Customer Portal account details, which you use to subscribe your hosts to the relevant content channels, both for the installer and the deployed hosts. The main details needed include your user name, password, the ID of pools to attach, the names of channels to enable, and the details of any HTTP proxy you might use to connect to the internet.
2.2. Client Browser Requirement s
Users access the user interface through a web application hosted on the same machine as the installer. Use a supported browser to access this user interface. Browser support is divided into four levels:
Level 1: Fully supported, preferred browsers for ideal experience.
Level 2: Mostly supported. The user interface functions, but some design elements may not align correctly, the layout and user interface controls may not align correctly, and performance may be degraded.
Level 3: Design elements may not align correctly. Level 4: Unsupported.
The following table outlines the supported browsers and their level of support: T ab le 2.1. Su p p o rt ed Bro wsers
Bro wser Versio n Su p p o rt Level
Firefox 2.6 L3 Firefox 17, 18, 19, 20 L4 Firefox 21 L2 Firefox 22, 23, 24 L1 Firefox Latest L1 Chrome 19, 20 L4 Chrome 21, 27 L2 Chrome Latest L1 Internet Explorer 7, 8 L4 Internet Explorer 9, 10, 11 L2 Safari All L4
2.3. Host Requirement s
The following sections outline the main hardware requirements for hosts to provision RHEL
OpenStack Platform services. These requirements are categorized in accordance with the three core roles that hosts perform in a RHEL OpenStack Platform environment.
2.3.1. Cont roller Node Requirement s
Controller nodes are responsible for hosting the core services in a RHEL OpenStack Platform environment, such as the Horizon dashboard, the back-end database server, Keystone authentication, and High Availability services.
Pro cesso r
64-bit x86 processor with support for the Intel 64 or AMD64 CPU extensions. Memo ry
A minimum of 4 GB of RAM. Disk Sp ace
A minimum of 100 GB of available disk space is recommended.
Add additional disk space to this requirement based on the amount of space that you intend to make available to virtual machine instances. This figure varies based on both the size of each disk image you intend to create and whether you intend to share one or more disk images between multiple instances.
1 TB of disk space is recommended for a realistic environment capable of hosting multiple instances of varying sizes.
Net wo rk In t erf ace Card s
A minimum of 3 x 1 Gbps Network Interfaces.
2.3.2. Comput e Node Requirement s
Compute nodes are responsible for running virtual machine instances after they are launched. Compute nodes must support hardware virtualization. Compute nodes must also have enough memory and disk space to support the requirements of the virtual machine instances they host.
Pro cesso r
64-bit x86 processor with support for the Intel 64 or AMD64 CPU extensions, and the AMD-V or Intel VT hardware virtualization extensions enabled.
Memo ry
A minimum of 4 GB of RAM.
Add additional RAM to this requirement based on the amount of memory that you intend to make available to virtual machine instances.
Disk Sp ace
A minimum of 100 GB of available disk space is recommended.
Add additional disk space to this requirement based on the amount of space that you intend to make available to virtual machine instances. This figure varies based on both the size of each disk image you intend to create and whether you intend to share one or more disk images between multiple instances.
1 TB of disk space is recommended for a realistic environment capable of hosting multiple instances of varying sizes.
A minimum of 3 x 1 Gbps Network Interfaces.
2.3.3. Ceph St orage Node Requirement s
Ceph storage nodes are responsible for providing object storage in a RHEL OpenStack Platform environment.
Pro cesso r
64-bit x86 processor with support for the Intel 64 or AMD64 CPU extensions. Memo ry
Memory requirements depend on the amount of storage space. Ideally, use at minimum 1 GB of memory per 1 TB of hard disk space.
Disk Sp ace
Storage requirements depends on the amount of memory. Ideally, use at minimum 1 GB of memory per 1 TB of hard disk space.
Net wo rk In t erf ace Card s
A minimum of 1 Gbps Network Interfaces.
Important
The installer only implements some basic host configuration for Ceph Storage Nodes (OSD). Ceph Storage Nodes (OSD) require additional package installation and configuration to create a full Ceph Storage Cluster.
Chapter 3. Installing the RHEL OpenStack Platform Installer
The installer manages the provisioning of Red Hat Enterprise Linux OpenStack Platform components on a set of machines. It uses a web-based graphical user interface to provide these functions. Before using the RHEL OpenStack Platform installer, you must install the required packages and configure the application using the rhel -o sp-i nstal l er script.
Warning
Upgrading the Red Hat Enterprise Linux OpenStack Platform installer is not currently supported. To use the latest version of the installer, use a fresh installation.
Important
The role of the installer is to provision Red Hat Enterprise Linux OpenStack Platform environments and manage the life cycle of the hosts in that environment. After you have provisioned your environment, all additional configuration of Red Hat Enterprise Linux
OpenStack Platform components on hosts you have provisioned must be performed manually on those hosts. .
3.1. Preconfiguring t he Net work
This section provides some pre-installation advice regarding the network that the Red Hat Enterprise Linux OpenStack Platform installer uses to manage the environment.
Disable Net workManager
The rhel -o sp-i nstal l er script uses the netwo rk service instead of the Netwo rkManag er service. Disable Netwo rkManag er using the following commands:
# systemctl stop NetworkManager.service # systemctl disable NetworkManager.service
Open each interface configuration file on the system in a text editor. Interface configuration files are found in the /etc/sysco nfi g /netwo rkscri pts/ directory and have names of the form i fcfg -X where -X is replaced by the name of the interface.
In each file, set NM_C O NT R O LLED configuration key to no and the O N_BO O T configuration key to yes.
NM_CONTROLLED=no ONBOOT=yes
Enable the netwo rk service when complete. # systemctl start network.service # systemctl enable network.service
Your system now uses the netwo rk service to control networking instead of Netwo rkManag er.
Remove dnsmasq
The d nsmasq service is a controller for DNS and DHCP services. However, it can interfere with the installer's management of the DHCP. It is recommended to remove it from the installer's system.
# yum remove dnsmasq
This ensures the rhel -o sp-i nstal l er correctly configures the DHCP settings without any conflict with d nsmasq .
Configure DNS Resolut ion
The rhel -o sp-i nstal l er script configures a chosen network interface for provisioning
management services, including DNS resolution. However, other network interfaces on the installer host can overwrite these settings in the /etc/reso l v. co nf file if their P EER D NS is set to yes. Modify all /etc/sysco nfi g /netwo rk-scri pts/i fcfg -* files, except the one for the chosen provisioning management, and set the P EER D NS to:
PEERDNS=no
If you choose not to let the rhel -o sp-i nstal l er script configure your network interface, ensure the chosen provisioning management interface has DNS information set. For example, if your provisioning provisioning network interface is eth0 , edit the /etc/sysco nfi g /netwo rk-scri pts/i fcfg -eth0 file to include the following:
PEERDNS=yes
DNS1=[ip-address of rhel-osp installer host] DNS2=[ip address of dns forward entry in dhcp] Restart the netwo rk service when complete.
# systemctl restart network.service
This should populate the /etc/reso l v. cfg with the nameservers specified.
3.2. Subscribing t o t he Required Channels Using Subscript ion Manager
To install the RHEL OpenStack Platform installer, first register the host system using Red Hat Subscription Manager, and subscribe to the required channels.
Pro ced u re 3.1. Su b scrib in g t o t h e Req u ired Ch an n els Usin g Su b scrip t io n Man ag er 1. Register your system with the Content Delivery Network, entering your Customer Portal user
name and password when prompted:
# subscri pti o n-manag er reg i ster
2. Find entitlement pools containing the channels required to install the Red Hat Enterprise Chapt er 3. Inst alling t he RHEL O penSt ack Plat form Inst aller
# subscri pti o n-manag er l i st --avai l abl e | g rep -A8 "R ed Hat Enterpri se Li nux Server"
# subscri pti o n-manag er l i st --avai l abl e | g rep -A8 "R ed Hat Enterpri se Li nux O penStack P l atfo rm"
3. Use the pool identifiers located in the previous step to attach the R ed Hat Enterpri se Li nux 7 Server and R ed Hat Enterpri se Li nux O penStack P l atfo rm
entitlements:
# subscri pti o n-manag er attach --po o l = pool_id 4. Enable the required channels:
# subscri pti o n-manag er repo s --enabl e= rhel -7-server-rpms
# subscri pti o n-manag er repo s --enabl e= rhel -7-server-o penstack-6 . 0 -i nstal l er-rpms
# subscri pti o n-manag er repo s --enabl e= rhel -server-rhscl -7-rpms
3.3. Running t he Configurat ion Script
Run the rhel -o sp-i nstal l er command to install the RHEL OpenStack Platform installer application and configure the core parameters the installer uses to provision RHEL OpenStack Platform 6.0.
Note
The rhel -o sp-i nstal l er command automatically configures the required SELinux permissions and adds the required firewall rules to ip t ab les while preserving any existing firewall rules. See Appendix A, Firewall Rules for the list of firewall rules that the command configures.
Pro ced u re 3.2. In st allin g an d ru n n in g t h e Red Hat En t erp rise Lin u x O p en St ack Plat f o rm in st aller co n f ig u rat io n scrip t
1. Install the rhel-osp-installer package:
# yum i nstal l rhel -o sp-i nstal l er 2. Start the installation:
# rhel -o sp-i nstal l er
3. Enter the number for the network interface that the installer will use to provision RHEL OpenStack Platform, and press Enter:
Please select NIC on which you want Foreman provisioning enabled: 1. eth1
2. eth0 ?
Once you have chosen a network interface, the configuration script displays some network options to configure.
Pro ced u re 3.3. Co n f ig u rin g Net wo rk O p t io n s
1. Enter the number for the configuration option to change, and press Enter. T ab le 3.1. Net wo rkin g Set u p O p t io n s
O p t io n Descrip t io n
Netwo rk i nterface The network interface to use for the provisioning network. The default values of other networking options, such as the IP ad d ress and Netwo rk ad d ress, are automatically specified based on the network interface you select.
IP Ad d ress The IP address of the machine hosting the installer.
Netwo rk mask The network mask of the machine hosting the installer. The installer also uses this value to populate the network mask of the default subnet in the provisioning network. This means all provisioned hosts use this subnet too.
Netwo rk ad d ress The network address of the default subnet. The installer uses this address as the provisioning network. This address must be in CIDR format. For example, 19 2. 16 8. 1. 0 /24 .
Ho st g ateway The address of a machine that acts as a gateway for the machine hosting the installer.
D HC P rang e start The first address in the range of IP addresses that the installer can assign to machines on the provisioning network. This value is also used to populate the DHCP range start of the default subnet that the installer configures to act as the provisioning network.
D HC P rang e end The last address in the range of IP addresses that the installer can assign to machines on the provisioning network. This value is also used to populate the DHCP range end of the default subnet that the installer configures to act as the provisioning network.
D HC P G ateway The address of a machine that can act as a gateway for machines that the installer provisions. By default, the address of the machine hosting the installer is specified as the DHCP gateway. To use this machine as the default gateway, see
Section 3.5, “ Configuring a Gateway”. If aim to use a different machine to act as a gateway, edit this value and specify the address of a machine that can perform this function.
D NS fo rward er The address of a machine that can resolve IP addresses and host names. This value is also used to populate the primary DNS of the default subnet that the installer configures to act as the provisioning network.
D o mai n The name of the domain that the installer provides. The name of the domain must match the fully qualified domain name of the machine hosting the installer.
Fo reman UR L The address for accessing the user interface. By default, this value is set to the fully qualified domain name of the machine hosting the installer.
NT P sync ho st The address of an NTP server that the installer can use to synchronize the time on machines that it provisions.
T i mezo ne The timezone that the installer applies to machines that it provisions. Timezones must be in the format of an IANA time zone identifier such as Ameri ca/New_Y o rk or Asi a/T o kyo .
O p t io n Descrip t io n
2. Enter a new value, and press Enter.
3. When you have specified the preferred value for each configuration option, enter 1, and press Enter.
Examp le 3.1. Samp le Net wo rk Co n f ig u rat io n Screen Networking setup:
Network interface: 'eth1'
IP address: 'XX.XX.XX.XX' Network mask: 'XX.XX.XX.XX' Network address: 'XX.XX.XX.XX' Host Gateway: 'XX.XX.XX.XX' DHCP range start: 'XX.XX.XX.XX' DHCP range end: 'XX.XX.XX.XX' DHCP Gateway: 'XX.XX.XX.XX' DNS forwarder: 'XX.XX.XX.XX' Domain: 'mydomain.example.com'
Foreman URL: 'https://host.mydomain.example.com' NTP sync host: '0.rhel.pool.ntp.org'
Timezone: 'America/New_York' Configure networking on this machine: ✓
Configure firewall on this machine: ✓
The installer can configure the networking and firewall rules on this machine with the above configuration. Default values are populated from the this machine's existing networking configuration.
If you DO NOT want to configure networking please set 'Configure networking on this machine' to No before proceeding. Do this by selecting option 'Do not configure networking' from the list below. How would you like to proceed?:
1. Proceed with the above values 2. Change Network interface
3. Change IP address 4. Change Network mask 5. Change Network address 6. Change Host Gateway 7. Change DHCP range start 8. Change DHCP range end 9. Change DHCP Gateway 10. Change DNS forwarder 11. Change Domain
12. Change Foreman URL 13. Change NTP sync host 14. Change Timezone
15. Do not configure networking 16. Do not configure firewall 17. Cancel Installation
Important
The name of the domain must match that of the fully qualified domain name of the machine hosting the installer.
Important
By default, the address of the machine hosting the installer is specified as the DHCP gateway, which is the gateway provisioned hosts use. If you have not configured the machine hosting the installer to act as a gateway, you must edit this value and specify the address of a machine that can perform this function.
Once you complete the network configuration, the configuration script displays some authentication options to configure for client hosts.
Pro ced u re 3.4 . Co n f ig u rin g Clien t Au t h en t icat io n
1. Enter the number for the configuration option to change, and press Enter. T ab le 3.2. Clien t Au t h en t icat io n O p t io n s
O p t io n Descrip t io n
SSH publ i c key A public SSH key that is copied to machines that the installer provisions. This can be either the public key itself or a location to a file containing the public key.
R o o t passwo rd The password for the ro o t user on machines the installer provisions. The password must be at least eight characters in length. If you do not manually specify a password, a random password is generated.
2. Enter a new value, and press Enter.
3. When you have specified either a SSH public key or a root password, enter 1, and press Enter.
Examp le 3.2. Samp le Clien t Au t h en t icat io n Co n f ig u rat io n Screen Configure client authentication
SSH public key: ''
Root password: '*********'
Please set a default root password for newly provisioned machines. If you choose not to set a password, it will be generated randomly. The password must be a minimum of 8 characters. You can also set a public ssh key which will be deployed to newly provisioned machines.
How would you like to proceed?:
1. Proceed with the above values 2. Change SSH public key
3. Change Root password
4. Toggle Root password visibility
Once you have completed the client authentication options, the configuration script starts installing and configuring the installer components. This part takes a few minutes to complete.
When complete, the configuration script asks the location of your base operating system installation medium.
Pro ced u re 3.5. Co n f ig u rin g In st allat io n Med iu m Det ails 1. Enter 1, and press Enter.
T ab le 3.3. In st allat io n Med ia O p t io n s
O p t io n Descrip t io n
Set R HEL repo path (http o r https UR L)
The address of a Red Hat Enterprise Linux 7.2 installation tree. The path must end in the directory that contains directories such as i so l i nux, Li veO S, and repo d ata. This option is used to populate the default installation media entry that the installer uses to install the base operating system on machines that it provisions.
2. Enter the address of a Red Hat Enterprise Linux Server 7.2 installation tree that the machine hosting the installer can access through a web server, and press Enter.
Important
The installer requires a Red Hat Enterprise Linux 7 kickstart tree. If you do not have one available, create one on the installer using a Red Hat Enterprise Linux 7 ISO or DVD. Follow the steps in Section 3.4, “ Preparing the Installation Medium” after the rhel -o sp-i nstal l er c-ompletes. F-or the m-oment, enter the f-oll-owing as the RHEL rep-o URL:
http: //www. exampl e. co m: 8120 /R HEL7
Make sure to replace www. exampl e. co m with the hostname of your installer host.
3. Enter 2, and press Enter.
Examp le 3.3. Samp le In st allat io n Med iu m Co n f ig u rat io n Screen
Now you should configure installation media which will be used for provisioning.
Note that if you don't configure it properly, host provisioning won't work until you configure installation media manually.
1. Set RHEL repo path (http or https URL): http://www.example.com:8120/RHEL7
2. Proceed with configuration
3. Skip this step (provisioning won't work)
Once you set the installation media, the configuration script asks for your subscription management details.
Pro ced u re 3.6 . Co n f ig u rin g Su b scrip t io n Man ag emen t Det ails
1. Enter the number for the configuration option to change, and press Enter. T ab le 3.4 . Su b scrip t io n Man ag er O p t io n s
O p t io n Descrip t io n
Subscri pti o n manag er username
The username of a Customer Portal account that can be used to register machines that the installer provisions with the Content Delivery Network.
Subscri pti o n manag er passwo rd
A password that can be used to authenticate the above account.
C o mma o r space separated
repo si to ri es
A comma or space separated list of repositories to enable on machines that the installer provisions. By default, this field contains the main repositories that provide the packages required to install Red Hat Enterprise Linux OpenStack Platform components.
Subscri pti o n manag er po o l (reco mmend ed )
The ID of an entitlement pool to attach to machines that the installer provisions. Only a single entitlement pool ID can be specified, and if no entitlement pool ID is specified, the installer attempts to auto-attach the required entitlement pool.
Subscri pti o n manag er pro xy ho stname
The host name of a machine that can be used as a Subscription Manager proxy.
Subscri pti o n manag er pro xy po rt
The port by which to connect with the Subscription Manager proxy.
Subscri pti o n manag er pro xy username
A username by which to connect with the Subscription Manager proxy.
Subscri pti o n manag er pro xy passwo rd
The password by which the authenticate the above username.
2. Enter a new value, and press Enter.
3. When you have specified the preferred value for each configuration option, enter 9 , and press Enter.
Examp le 3.4 . Samp le Su b scrip t io n Man ag emen t Co n f ig u rat io n Screen Enter your subscription manager credentials:
1. Subscription manager username: 2. Subscription manager password:
3. Comma separated repositories:
common-rpms rhel-ha-for-rhel-7-server-rpms 4. Subscription manager pool (recommended): 5. Subscription manager proxy hostname: 6. Subscription manager proxy port: 7. Subscription manager proxy username: 8. Subscription manager proxy password: 9. Proceed with configuration
10. Skip this step (provisioning won't subscribe your machines)
Note
The value for the Subscription Manager pool must be in the format of a Subscription Manager entitlement pool ID. Moreover, you can only specify a single entitlement pool ID. If you leave the value for this configuration item blank, the installer attempts to auto-attach the required entitlements on systems it provisions.
Important
If you choose not to specify your Subscription Manager account details in this step, you will not be able to provision RHEL OpenStack Platform unless you manually configure an operating system entry with the required details through the installer's user interface. The RHEL OpenStack Platform installer configuration is complete, and the entries required to
provision RHEL OpenStack Platform are automatically generated based on the details you provided. After the configuration is complete, the script displays the user name and a randomly generated password for the default administrative user account. The script also displays the address for accessing the user interface.
Examp le 3.5. Samp le Co mp let io n Screen Success!
* Foreman is running at https://www.example.com
Initial credentials are admin / nziESrtcuNVFG79z
* Foreman Proxy is running at https://www.example.com:8443 * Puppetmaster is running at port 8140
The full log is at /var/log/rhel-osp-installer/rhel-osp-installer.log
Important
It is recommended to login immediately with the initial credentials and change the password for the ad mi n user.
Log into the installer and navigate to Ad min User → My acco u n t . Change the P asswo rd , Veri fy it, and click Submi t.
3.4 . Preparing t he Inst allat ion Medium
The installer requires an installation medium. An installation medium is a source of files the installer uses to install the base operating system on a machine when you provision RHEL OpenStack Platform, and must be in the format of a Red Hat Enterprise Linux 7.2 installation tree.
If you do not have an installation medium already setup, create your own web server on the installer host to store and share Red Hat Enterprise Linux 7 installation medium.
Important
This procedure must be performed on the installer host after completing the rhel -o sp-i nstal l er confsp-iguratsp-ion scrsp-ipt. Thsp-is sp-is because the rhel -o sp-sp-i nstal l er scrsp-ipt wrsp-ites over any existing httpd settings with its own configuration during the installation process. This procedure modifies these settings after rhel -o sp-i nstal l er writes its own httpd configuration.
Pro ced u re 3.7. Prep arin g an In st allat io n Med iu m
1. Go to https://access.redhat.com, and log in to the Red Hat Customer Portal using your customer account details.
2. Click Do wn lo ad s in the menu bar.
3. Click R ed Hat Enterpri se Li nux to access the product download page. 4. Click R HEL 7. 2 Bi nary D VD .
5. Create a temporary directory into which to mount the ISO file: # mkdir /RHEL7
6. Mount the ISO file in the temporary directory:
# mount -t iso9660 -o loop rhel-server-7.2-x86_64-dvd.iso /RHEL7 7. Copy the contents of the temporary directory to the directory in which to store the files for the
installation medium:
# cp -dpR /RHEL7 /var/www/html/. 8. Unmount the ISO file:
# umount /RHEL7
9. Remove the temporary directory in which you mounted the ISO file: # rmdir /RHEL7
10. Set the permissions for the installation medium:
11. Create a new file at /etc/httpd /co nf. d /med i um. co nf and add the following configuration to it: Listen 8120 NameVirtualHost *:8120 <VirtualHost *:8120> DocumentRoot /var/www/html/ ServerName www.example.com <Directory "/var/www/html/">
Options All Indexes FollowSymLinks Order allow,deny
Allow from all </Directory> </VirtualHost>
This exposes an accessible location on port 8120 (unassigned port) of the web server, which contains the R HEL7 folder with the installation medium.
12. Add a rule to your firewall configuration to allow access to port 8120, then restart the firewall: # iptables I INPUT 1 p tcp m multiport ports 8120 m comment --comment "8120 accept - medium" -j ACCEPT
# iptables-save > /etc/sysconfig/iptables # systemctl restart iptables.service 13. Allow HTTP access for port 8120 in SELinux:
# semanage port -a -t http_port_t -p tcp 8120 14. Restart your web server:
# systemctl restart httpd.service
The installation medium is now available for the Red Hat Enterprise Linux OpenStack Platform installer to access. Test access to the installation medium by navigating to
http: //www. exampl e. co m: 8120 /R HEL7/, which displays a listing of Red Hat Enterprise Linux 7 files and folders.
3.5. Configuring a Gat eway
Configure the machine hosting installer to act as a gateway so traffic from the private provisioning network routes to a network interface with external connectivity.
Pro ced u re 3.8. Co n f ig u rin g a G at eway
1. Log into the machine hosting the installer as the root user.
2. Edit /etc/sysctl . co nf and change the value of net. i pv4 . i p_fo rward to 1: net. i pv4 . i p_fo rward = 1
# sysctl -p
4. Enable IP masquerading:
# i ptabl es -t nat -I P O ST R O UT ING 1 -o [if_name] -j MASQ UER AD E # i ptabl es -I FO R WAR D 1 ! -s [XX.XX.XX.XX/XX] -j D R O P
# i ptabl es -I FO R WAR D 1 -d [XX.XX.XX.XX/XX] -j AC C EP T # i ptabl es -I FO R WAR D 1 -s [XX.XX.XX.XX/XX] -j AC C EP T
[if_name]: The name of the network interface to which to forward network traffic. You must specify the name of the network interface that will not be used for the private provisioning network.
[XX.XX.XX.XX/XX]: The network address of the private provisioning network that the installer defines. You must specify this address using CIDR notation. For example, XX. 0 . 0 . 0 /8, XX. XX. 0 . 0 /16 , or XX. XX. XX. 0 0 /24 .
5. Save the changes to the firewall:
# i ptabl es-save > /etc/sysco nfi g /i ptabl es 6. Restart networking:
# systemctl restart netwo rk. servi ce
The new firewall rules routes the traffic from the private provisioning network to a network interface with external network connectivity, which allows machines on that network to access resources on other networks.
Chapter 4. Planning your Environment
The Red Hat Enterprise Linux OpenStack Platform installer maps OpenStack services to hosts in your environment and installs these services to their assigned hosts. This includes various options for high-availability controllers, Neutron or Nova networking, and a choice of messaging service. A deployment also provides specific parameters to customize each service. This provides a mechanism to define all aspects of an OpenStack environment and help scale the environment in the future. Prior to creating a deployment, plan how your environment looks so that you can correctly define the various host roles and services.
The following diagram outlines the topology of a sample deployment, which this chapter examines in greater detail:
Fig u re 4 .1. Samp le Dep lo ymen t T o p o lo g y
4 .1. Host s
Before you create a deployment, assign a role to each host and ensure each host meets the requirements set in Section 2.3, “ Host Requirements”.
The RHEL OpenStack Plaform installer uses four roles: Co n t ro ller
Provides key services such as the MySQL database for storing data about your environment, Horizon, Keystone, and Glance.
Co mp u t e
A host that acts as a hypervisor, providing the processing capabilities required for running virtual machines in the environment. You can add more Compute nodes to your
environment at any time by assigning additional hosts to this deployment role and repeating the provisioning process; the installer ignores all hosts that have already been provisioned and provisions only the new host.
Cep h St o rag e No d e ( O SD)
A generic Red Hat Enterprise Linux 7.2 host that can be manually configured after deployment to act as a Ceph storage server node. This deployment role is optional. G en eric RHEL 7
A generic Red Hat Enterprise Linux 7.2 host that can be manually configured after deployment to provide services not defined by any of the pre-existing deployment roles. This deployment role is optional.
In Figure 4.1, “ Sample Deployment Topology”, there are seven hosts in the deployment. The server icon at the top of the diagram represents the installer. The server icon beneath the installer represents controller nodes. Because this deployment uses high availability, there are three hosts assigned to this role so that the environment can continue to function in the event of a failure on any of the three nodes. The three server icons directly beneath the controller nodes represent compute nodes. The first two compute nodes were added when the RHEL OpenStack Platform environment was
provisioned. The third compute node, C o mpute N, represents additional compute nodes that can be added to the environment after it has been provisioned to enable horizontal scaling. The final server icon in the diagram represents a Ceph OSD node.
4 .2. Net working
It is important to plan what networking type to use and the subnets in your environment so that you can properly map services and hosts to correctly communicate with each other.
The installer providers two different networking options: No va
This is the legacy networking type where the Compute nodes manage IP forwarding, bridges, and VLANs.
Neu t ro n
This is the newer networking service that operates autonomously and manages software-based networks, static and floating IP addresses, and DHCP. The installer maps and deploys this service onto each Controller node in a RHEL OpenStack Plaform environment.
The installer also provides functions to map different services to different subnets. For example, the hosts in Figure 4.1, “ Sample Deployment Topology” communicate with each other and with external networks over the four following subnets:
The green subnet represents the provisioning network that the installer uses for provisioning and configuring hosts. This network carries traffic between the installer and the hosts in the
deployment. This is the network that the installer uses to boot hosts using PXE, and to set up and configure hosts when you provision a RHEL OpenStack Platform environment. While this network traffic type is carried over a dedicated subnet in this deployment, this network traffic type can be shared with any of the network traffic types carried by the blue network outlined below. The subnet that carries this network traffic type must be assigned to every host in the deployment.
The dark blue subnet represents a private network that carries network traffic between the nodes in a RHEL OpenStack Platform environment. This network carries management, cluster
management, administrative API, storage, and storage clustering network traffic. The subnet that carries these network traffic types must be assigned to every host in the deployment.
The light blue subnet represents a public network that carries network traffic between instances in the RHEL OpenStack Platform environment and external networks. This network provides external network connectivity to virtual machines. A dedicated subnet must be created to carry this type of network traffic. The subnet that carries this network traffic type is only assigned to controller nodes.
This network also allows the installer to communicate with external network resources such as the Content Delivery Network. It is configured manually on the machine hosting the installer. See
Section 3.5, “ Configuring a Gateway” for more information. All scenarios in this guide require three networks:
A network for the installer's provisioning network A network for OpenStack services
A network for external access
The initial configuration of the installer already contains a subnet entry for the provisioning network (10 . 1. 1. 0 /24 ). Thie following procedures show how to map networks for an External subnet (19 2. 16 8. 1. 0 /24 ) and OpenStack services (10 . 1. 1. 0 /24 ).
Important
An incompatibility between Modular Layer 2 Population and Layer 3 High Availability plugins means only one network configuration plugin should be used. The installer automatically configures Layer 3 High Availability (l 3_ha) for use if Layer 2 Population (l 2_po pul ati o n) is disabled. Likewise, if Layer 2 Population is enabled, the Layer 3 High Availability is
disabled.
4 .2.1. Creat ing an Ext ernal Subnet
The following procedure maps the external network (19 2. 16 8. 1. 0 /24 ) for provisioned hosts to use.
Pro ced u re 4 .1. Creat in g an Ext ern al Su b n et
2. Click New Subnet.
3. Configure general subnet details:
a. Enter a name for the subnet (e.g. External ) in the Name field.
b. Enter the network address of the subnet (e.g. 19 2. 16 8. 1. 0 ) in the Netwo rk ad d ress field.
c. Enter the network mask for the subnet (e.g. 255. 255. 255. 0 ) in the Netwo rk mask field.
d. Enter the address of a gateway (e.g. 19 2. 16 8. 1. 1) in the G ateway address field. e. Enter the address of the primary DNS server, if any, in the P ri mary D NS server
field.
f. Enter the address of the secondary DNS server, if any, in the Seco nd ary D NS server field.
g. Select No ne as IP address management source from the IP AM list. This lets the external networks' DHCP server take care of the IP management.
h. Optionally, enter the ID of a VLAN for the subnet.
i. Select D HC P as the default boot mode for interfaces assigned to the subnet from the Bo o t mo d e list.
4. Configure domain membership: a. Click D o mai ns.
b. Check all domains for which the subnet is a member.
Note
This is an optional step and if you need to add the domain for your external network, you can do so later by navigating to In f rast ru ct u re → Do main s. 5. Click the C apsul es tab to view the capsule settings. A capsule acts as a proxy for certain
installer services, such as DHCP, TFTP, and DNS.
The capsule settings are only required for the d efaul t provisioning subnet. This is because the installer uses this subnet for host provisioning and deployment of Red Hat OpenStack Platform services. Any new subnets added to the installer do not require capsule settings. 6. Click Submi t.
You now have an external subnet mapping to use in your RHEL OpenStack Platform environment.
4 .2.2. Creat ing an OpenSt ack Services Subnet
The following procedure maps the OpenStack services network (10 . 1. 2. 0 /24 ) for provisioned hosts to use.
1. From the title bar in the main screen of the user interface, click In f rast ru ct u re → Su b n et s. 2. Click New Subnet.
3. Configure general subnet details:
a. Enter a name for the subnet (e.g. O penStack Servi ces) in the Name field.
b. Enter the network address of the subnet (e.g. 10 . 1. 2. 0 ) in the Netwo rk ad d ress field.
c. Enter the network mask for the subnet (e.g. 255. 255. 255. 0 ) in the Netwo rk mask field.
d. Enter the address of a gateway (e.g. 10 . 1. 2. 1) in the G ateway address field. e. Enter the address of the primary DNS server, if any, in the P ri mary D NS server
field.
f. Enter the address of the secondary DNS server, if any, in the Seco nd ary D NS server field.
g. Select Internal D B as IP address management source from the IP AM list. The installer automatically assigns IP addresses to hosts.
h. Select the default boot mode for interfaces assigned to the subnet from the Bo o t mo d e list. This sets the boot protocol for client network interfaces. Select Stati c to manually assign IP address through the installer's IPAM Internal Database option. 4. Configure domain membership:
a. Click the D o mai ns tab.
b. Check all domains for which the subnet is a member.
Note
This is an optional step and if you need to add the domain for your external network, you can do so later by navigating to In f rast ru ct u re → Do main s. 5. Click the C apsul es tab to view the capsule settings. A capsule acts as a proxy for certain
installer services, such as DHCP, TFTP, and DNS.
The capsule settings are only required for the d efaul t provisioning subnet. This is because the installer uses this subnet for host provisioning and deployment of Red Hat OpenStack Platform services. Any new subnets added to the installer do not require capsule settings. 6. Click Submi t.
You now have a OpenStack services subnet mapping to use in your RHEL OpenStack Platform environment.
4 .3. St orage
The installer provides several options for image (Glance) and block (Cinder) storage services:
Local storage on the Controller host. Local storage is only available for environments with one Controller node. This means environments using local storage cannot have a highly available group of Controller nodes.
NFS storage. This requires a host or NAS storage unit with an NFS server.
Red Hat Ceph Storage nodes. If planning to use Red Hat Ceph Storage, you can use the installer's Ceph Storage Node (OSD) deployment role for creating nodes in a Ceph Storage Cluster.
Important
The installer only implements some basic host configuration for Ceph Storage Nodes (OSD). Ceph Storage Nodes (OSD) require additional package installation and configuration to create a full Ceph Storage Cluster.
EqualLogic SAN storage (Cinder storage only) NetApp storage (Cinder storage only)
In Figure 4.1, “ Sample Deployment Topology”, the environment is using a Ceph storage node.
4 .4 . Deployment Scenarios
You can customize many of the environment features to suit your needs, but to provide examples of how these features are deployed, this guide presents two deployment scenarios:
Basic En viro n men t - See Chapter 5, Deployment Scenario 1: Basic Environment
Ad van ced En viro n men t wit h NFS St o rag e - See Chapter 6, Deployment Scenario 2: Advanced Environment with NFS Storage
Ad van ced En viro n men t wit h Cep h St o rag e - See Chapter 7, Deployment Scenario 3: Advanced Environment with Red Hat Ceph Storage
The following table highlights the key differences in these scenarios:
Basic En viro n men t Scen ario
Ad van ced En viro n men t Scen ario wit h NFS St o rag e
Ad van ced En viro n men t Scen ario wit h Red Hat Cep h St o rag e
Total Hosts 3 6 9
Host Roles 1 Controller
2 Compute 3 Controller 3 Compute 3 Controller 3 Compute 3 Ceph
Networking Type Nova Neutron Neutron
Total Subnets 3 3 3
Image Storage (Glance)
Local NFS Ceph
Chapter 5. Deployment Scenario 1: Basic Environment
The object of this deployment scenario is to create a basic Red Hat Enterprise Linux OpenStack Platform environment using the following specifications:
Three nodes:
One Controller node Two Compute nodes Nova networking
Three networks:
A network for the installer's provisioning network (This example uses 10 . 1. 1. 0 /24 ) A network for OpenStack services (This example uses 10 . 1. 2. 0 /24 )
A network for external access (This example uses 19 2. 16 8. 1. 0 /24 ) Local Controller storage for Glance
Local Controller storage for Cinder
5.1. Discovering Host s for a Basic Environment
The basic environment scenario requires three hosts to provision as Red Hat Enterprise Linux OpenStack Platform nodes. The installer initially discovers these hosts through a PXE-based
discovery service. Users run a PXE boot on their bare metal hosts over the provisioning subnet (e.g. 10 . 1. 1. 0 /24 ). The installer automatically includes them in the list of available hosts for
provisioning.
Pro ced u re 5.1. Ad d in g a Ho st via Disco very
1. Start the host and elect to start over the network from the boot options menu. This starts the host using the PXE service the installer provides.
2. Select Fo reman D i sco very from the P XE bo o t options menu. The host starts into the Fo reman D i sco very screen and is automatically registered in the installer.
Fig u re 5.1. T h e Fo reman Disco very Screen
3. Log in to the user interface and confirm that the host has been registered: a. Click Ho st s → Disco vered h o st s.
b. Click the name of the newly registered host to open the details page for the host, and review the details.
Fig u re 5.2. T h e Disco vered Ho st Det ails Pag e
The host is automatically included in the list of unassigned hosts when you assign hosts to a deployment. The host is also automatically added to the d i sco very environment, which is the default Puppet environment for discovered hosts. This environment acts as a holding area that identifies hosts that have not yet been provisioned.
Note
All network interfaces on the discovered host are active. However, DNS is only active on the interface the installer defines as the primary network interface. Make sure to use the
provisioning network for the primary network interface when provisioning your host. Alternatively, set the fo reman. url and fo reman. i p parameters for each host before provisioning.
5.2. Creat ing a Deployment for a Basic Environment
This process creates a deployment for provisioning a basic RHEL OpenStack Platform environment. This process runs through the relevant options for this environment. For more information on the options available for configuring networking and services, see Appendix B, New Deployment Settings. To start the creation of a new deployment, navigate to O p en St ack In st aller → New d ep lo ymen t . The D epl o yment Setti ng s page requires some initial settings for your basic environment.
Pro ced u re 5.2. Co n f ig u rin g Dep lo ymen t Set t in g s
1. Enter a name for the deployment in the Name field. For example, Basi c D epl o yment. 2. Enter a description in the D escri pti o n field.
3. Select No va Netwo rk in the Netwo rki ng section.
5. Ensure R ed Hat Enterpri se Li nux O penStack P l atfo rm 6 wi th R HEL 7 is selected in the P l atfo rm section.
6. Select G enerate rand o m passwo rd fo r each servi ce in the Servi ce P asswo rd section to generate a random password for each service, or select Use si ng l e passwo rd fo r al l servi ces and enter a password in the P asswo rd and C o nfi rm fields to set the same password for all services.
7. Optionally, enter a list of custom repositories in the C usto m repo s text area. Multiple custom repositories must be added on separate lines, and each custom repository must take the form of a base URL.
8. Click Next.
Fig u re 5.3. T h e Dep lo ymen t Set t in g s st ep
The Netwo rk C o nfi g urati o n page maps OpenStack's network traffic types to the subnets in your environments.
Pro ced u re 5.3. Co n f ig u rin g Net wo rk T raf f ic
1. Drag the External network traffic type onto the External subnet (e.g. 19 2. 16 8. 1. 0 /24 ) created in Section 4.2.1, “ Creating an External Subnet”.
2. Drag the T enant, Manag ement, C l uster Manag ement, Ad mi n AP I, P ubl i c AP I, Sto rag e, and Sto rag e C l usteri ng network traffic types onto the O penStack Servi ces subnet (e.g. 10 . 1. 2. 0 /24 ) created in Section 4.2.2, “ Creating an OpenStack Services Subnet”.
3. Leave the P ro vi si o ni ng /P XE network traffic type in the d efaul t subnet (e.g. 10 . 1. 1. 0 /24 ).
4. Click Next.
Fig u re 5.4 . T h e Net wo rk Co n f ig u rat io n st ep
Note
By default, all network traffic types except External and T enant are assigned to the default subnet. The External network traffic type cannot be assigned to the same subnet as other network traffic types and requires a dedicated subnet for this network traffic type. Drag and drop network traffic types to subnets as required, or to the Avai l abl e Netwo rk T raffi c T ypes box to disable optional network traffic types.
The Servi ces O vervi ew page provides an opportunity to review the list of services to be provisioned. Click Next to move to the next page.
Fig u re 5.5. T h e Services O verview st ep
The Servi ces C o nfi g urati o n page provides options to configure OpenStack's Nova, Glance, and Cinder services.
Pro ced u re 5.4 . Co n f ig u rin g Service O p t io n s 1. Enter the following options for No va:
a. Select Fl at wi th D HC P as the T enant Netwo rk T ype. This enables the Compute nodes to control the IP assignment for VM instances through d nsmasq .
b. Enter a Fl o ati ng IP rang e fo r external netwo rk using CIDR notation (e.g. 19 2. 16 8. 1. 0 /24 ). The external network you specified previously acts as this network.
c. Enter a Fi xed IP rang e fo r tenant netwo rks using CIDR notation (e.g. 10 . 1. 2. 0 /24 ).
Fig u re 5.6 . No va co n f ig u rat io n o p t io n s 2. Select the following options for G l ance:
a. Select Lo cal Fi l e from the C ho o se D ri ver Backend section. This enables local storage for the Glance service.
Fig u re 5.7. G lan ce co n f ig u rat io n o p t io n s
a. Check LVM in the C ho o se D ri ver Backend section. This enables local storage for the Cinder service.
Fig u re 5.8. Cin d er co n f ig u rat io n o p t io n s 4. Click Submi t.
This completes the deployment creation process. The next step in the creation of the basic environment involves assigning the discovered hosts to specific deployment roles.
5.3. Assigning Host s t o Deployment Roles
To provision RHEL OpenStack Platform using a deployment, you must assign hosts you added through discovery to roles in the deployment. Assigning a host to a role automatically populates configuration options for that host, such as the operating system entry, Subscription Manager details, and puppet modules to install on the host.
A basic environment requires hosts assigned to the following roles: One Controller node
Two Compute nodes
Assign hosts you added to the installer to one of the roles in a deployment. Pro ced u re 5.5. Assig n in g Ho st s t o Dep lo ymen t Ro les
1. Click O p en St ack In st aller → Dep lo ymen t s.
2. Click the name of the deployment to which to assign hosts to open the details page for that deployment.
Fig u re 5.9 . T h e d ep lo ymen t d et ails p ag e
3. In the D epl o yment R o l es section, click + for a deployment role to display the Unassi g ned Ho sts section for that deployment role:
Co n t ro ller
Provides key services such as the MySQL database for storing data about your environment, Horizon, Keystone, and Glance. Assign one host to this role for the basic deployment scenario.
Co mp u t e
A host that acts as a hypervisor, providing the processing capabilities required for running virtual machines in the environment. You can add more Compute nodes to your environment at any time by assigning additional hosts to this deployment role and repeating the provisioning process; the installer ignores all hosts that have already been provisioned and provisions only the new host. Assign two hosts to this role for the basic deployment scenario.
Cep h St o rag e No d e ( O SD)
A generic Red Hat Enterprise Linux 7.2 host that can be manually configured after deployment to act as a Ceph storage server node. This deployment role is optional. Assign no hosts to this role for the basic deployment scenario.
G en eric RHEL 7
A generic Red Hat Enterprise Linux 7.2 host that can be manually configured after deployment to provide services not defined by any of the pre-existing deployment roles. This deployment role is optional. Assign no hosts to this role for the basic deployment scenario.
4. Select the check box for hosts in the Unassi g ned Ho sts section.
5.4 . Configuring Host Net working
After you assign a host to a deployment role in a deployment, you can configure the network traffic that each network interface on the host carries. Network traffic types are divided amongst subnets in accordance with the options you select when you create a deployment.
Pro ced u re 5.6 . Co n f ig u rin g Net wo rkin g o n a Ho st 1. Click the Ho sts tab.
2. Click the Assi g ned sub-tab.
3. Check a host, then click C o nfi g ure Netwo rks.
4. Drag and drop subnets between the sections for network interfaces to change the network traffic carried by those interfaces.
Fig u re 5.10. T h e Co n f ig u re Net wo rks Screen
5. Optionally, configure a bond between two network interfaces:
a. Click the bonding button for a network interface and click the name of a network interface to bond the two network interfaces.
6. Click D o ne.
5.5. Configuring Ext ernal Bridge
We also need to define our external bridge for the OpenStack deployment. This bridge is usually named br-ex. Use the following procedure to set this value.
1. Click the Ad vanced C o nfi g urati o n tab. 2. Click the Ed i t button.
3. Choose the Neutro n service.
4. Scroll to the External netwo rk bri d g e field and enter br-ex. 5. Click the Appl y button.
You have now defined the external bridge for your deployment.
5.6. Provisioning Red Hat Ent erprise Linux OpenSt ack Plat form
When you are ready to provision the RHEL OpenStack Platform environment, click D epl o y to open the deployment confirmation screen.
Fig u re 5.11. T h e d ep lo ymen t co n f irmat io n screen
Note
Clicking D epl o y registers the nodes and consumes entitlements. If you perform multiple deployments, you may need to first remove the existing environment from Subscri pti o n Manag er, if applicable.
Confirm the OpenStack services to be provisioned and click D epl o y.
Hosts assigned to roles in the deployment are moved to the pro d ucti o n environment, which contains the Puppet classes required to provision RHEL OpenStack Platform. The hosts are provisioned in accordance with the role to which they are assigned in the deployment and the deployment screen shows the progress of provisioning.
5.7. Monit oring Progress of t he Deployment
There are several methods to monitor the progress of your deployment. This section gives a high level overview of each of these methods.
Progress Bar
The Progress Bar on the deployment screen provides an overall indicator of the deployment progress, including the percentage of completion for the different node types deployed.
T asks
The T asks page displays a list of details about current tasks being run by the installer. You can access the T asks page at any time from anywhere in the user interface by clicking Mo n it o r → T asks. You can also access the task for your deployment by clicking Sho w mo re d etai l s under the progress bar.
The T asks page is useful for indentifying specific progress on your deployment including any errors that have stopped your deployment.
Dynflow Console
The D ynfl o w C o nso l e shows the subtasks for a particular task and the progress on each. This can include subtasks such as building the host's operating system, or deployment and configuration of the OpenStack environment. Access the D ynfl o w C o nso l e from any T asks page.
Report s
The R epo rts page displays a list of reports of Puppet runs executed on the hosts that the installer manages. You can access this page at any time from anywhere in the user interface by clicking Mo n it o r → Rep o rt s. You can also view all reports for a specific host by navigating to Ho st s → All Ho st s → [ Ho st n ame] → Rep o rt s.
Fig u re 5.12. T h e Rep o rt s p ag e
The reports table displays a list of the number of actions performed on individual hosts during a report interval. The time at which a report was collected is displayed in the Last repo rt column, and actions are divided into a number of categories as outlined below:
Appl i ed : The number of changes that were applied to resources on the host, such as files, directories, or user accounts.
R estarted : The number of resources, such as services, that were restarted.
Fai l ed : The number of actions that were executed but did not complete successfully.
R estart Fai l ures: The number of resources, such as services, that were scheduled to restart but did not restart successfully.
Ski pped : The number of actions that were scheduled, but were skipped due to a problem scheduling the Puppet run.
P end i ng : The number of actions that were scheduled to be applied, but had not yet been performed at the time the report was collected.
5.8. Complet ing Deployment for a Basic Environment
After you have provisioned your RHEL OpenStack Platform environment, the installer provides a list of details for that environment such as service passwords and the location of the Horizon
dashboard.
Pro ced u re 5.7. Ret rievin g Service Det ails
1. Click O p en St ack In st aller → Dep lo ymen t s.
2. Click the name of a deployment you have provisioned. 3. Review the details of the deployment.
Fig u re 5.13. T h e service d et ails p ag e
4. Optionally, click the Access al l d etai l s button to display the Al l d etai l s window, which displays a list of the passwords for all services in your environment.
Access the RHEL OpenStack Platform user interface with a web browser. Replace HOSTNAME with the host name or IP address of the server acting as the controller:
HTTPS
https://HOSTNAME/dashboard/ HTTP
http://HOSTNAME/dashboard/
When prompted, log in using the credentials of the ad mi n user. To begin using the OpenStack deployment, see the Administration User Guide and Cloud Administrator Guide.
Fig u re 5.14 . T h e Dash b o ard Lo g in Screen
This completes the creation of a basic Red Hat Enterprise Linux OpenStack Platform environment. Chapt er 5. Deployment Scenario 1 : Basic Environment
Chapter 6. Deployment Scenario 2: Advanced Environment with
NFS Storage
The object of this deployment scenario is to create an advanced Red Hat Enterprise Linux OpenStack Platform environment using the following specifications:
Six nodes:
Three Controller nodes with high-availability Three Compute nodes
Integration with an existing NFS storage server Neutron networking
Three networks:
A network for the installer's provisioning network (This example uses 10 . 1. 1. 0 /24 ) A network for OpenStack services (This example uses 10 . 1. 2. 0 /24 )
A network for external access (This example uses 19 2. 16 8. 1. 0 /24 ) NFS storage for Glance. This example uses an NFS share called g l ance. NFS storage for Cinder. This example uses an NFS share called ci nd er.
6.1. Discovering Host s for an Advanced Environment
The advanced environment scenario requires six hosts to provision as Red Hat Enterprise Linux OpenStack Platform nodes. The installer initially discovers these hosts through a PXE-based
discovery service. Users run a PXE boot on their bare metal hosts over the provisioning subnet (e.g. 10 . 1. 1. 0 /24 ). The installer automatically includes them in the list of available hosts for
provisioning.
Pro ced u re 6 .1. Ad d in g a Ho st via Disco very
1. Start the host and elect to start over the network from the boot options menu. This starts the host using the PXE service the installer provides.
2. Select Fo reman D i sco very from the P XE bo o t options menu. The host starts into the Fo reman D i sco very screen and is automatically registered in the installer.
