Red Hat Enterprise Linux OpenStack Platform 6 Deploying OpenStack: Enterprise Environments (Red Hat Enterprise Linux OpenStack Platform Installer)

Transcription

1 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 Documentation Team

2

3 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 rhos-docs@redhat.com

4 Legal Notice Copyright 2015 Red Hat, Inc. This do cument is licensed by Red Hat under the Creative Co mmo ns Attributio n- ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be remo ved. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other co untries. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Java is a registered trademark o f Oracle and/o r its affiliates. XFS is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/o r o ther co untries. MySQL is a registered trademark of MySQL AB in the United States, the European Union and o ther co untries. Node.js is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project. The OpenStack Wo rd Mark and OpenStack Lo go are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not 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 how to install Red Hat Enterprise Linux OpenStack Platform 6 on Red Hat Enterprise Linux in an enterprise enviro nment using the Red Hat Enterprise Linux OpenStack Platfo rm Installer.

5 T able of Cont ent s Table of Contents. Chapt..... er Int... roduct ion Chapt..... er Requirement s RHEL O p enstack Platfo rm Installer System Req uirements Client Bro wser Req uirements Ho st Req uirements 5. Chapt..... er Inst.... alling..... t. he.. RHEL O. penst ack... Plat... form..... Inst... aller Preco nfig uring the Netwo rk Sub scrib ing to the Req uired Channels Using Sub scrip tio n Manag er Running the Co nfig uratio n Scrip t Prep aring the Installatio n Med ium Co nfig uring a G ateway 18. Chapt..... er Planning your.... Environment Ho sts Netwo rking Sto rag e Dep lo yment Scenario s 26. Chapt..... er Deployment Scenario :. Basic..... Environment Disco vering Ho sts fo r a Basic Enviro nment Creating a Dep lo yment fo r a Basic Enviro nment Assig ning Ho sts to Dep lo yment Ro les Co nfig uring Ho st Netwo rking Co nfig uring External Brid g e Pro visio ning Red Hat Enterp rise Linux O p enstack Platfo rm Mo nito ring Pro g ress o f the Dep lo yment Co mp leting Dep lo yment fo r a Basic Enviro nment 39. Chapt..... er Deployment Scenario :. Advanced Environment wit.. h.. NFS.... St.. orage Disco vering Ho sts fo r an Ad vanced Enviro nment Creating a Dep lo yment fo r an Ad vanced Enviro nment Assig ning Ho sts to Dep lo yment Ro les Co nfig uring Ho st Netwo rking Co nfig uring External Brid g e Co nfig uring Fencing o n Hig h-availab ility No d es Pro visio ning Red Hat Enterp rise Linux O p enstack Platfo rm Mo nito ring Pro g ress o f the Dep lo yment Co mp leting Dep lo yment fo r an Ad vanced Enviro nment 56. Chapt..... er Deployment Scenario :.. Advanced Environment wit.. h.. Red.... Hat.... Ceph..... St.. orage Disco vering Ho sts fo r an Ad vanced Enviro nment Creating a Dep lo yment fo r an Ad vanced Enviro nment Assig ning Ho sts to Dep lo yment Ro les Co nfig uring Ho st Netwo rking Co nfig uring External Brid g e Mo d ifying Ad vanced Cep h Setting s Co nfig uring Fencing o n Hig h-availab ility No d es Pro visio ning Red Hat Enterp rise Linux O p enstack Platfo rm Mo nito ring Pro g ress o f the Dep lo yment Co mp leting Dep lo yment fo r an Ad vanced Enviro nment 75. Chapt..... er Scaling t. he... Environment

6 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller). Chapt..... er Scaling t. he... Environment Disco vering a New Ho st fo r Scaling Assig ning the Ho st to an Existing Dep lo yment Ro le Co nfig uring Ho st Netwo rking Dep lo ying New Ho sts fo r Red Hat Enterp rise Linux O p enstack Platfo rm 8 0. Chapt..... er T.. roubleshoot ing Defining the Pro visio ning Pro cess Tro ub lesho o ting Issues when Build ing Ho sts Tro ub lesho o ting Issues when Co nfig uring Ho sts 8 4. Chapt..... er Next..... St.. eps Appendix A... Firewall Rules Appendix B.... New.... Deployment Set... t. ings B.1. Netwo rk Co nfig uratio n Setting s 8 8 B.2. Services Co nfig uratio n Setting s 8 8. Appendix C... Configuring t he... RHEL..... O.. penst..... ack.... Plat... form..... Inst... aller C.1. Installatio n Med ia 9 2 C.2. O p erating Systems 9 4 C.3. Pro visio ning Temp lates 9 7 C.4. Partitio n Tab les 9 9 C.5. Sub nets 10 0 C.6. Users 10 1 C.7. User G ro up s 10 2 C.8. Ro les Appendix D.... Revision Hist.... ory

7 Chapt er 1. Int roduct ion 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 D eploying Basic OpenStack environments using Nova networking and local storage D eploying 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"( US/Red_Hat_Enterprise_Linux_OpenStack_Platform/). 3

8 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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 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 D NS 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. D isable 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. 4

9 Chapt er 2. Requirement s 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 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: D esign elements may not align correctly. Level 4: Unsupported. The following table outlines the supported browsers and their level of support: Table 2.1. Supported Browsers Browser Version Support 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 L 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 Cont roller Node Requirement s 5

10 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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. Processor 64-bit x86 processor with support for the Intel 64 or AMD64 CPU extensions. Memo ry A minimum of 4 GB of RAM. Disk Space 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. Network Interface Cards A minimum of 3 x 1 Gbps Network Interfaces 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. Processor 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 Space 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. Network Interface Cards 6

11 Chapt er 2. Requirement s A minimum of 3 x 1 Gbps Network Interfaces Ceph St orage Node Requirement s Ceph storage nodes are responsible for providing object storage in a RHEL OpenStack Platform environment. Processor 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 Space Storage requirements depends on the amount of memory. Ideally, use at minimum 1 GB of memory per 1 TB of hard disk space. Network Interface Cards 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. 7

12 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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 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. D isable 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 rk-scri 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 8

13 Chapt er 3. Inst alling t he RHEL O penst ack Plat form Inst aller 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 D NS 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 D NS information set. For example, if your provisioning provisioning network interface is eth0, edit the /etc/sysco nfi g /netwo rkscri 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 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. Procedure 3.1. Subscribing to the Required Channels Using Subscription Manager 1. Register your system with the Content D elivery 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 Linux OpenStack Platform Installer. 9

14 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux 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 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. Procedure 3.2. Installing and running the Red Hat Enterprise Linux O penstack Platform installer configuration script 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? 10

15 Chapt er 3. Inst alling t he RHEL O penst ack Plat form Inst aller Once you have chosen a network interface, the configuration script displays some network options to configure. Procedure 3.3. Configuring Network O ptions 1. Enter the number for the configuration option to change, and press Enter. Table 3.1. Networking Setup O ptions O ption Netwo rk i nterface IP Ad d ress Netwo rk mask Netwo rk ad d ress Ho st g ateway D HC P rang e start D HC P rang e end D HC P G ateway D NS fo rward er D o mai n Fo reman UR L NT P sync ho st Description 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. The IP address of the machine hosting the installer. 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. 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, /24. The address of a machine that acts as a gateway for the machine hosting the installer. 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. 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. 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. 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. 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. 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. The address of an NTP server that the installer can use to synchronize the time on machines that it provisions. 11

16 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) O ption T i mezo ne Description 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. 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. Example 3.1. Sample Network Configuration 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: ' 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 12

17 Chapt er 3. Inst alling t he RHEL O penst ack Plat form Inst aller 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. Procedure 3.4. Configuring Client Authentication 1. Enter the number for the configuration option to change, and press Enter. Table 3.2. Client Authentication O ptions O ption SSH publ i c key R o o t passwo rd Description 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. 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. Example 3.2. Sample Client Authentication Configuration 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?: 13

18 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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. Procedure 3.5. Configuring Installation Medium Details 1. Enter 1, and press Enter. Table 3.3. Installation Media O ptions O ption Set R HEL repo path (http o r https UR L) Description 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 completes. For the moment, enter the following as the RHEL repo 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. Example 3.3. Sample Installation Medium Configuration 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. Enter RHEL repo path: 14

19 Chapt er 3. Inst alling t he RHEL O penst ack Plat form Inst aller 1. Set RHEL repo path (http or https URL): 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. Procedure 3.6. Configuring Subscription Management Details 1. Enter the number for the configuration option to change, and press Enter. Table 3.4. Subscription Manager O ptions O ption Subscri pti o n manag er username Subscri pti o n manag er passwo rd C o mma o r space separated repo si to ri es Subscri pti o n manag er po o l (reco mmend ed ) Subscri pti o n manag er pro xy ho stname Subscri pti o n manag er pro xy po rt Subscri pti o n manag er pro xy username Subscri pti o n manag er pro xy passwo rd Description The username of a Customer Portal account that can be used to register machines that the installer provisions with the Content D elivery Network. A password that can be used to authenticate the above account. 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. 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. The host name of a machine that can be used as a Subscription Manager proxy. The port by which to connect with the Subscription Manager proxy. A username by which to connect with the Subscription Manager proxy. 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. Example 3.4. Sample Subscription Management Configuration Screen Enter your subscription manager credentials: 1. Subscription manager username: 2. Subscription manager password: 3. Comma separated repositories: rhel-7-server-openstack-6.0- rpms rhel-7-server-openstack-6.0-installer-rpms rhel-7-server-rh- 15

20 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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. Example 3.5. Sample Completion Screen Success! * Foreman is running at Initial credentials are admin / nziesrtcunvfg79z * Foreman Proxy is running at * 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 Admin User My account. Change the P asswo rd, Veri fy it, and click Submi t. 16

21 Chapt er 3. Inst alling t he RHEL O penst ack Plat form Inst aller 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 spi nstal l er configuration script. This is because the rhel -o sp-i nstal l er script writes 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. Procedure 3.7. Preparing an Installation Medium 1. Go to and log in to the Red Hat Customer Portal using your customer account details. 2. Click Downloads 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: # chmod -R 755 /var/www/html/rhel7/ 17

22 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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 <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 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 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 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. Procedure 3.8. Configuring a G ateway 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 3. Load the new value: 18

23 Chapt er 3. Inst alling t he RHEL O penst ack Plat form Inst aller # 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 /8, XX. XX /16, or XX. XX. XX. 0 0 / 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. 19

24 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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: 20

25 Chapt er 4. Planning your Environment Figure 4.1. Sample Deployment Topology 4.1. Host s 21

26 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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: Controller Provides key services such as the MySQL database for storing data about your environment, Horizon, Keystone, and Glance. Compute A host that acts as a hypervisor, providing the processing capabilities required for running virtual machines in the environment. You can add more Compute nodes to your environment at any time by assigning additional hosts to this deployment role and repeating the provisioning process; the installer ignores all hosts that have already been provisioned and provisions only the new host. Ceph Storage Node (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 eneric 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 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: Nova This is the legacy networking type where the Compute nodes manage IP forwarding, bridges, and VLANs. Neutron This is the newer networking service that operates autonomously and manages softwarebased networks, static and floating IP addresses, and D HCP. The installer maps and deploys this service onto each Controller node in a RHEL OpenStack Plaform environment. 22

27 Chapt er 4. Planning your Environment The installer also provides functions to map different services to different subnets. For example, the hosts in Figure 4.1, Sample D eployment 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 D elivery 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 ( /24 ). Thie following procedures show how to map networks for an External subnet ( /24 ) and OpenStack services ( /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 Creat ing an Ext ernal Subnet The following procedure maps the external network ( /24 ) for provisioned hosts to use. Procedure 4.1. Creating an External Subnet 1. From the title bar in the main screen of the user interface, click Infrastructure Subnets. 23

28 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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 ) in the Netwo rk ad d ress field. c. Enter the network mask for the subnet (e.g ) in the Netwo rk mask field. d. Enter the address of a gateway (e.g ) 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' D HCP 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 Infrastructure Domains. 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 Creat ing an OpenSt ack Services Subnet The following procedure maps the OpenStack services network ( /24 ) for provisioned hosts to use. Procedure 4.2. Creating an O penstack Services Subnet 24

29 Chapt er 4. Planning your Environment 1. From the title bar in the main screen of the user interface, click Infrastructure Subnets. 2. Click New Subnet. 3. Configure general subnet details: 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 ) in the Netwo rk ad d ress field. c. Enter the network mask for the subnet (e.g ) in the Netwo rk mask field. d. Enter the address of a gateway (e.g ) 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 D atabase 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 Infrastructure Domains. 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 St orage The installer provides several options for image (Glance) and block (Cinder) storage services: 25

30 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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 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 Environment - See Chapter 5, Deployment Scenario 1: Basic Environment Advanced Environment with NFS Storage - See Chapter 6, Deployment Scenario 2: Advanced Environment with NFS Storage Advanced Environment with Ceph Storage - See Chapter 7, Deployment Scenario 3: Advanced Environment with Red Hat Ceph Storage The following table highlights the key differences in these scenarios: Basic Environment Scen ario Advanced Environment Scenario with NFS Storage Total Hosts Host Roles 1 Controller 3 Controller Advanced Environment Scenario with Red Hat Ceph Storage 3 Controller 2 Compute 3 Compute 3 Compute 3 Ceph Networking Type Nova Neutron Neutron Total Subnets Image Storage (Glance) Local NFS Ceph Block Storage (Cinder) Local (LVM) NFS Ceph 26

31 Chapt er 5. Deployment Scenario 1 : Basic Environment 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 /24 ) A network for OpenStack services (This example uses /24 ) A network for external access (This example uses /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 /24 ). The installer automatically includes them in the list of available hosts for provisioning. Procedure 5.1. Adding a Host via Discovery 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. 27

32 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) Figure 5.1. The Foreman Discovery Screen 3. Log in to the user interface and confirm that the host has been registered: a. Click Hosts Discovered hosts. b. Click the name of the newly registered host to open the details page for the host, and review the details. 28

33 Chapt er 5. Deployment Scenario 1 : Basic Environment Figure 5.2. The Discovered Host Details Page 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 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 penstack Installer New deployment. The D epl o yment Setti ng s page requires some initial settings for your basic environment. Procedure 5.2. Configuring Deployment Settings 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. 4. Select R abbi tmq as the message broker in the Messag i ng P ro vi d er section. 29

34 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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. Figure 5.3. The Deployment Settings step The Netwo rk C o nfi g urati o n page maps OpenStack's network traffic types to the subnets in your environments. Procedure 5.3. Configuring Network Traffic 1. Drag the External network traffic type onto the External subnet (e.g /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 /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 /24 ). 30

35 Chapt er 5. Deployment Scenario 1 : Basic Environment 4. Click Next. Figure 5.4. The Network Configuration step 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. D rag 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. 31

36 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) Figure 5.5. The Services O verview step The Servi ces C o nfi g urati o n page provides options to configure OpenStack's Nova, Glance, and Cinder services. Procedure 5.4. Configuring Service O ptions 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 /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 /24 ). 32

37 Chapt er 5. Deployment Scenario 1 : Basic Environment Figure 5.6. Nova configuration options 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. Figure 5.7. G lance configuration options 3. Select the following options for C i nd er: 33

38 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) a. Check LVM in the C ho o se D ri ver Backend section. This enables local storage for the Cinder service. Figure 5.8. Cinder configuration options 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 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. Procedure 5.5. Assigning Hosts to Deployment Roles 1. Click O penstack Installer Deployments. 2. Click the name of the deployment to which to assign hosts to open the details page for that deployment. 34

39 Chapt er 5. Deployment Scenario 1 : Basic Environment Figure 5.9. The deployment details page 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: Controller 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. Compute A host that acts as a hypervisor, providing the processing capabilities required for running virtual machines in the environment. You can add more Compute nodes to your environment at any time by assigning additional hosts to this deployment role and repeating the provisioning process; the installer ignores all hosts that have already been provisioned and provisions only the new host. Assign two hosts to this role for the basic deployment scenario. Ceph Storage Node (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 eneric 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. Click Assi g n Ho sts to assign the host to the selected deployment role. 35

40 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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. Procedure 5.6. Configuring Networking on a Host 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. D rag and drop subnets between the sections for network interfaces to change the network traffic carried by those interfaces. Figure The Configure Networks 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. b. Select the bonding mode from the Bo nd i ng Mo d e list. 36

41 Chapt er 5. Deployment Scenario 1 : Basic Environment 6. Click D o ne 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 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. Figure The deployment confirmation screen 37

42 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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 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 Monitor Tasks. 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 Monitor Reports. You can also view all reports for a specific host by navigating to Hosts All Hosts [Hostname] Reports. 38

43 Chapt er 5. Deployment Scenario 1 : Basic Environment Figure The Reports page 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 Complet ing Deployment for a Basic Environment 39

44 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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. Procedure 5.7. Retrieving Service Details 1. Click O penstack Installer Deployments. 2. Click the name of a deployment you have provisioned. 3. Review the details of the deployment. Figure The service details page 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 HTTP 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. 4 0

45 Chapt er 5. Deployment Scenario 1 : Basic Environment Figure The Dashboard Login Screen This completes the creation of a basic Red Hat Enterprise Linux OpenStack Platform environment. 4 1

46 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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 /24 ) A network for OpenStack services (This example uses /24 ) A network for external access (This example uses /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 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 /24 ). The installer automatically includes them in the list of available hosts for provisioning. Procedure 6.1. Adding a Host via Discovery 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. 4 2

47 Chapt er 6. Deployment Scenario 2 : Advanced Environment wit h NFS St orage Figure 6.1. The Foreman Discovery Screen 3. Log in to the user interface and confirm that the host has been registered: a. Click Hosts Discovered hosts. b. Click the name of the newly registered host to open the details page for the host, and review the details. 4 3

48 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) Figure 6.2. The Discovered Host Details Page 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 Creat ing a Deployment for an Advanced Environment This process creates a deployment for provisioning an advanced 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 penstack Installer New deployment. The D epl o yment Setti ng s page requires some initial settings for your advanced environment. 1. Enter a name for the deployment in the Name field. For example, Ad vanced D epl o yment. 2. Enter a description in the D escri pti o n field. 3. Select Neutro n Netwo rki ng in the Netwo rki ng section. 4. Select R abbi tmq as the message broker in the Messag i ng P ro vi d er section. 4 4

49 Chapt er 6. Deployment Scenario 2 : Advanced Environment wit h NFS St orage 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. Figure 6.3. The Deployment Settings step The Netwo rk C o nfi g urati o n page maps OpenStack's network traffic types to the subnets in your environments. Procedure 6.2. Configuring Network Traffic 1. Drag the External network traffic type onto the External subnet (e.g /24 ) created in Section 4.2.1, Creating an External Subnet. 4 5

50 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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 /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 /24 ). 4. Click Next. Figure 6.4. The Network Configuration step 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. D rag 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. 4 6

51 Chapt er 6. Deployment Scenario 2 : Advanced Environment wit h NFS St orage Figure 6.5. The Services O verview step The Servi ces C o nfi g urati o n page provides options to configure OpenStack's Neutron, Glance, and Cinder services. 1. Accept the default options for Neutro n configuration. Figure 6.6. Neutron Configuration O ptions 4 7

52 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) Note By default, the L2 po pul ati o n option in the Neutro n tab is not selected. Due to an incompatibility in L3 high availability and L2 population, you must ensure this option remains deselected in environments with more than one controller such as this scenario. However, in environments with one controller node where OpenStack networking is used, you must manually select this option. 2. Select the following options for G l ance: a. Select NFS from the C ho o se D ri ver Backend section. This displays a field for the NFS UR I. Enter this URI in the following form: [server]: [l o cal path] For example: nfs. exampl e. co m: /g l ance Figure 6.7. G lance configuration options 3. Select the following options for C i nd er a. Check NFS in the C ho o se D ri ver Backend section. This displays a field for the NFS UR I. Enter this URI in the following form: [server]: [l o cal path] For example: nfs. exampl e. co m: /ci nd er 4 8

53 Chapt er 6. Deployment Scenario 2 : Advanced Environment wit h NFS St orage Figure 6.8. Cinder configuration options 4. Click Submi t. This completes the deployment creation process. The next step in the creation of the advanced environment involves assigning the discovered hosts to specific deployment roles 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. An advanced environment requires hosts assigned to the following roles: Three Controller nodes Three Compute nodes Assign hosts you added to the installer to one of the roles in a deployment. Procedure 6.3. Assigning Hosts to Deployment Roles 1. Click O penstack Installer Deployments. 2. Click the name of the deployment to which to assign hosts to open the details page for that deployment. 4 9

54 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) Figure 6.9. The deployment details page 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: Controller Provides key services such as the MySQL database for storing data about your environment, Horizon, Keystone, and Glance. Assign two hosts to this role for the advanced deployment scenario. Compute A host that acts as a hypervisor, providing the processing capabilities required for running virtual machines in the environment. You can add more Compute nodes to your environment at any time by assigning additional hosts to this deployment role and repeating the provisioning process; the installer ignores all hosts that have already been provisioned and provisions only the new host. Assign three hosts to this role for the advanced deployment scenario. Ceph Storage Node (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 eneric 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. 50

55 Chapt er 6. Deployment Scenario 2 : Advanced Environment wit h NFS St orage 5. Click Assi g n Ho sts to assign the host to the selected deployment role 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. Procedure 6.4. Configuring Networking on a Host 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. D rag and drop subnets between the sections for network interfaces to change the network traffic carried by those interfaces. Figure The Configure Networks 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. 51

56 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) b. Select the bonding mode from the Bo nd i ng Mo d e list. 6. Click D o ne 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 Configuring Fencing on High-Availabilit y Nodes Configure fencing on hosts that have been assigned to the controller deployment role in deployments where you selected Hi g h Avai l abi l i ty C o ntro l l ers / C o mpute in the D epl o yment Setti ng s step when creating that deployment. Procedure 6.5. Configuring Fencing on High-Availability Nodes 1. From the title bar in the main screen of the user interface, click Hosts All hosts. 2. Click the name of the host to configure. 3. Click Ed i t. 4. Click the Fenci ng tab. 52

57 Chapt er 6. Deployment Scenario 2 : Advanced Environment wit h NFS St orage Figure The Fencing tab 5. If the message Fenci ng i s d i sabl ed. T o enabl e, fi rst yo u need to ad d a BMC i nterface to the Ho st is displayed, you must manually configure the details of a baseboard management controller network interface attached to the host: a. Click the Netwo rk tab. b. Click Ad d Interface. c. Select BMC from the T ype list. d. Enter the MAC address for the network interface controller in the MAC ad d ress field. e. Click the Fenci ng tab. 6. Select Enabl e Fenci ng. 7. Select IP MI from the T ype list. 8. Enter the IP address of the fencing device in the IP Ad d ress field. 9. Enter the name of the IPMI user on the fencing device in the Username field. 10. Enter the password by which to authenticate the above user in the P asswo rd field. 11. Select Expo se Lanpl us to use the l anpl us interface. 53

58 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 12. If you selected the Expo se Lanpl us check box, enter any options in the Lanpl us O pti o ns field. 13. Click Submi t. You have configured fencing for the host, and the settings you specified are applied to the host when you provision RHEL OpenStack Platform 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. Figure The deployment confirmation 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 Monit oring Progress of t he Deployment 54

59 Chapt er 6. Deployment Scenario 2 : Advanced Environment wit h NFS St orage 6.8. 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 Monitor Tasks. 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 Monitor Reports. You can also view all reports for a specific host by navigating to Hosts All Hosts [Hostname] Reports. 55

60 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) Figure The Reports page 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 Complet ing Deployment for an Advanced Environment 56

61 Chapt er 6. Deployment Scenario 2 : Advanced Environment wit h NFS St orage 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. Procedure 6.6. Retrieving Service Details 1. Click O penstack Installer Deployments. 2. Click the name of a deployment you have provisioned. 3. Review the details of the deployment. Figure The service details page 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 HTTP 57

62 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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. Figure The Dashboard Login Screen This completes the creation of an advanced Red Hat Enterprise Linux OpenStack Platform environment. 58

63 Chapt er 7. Deployment Scenario 3: Advanced Environment wit h Red Hat Ceph St orage Chapter 7. Deployment Scenario 3: Advanced Environment with Red Hat Ceph Storage The object of this deployment scenario is to create an advanced Red Hat Enterprise Linux OpenStack Platform environment using the following specifications: Between six and nine nodes: Three Controller nodes with high-availability Three Compute nodes Three node for Red Hat Ceph Storage cluster. However, if you have an existing cluster, these nodes are not required. Integration with an Red Hat Ceph Storage cluster. This scenario provides options to configure for an existing cluster or creating a new cluster. Neutron networking Three networks: A network for the installer's provisioning network (This example uses /24 ) A network for OpenStack services (This example uses /24 ) A network for external access (This example uses /24 ) Ceph storage for Glance Ceph storage for Cinder 7.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 /24 ). The installer automatically includes them in the list of available hosts for provisioning. Procedure 7.1. Adding a Host via Discovery 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. 59

64 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) Figure 7.1. The Foreman Discovery Screen 3. Log in to the user interface and confirm that the host has been registered: a. Click Hosts Discovered hosts. b. Click the name of the newly registered host to open the details page for the host, and review the details. 60

65 Chapt er 7. Deployment Scenario 3: Advanced Environment wit h Red Hat Ceph St orage Figure 7.2. The Discovered Host Details Page 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 Creat ing a Deployment for an Advanced Environment This process creates a deployment for provisioning an advanced 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 penstack Installer New deployment. The D epl o yment Setti ng s page requires some initial settings for your advanced environment. 1. Enter a name for the deployment in the Name field. For example, Ad vanced D epl o yment. 2. Enter a description in the D escri pti o n field. 3. Select Neutro n Netwo rki ng in the Netwo rki ng section. 4. Select R abbi tmq as the message broker in the Messag i ng P ro vi d er section. 61

66 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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. Figure 7.3. The Deployment Settings step The Netwo rk C o nfi g urati o n page maps OpenStack's network traffic types to the subnets in your environments. Procedure 7.2. Configuring Network Traffic 1. Drag the External network traffic type onto the External subnet (e.g /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 /24 ) created in Section 4.2.2, Creating an OpenStack Services Subnet. 62

67 Chapt er 7. Deployment Scenario 3: Advanced Environment wit h Red Hat Ceph St orage 3. Leave the P ro vi si o ni ng /P XE network traffic type in the d efaul t subnet (e.g /24 ). 4. Click Next. Figure 7.4. The Network Configuration step 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. D rag 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. 63

68 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) Figure 7.5. The Services O verview step The Servi ces C o nfi g urati o n page provides options to configure OpenStack's Neutron, Glance, and Cinder services. 1. Accept the default options for Neutro n configuration. Figure 7.6. Neutron Configuration O ptions 64

69 Chapt er 7. Deployment Scenario 3: Advanced Environment wit h Red Hat Ceph St orage Note By default, the L2 po pul ati o n option in the Neutro n tab is not selected. Due to an incompatibility in L3 high availability and L2 population, you must ensure this option remains deselected in environments with more than one controller such as this scenario. However, in environments with one controller node where OpenStack networking is used, you must manually select this option. 2. Select the following options for G l ance: a. Select C eph from the C ho o se D ri ver Backend section. Figure 7.7. G lance configuration options 3. Select the following options for C i nd er a. Check C eph in the C ho o se D ri ver Backend section. 65

70 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) Figure 7.8. Cinder configuration options 4. Click Submi t. This completes the deployment creation process. The next step in the creation of the advanced environment involves assigning the discovered hosts to specific deployment roles 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. An advanced environment requires hosts assigned to the following roles: Three Controller nodes Three Compute nodes Three Ceph node if creating a new cluster Assign hosts you added to the installer to one of the roles in a deployment. Procedure 7.3. Assigning Hosts to Deployment Roles 1. Click O penstack Installer Deployments. 2. Click the name of the deployment to which to assign hosts to open the details page for that deployment. 66

71 Chapt er 7. Deployment Scenario 3: Advanced Environment wit h Red Hat Ceph St orage Figure 7.9. The deployment details page 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: Controller Provides key services such as the MySQL database for storing data about your environment, Horizon, Keystone, and Glance. Assign three hosts to this role for the advanced deployment scenario. Compute A host that acts as a hypervisor, providing the processing capabilities required for running virtual machines in the environment. You can add more Compute nodes to your environment at any time by assigning additional hosts to this deployment role and repeating the provisioning process; the installer ignores all hosts that have already been provisioned and provisions only the new host. Assign three hosts to this role for the advanced deployment scenario. Ceph Storage Node (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. If creating a new Ceph cluster with the installer, assign three hosts to this role. If integrating with an existing Ceph cluster, assign no hosts to this role. G eneric 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. 67

72 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) deployment scenario. 4. Select the check box for hosts in the Unassi g ned Ho sts section. 5. Click Assi g n Ho sts to assign the host to the selected deployment role 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. Procedure 7.4. Configuring Networking on a Host 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. D rag and drop subnets between the sections for network interfaces to change the network traffic carried by those interfaces. Figure The Configure Networks Screen Optionally, configure a bond between two network interfaces:

73 Chapt er 7. Deployment Scenario 3: Advanced Environment wit h Red Hat Ceph St orage 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. b. Select the bonding mode from the Bo nd i ng Mo d e list 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 Modifying Advanced Ceph Set t ings The installer provides you with a set of advanced configuration options to manually define aspects of your OpenStack Platform environment. This includes settings for Red Hat Ceph Storage. These advanced settings allow you to integrate your new OpenStack Platform environment with an existing Ceph Storage cluster. Note Refer to the /etc/ceph/ceph. co nf file from your existing Ceph cluster for settings to use in the Advanced Configuration section. Important It is recommended to leave these settings as defaults when creating a new Ceph cluster configuration through the installer. Use the following procedure to modify your Ceph settings. Procedure 7.5. Modifying Advanced Ceph Settings 1. Click the Ad vanced C o nfi g urati o n tab. 2. Click the Ed i t button. 3. Choose the C o ntro l l er service. Scroll to the following settings and edit them as required: 69

74 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) C eph cl uster netwo rk - The network that contains the existing Ceph cluster. C eph fsi d - The Ceph filesystem ID to use. C eph i mag es key - The key to use for image authentication. C eph mo n ho st - An array of monitor hosts. For example: ["ceph1.example.com","ceph2.example.com","ceph3.example.com"] C eph mo n i ni ti al members - An array of initial monitor hosts to establish a quorum. For example: ["ceph1.example.com","ceph2.example.com"] C eph vo l umes key - The key to use for volume authentication. 4. Choose the Neutro n-co mpute service. Scroll to the following settings and edit them as required: C eph cl uster netwo rk - The network that contains the existing Ceph cluster. C eph fsi d - The Ceph filesystem ID to use. C eph i mag es key - The key to use for image authentication. C eph mo n ho st - An array of monitor hosts. For example: ["ceph1.example.com","ceph2.example.com","ceph3.example.com"] C eph mo n i ni ti al members - An array of initial monitor hosts to establish a quorum. For example: ["ceph1.example.com","ceph2.example.com"] C eph vo l umes key - The key to use for volume authentication. Li bvi rt i mag es type - The image type for l i bvi rt to use for Ceph. Set this to d efaul t. 5. Click the Appl y button. 70

75 Chapt er 7. Deployment Scenario 3: Advanced Environment wit h Red Hat Ceph St orage Figure Scroll to the Ceph options The installer now uses the settings from your existing Ceph Storage cluster in your new Red hat Enterprise Linux OpenStack Platform environment Configuring Fencing on High-Availabilit y Nodes Configure fencing on hosts that have been assigned to the controller deployment role in deployments where you selected Hi g h Avai l abi l i ty C o ntro l l ers / C o mpute in the D epl o yment Setti ng s step when creating that deployment. Procedure 7.6. Configuring Fencing on High-Availability Nodes 1. From the title bar in the main screen of the user interface, click Hosts All hosts. 2. Click the name of the host to configure. 3. Click Ed i t. 4. Click the Fenci ng tab. 71

76 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) Figure The Fencing tab 5. If the message Fenci ng i s d i sabl ed. T o enabl e, fi rst yo u need to ad d a BMC i nterface to the Ho st is displayed, you must manually configure the details of a baseboard management controller network interface attached to the host: a. Click the Netwo rk tab. b. Click Ad d Interface. c. Select BMC from the T ype list. d. Enter the MAC address for the network interface controller in the MAC ad d ress field. e. Click the Fenci ng tab. 6. Select Enabl e Fenci ng. 7. Select IP MI from the T ype list. 8. Enter the IP address of the fencing device in the IP Ad d ress field. 9. Enter the name of the IPMI user on the fencing device in the Username field. 10. Enter the password by which to authenticate the above user in the P asswo rd field. 11. Select Expo se Lanpl us to use the l anpl us interface. 72

77 Chapt er 7. Deployment Scenario 3: Advanced Environment wit h Red Hat Ceph St orage 12. If you selected the Expo se Lanpl us check box, enter any options in the Lanpl us O pti o ns field. 13. Click Submi t. You have configured fencing for the host, and the settings you specified are applied to the host when you provision RHEL OpenStack Platform 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. Figure The deployment confirmation 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 Monit oring Progress of t he Deployment 73

78 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 7.9. 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 Monitor Tasks. 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 Monitor Reports. You can also view all reports for a specific host by navigating to Hosts All Hosts [Hostname] Reports. 74

79 Chapt er 7. Deployment Scenario 3: Advanced Environment wit h Red Hat Ceph St orage Figure The Reports page 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 Complet ing Deployment for an Advanced Environment 75

80 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 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. Procedure 7.7. Retrieving Service Details 1. Click O penstack Installer Deployments. 2. Click the name of a deployment you have provisioned. 3. Review the details of the deployment. Figure The service details page 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. A final step in the configuration of your advanced environment requires you to create your Ceph Storage Cluster. The deployed Ceph Storage Nodes (OSD) already have configuration files stored in /etc/ceph that help connect to your RHEL OpenStack Platform environment. Use these nodes to create your Ceph Storage Cluster. Consult your Ceph Storage Cluster documentation for details on how to install packages and finalize the configuration of the cluster. 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 76

81 Chapt er 7. Deployment Scenario 3: Advanced Environment wit h Red Hat Ceph St orage HTTP 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. Figure The Dashboard Login Screen This completes the creation of an advanced Red Hat Enterprise Linux OpenStack Platform environment with Red Hat Ceph Storage integration. 77

82 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) Chapter 8. Scaling the Environment The Red Hat Enterprise Linux OpenStack Platform installer not only deploys multi-node OpenStack environments but also provides a means to scale such environments. Scaling an environment is a simple process that only requires adding more hosts to deployment roles. This chapter steps through the process of adding a Compute node to an existing environment Discovering a New Host for Scaling Scaling your environment also uses the PXE-based discovery service to add new hosts. Users run a PXE boot on their bare metal hosts over the provisioning subnet (e.g /24 ) and the installer automatically includes them in the list of available hosts. Procedure 8.1. Adding a Host via Discovery 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. Figure 8.1. The Foreman Discovery Screen 78

83 Chapt er 8. Scaling t he Environment 3. Log in to the user interface and confirm that the host has been registered: a. Click Hosts Discovered hosts. b. Click the name of the newly registered host to open the details page for the host, and review the details. Figure 8.2. The Discovered Host Details Page 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 Assigning t he Host t o an Exist ing Deployment Role Adding a new host to your Red Hat Enterprise Linux OpenStack Platform environment requires assigning it to an existing deployment role. The installer builds the new host and then configures it to work within your environment. This scenario demonstrates adding a new host to the Compute deployment role. Procedure 8.2. Assigning Host to Compute Deployment Roles 1. Click O penstack Installer Deployments. 2. Click the name of the deployment to which to assign hosts to open the details page for that deployment. 3. In the D epl o yment R o l es section, click + for the C o mpute deployment role to display the Unassi g ned Ho sts for use in that deployment role. 4. Select the check box for the host in the Free Ho sts section. 5. Click Assi g n Ho sts to assign the new host to the selected deployment role. 79

84 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) 8.3. 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. Procedure 8.3. Configuring Networking on a Host 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. D rag and drop subnets between the sections for network interfaces to change the network traffic carried by those interfaces. Figure 8.3. The Configure Networks Screen 5. Optionally, configure a bond between two network interfaces: 6. Click D o ne. a. Click the bonding button for a network interface and click the name of a network interface to bond the two network interfaces. b. Select the bonding mode from the Bo nd i ng Mo d e list Deploying New Host s for Red Hat Ent erprise Linux OpenSt ack Plat form 80

85 Plat form Chapt er 8. Scaling t he Environment The new host is now assigned to the Compute deployment role and its networking is configured. The final step is to deploy the new host. Procedure 8.4. Deploying New Hosts for Red Hat Enterprise Linux O penstack Platform 1. Click D epl o y to open the deployment confirmation screen. Figure 8.4. The deployment confirmation 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. 2. Click D epl o y. The new host moves to the pro d ucti o n environment, which contains the Puppet classes required to provision RHEL OpenStack Platform. Only the new host is provisioned in accordance with its assigned Compute role. The existing hosts are not reprovisioned. 81

86 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) Chapter 9. Troubleshooting This chapter contains some advice to help analyze and resolve problems that might occur during the deployment of your Red Hat Enterprise Linux OpenStack Platform environment Defining t he Provisioning Process The Red Hat Enterprise Linux OpenStack Platform installer has two main steps when provisioning each host: Building - The building process occurs through PXE network boot. The installer applies a kickstart configuration to build the initial host operating system. This process involves: Installing the operating system, which you defined during the rhel -o sp-i nstal l er stage. Configuring network interfaces. Registering the system and attaching Red Hat product subscriptions. Installing Puppet for the configuration process. Configuration - The configuration process occurs when the host's building process successfully completes. This configuration process uses a set of Puppet modules to install and configure the required OpenStack services for your environment. The installer communicates with a Puppet Agent installed on each host to apply the configuration from each module. The provisioning and configuration process further breaks into specific tasks that the installer completes. You can view these tasks in the Dynflow console for the deployment task. To access the T ask page for your deployment, click Sho w mo re d etai l s under the progress bar on the Deployment page. From there, click the D ynfl o w C o nso l e. These D ynfl o w C o nso l e displays a combination of subtasks associated with your deployment. Knowing the functions of each subtask helps with determining the deployment stage. These subtasks are: Actions::Staypuft::Host::Update Updates a host' s attributes. Actions::Staypuft::Host::TriggerProvisioning Starts the provisioning process for a new host. This includes resetting the host and PXE booting to the provisioning templates assigned to the host. Actions::Staypuft::Host::WaitUntilProvisioned Waits until the host provisioning process completes. This item completes when the host finishes running through the kickstart provisioning template. Actions::Staypuft::Host::WaitUntilReady Checks if a particular host is ready to accept SSH connections. This is so the installer can start the Puppet Agent on the host. Actions::Staypuft::Host::PuppetRun Starts configuration on the host using Puppet Agent. Actions::Staypuft::Host::ReportWait 82

87 Chapt er 9. T roubleshoot ing Waits until the Puppet Agent on the host completes configuration and sends a report. Actions::Staypuft::Host::AssertReportSuccess Checks if the host has any outstanding errors from the last Puppet Agent report T roubleshoot ing Issues when Building Host s Reviewing Anaconda Logs Host provisioning in a Red Hat Enterprise Linux OpenStack Platform environment uses Kickstart and anaco nd a to build the base operating system. This means the logs for the initial build are stored in /var/l o g /anaco nd a/ of each host. The log files in this directory show the host's entire build process and provide messages for any point of error. If a host fails to build, consult these log files to determine the causes of the failed build Checking Subscript ion Det ails and Inst alled Packages Check if the host has successfully registered to the Red Hat Customer Portal and has the correct subscriptions attached: # subscription-manager status # subscription-manager list --consumed # subscription-manager repos grep "Enabled:.*1" -B3 Also check if the following packages were installed during the initial build process: # yum list sos sos-plugins-openstack rhos-log-collector puppet rhel-ospinstaller-client If the hosts lacks the required subscription details or necessary packages after the build process completes, it means an error occurred when attempting to register your host and attach the relevant subscription pools. Check the build logs (see Section 9.1, D efining the Provisioning Process ) or restart the build process for the host (see Section 9.2.4, Rebuilding Hosts ) to see where the subscription management issues occur Edit ing Kickst art T emplat es The Red Hat Enterprise Linux OpenStack Platform installer uses a set of Kickstart templates and snippets. These templates are located in Hosts Provisioning Templates. The default template used for provisioning hosts is the Ki ckstart R HEL d efaul t template. The template follows standard Kickstart syntax. However, the template also allows certain variables including: Host Parameters - These are custom values defined for each host and are inserted into the template using the following syntax: host.params['time-zone'] %> A full list of parameters is available on each host's P arameters tab. 83

88 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) Template Snippets - Snippets are template segments used in multiple templates. Using snippets reduces the amount of replication across multiple provisioning templates. Insert snippets into a template using the following syntax: <%= snippet 'kickstart_networking_setup' %> Editing the default kickstart template provides a means of customizing the build process to workaround any issues that appear in the anaco nd a logs of a faulty build. Warning The default Kickstart template and associated snippets are designed and tested to provide a working Red Hat Enterprise Linux OpenStack Platform environment. Only edit the default Kickstart template if your encounter an error in the build process and you feel comfortable with resolving the error yourself. Perform such edits with caution as faults in the Kickstart template can cause the provisioning process to stop functioning. Contact your Red Hat Technical Support representative if you require help with diagnosing and resolving build errors in the provisioning process Rebuilding Host s In the event of a host fault, make any necessary adjustments to the Kickstart template and trigger a host rebuild. Procedure 9.1. Triggering a Host Rebuild 1. Navigate to Hosts All hosts. 2. Click on the Name of the host to rebuild. 3. Click the Bui l d button. A message appears stating that the host will rebuild the next time it boots. 4. Manually reboot your host and boot it through PXE. The host runs through the build process again when it boots through PXE T roubleshoot ing Issues when Configuring Host s Diagnosing Communicat ion Issues wit h Host s Each time the installer runs a Acti o ns: : Staypuft: : Ho st: : P uppetr un subtask on a host, the installer starts the Puppet Agent on the host through SSH. Ensure the installer resolves the host' s domain name: [root@ installer ~]# ping macd050992f6aa3.example.com If the Acti o ns: : Staypuft: : Ho st: : P uppetr un subtask is in progress, check if puppet is running on the host: 84

89 Chapt er 9. T roubleshoot ing [root@ macd050992f6aa3 ~]# ps -aux grep "puppet" If the installer cannot resolve the host's domain name or Puppet Agent isn't running on the host, it means the installer has failed to reach to host. Check your installer's network and DNS settings to correct this issue Reviewing Host Report s If the host fails configuration at a Acti o ns: : Staypuft: : Ho st: : AssertR epo rtsuccess subtask, check the host reports for any commands that reported errors. Host reports provide information on each step in Puppet' s configuration process, including if the step passed or failed. This helps identify specific points of error in the configuration process. Navigate to Hosts All hosts and select the Name of the faulty host. Click the R epo rts button from the D etai l s sections. This displays a list of reports from each time a Puppet configuration ran on that host. Select the latest report to view errors that occurred on the latest configuration attempt. Scroll down the report until you find the step that caused the error. Identifying this step can help with implementing a solution to fix the configuration process the next time Puppet runs. For help with diagnosing such errors, contact a Red Hat Technical Support representative T riggering Puppet Agent After performing any solutions or workarounds on your host, trigger the Puppet Agent to run again and see if the error still occurs. Navigate to Hosts All hosts, select the Name of the host, and click R un puppet. Puppet Agent attempts to configure the host again and reports back to the installer if the error reappears or any new errors appear. Alternatively, you can run Puppet Agent manually on the host. Log into the host and enter the following command on the host to trigger the Puppet Agent to run: # puppet agent -t The -t (or --test) option enables the most common options for performing Puppet Agent configuration and reporting the results. The Puppet Agent attempts to configure the host again, reports back to the installer if the error reappears or any new errors appear, and displays these results directly on the host' s terminal screen. 85

90 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) Chapter 10. Next Steps After you have provisioned your RHEL OpenStack Platform environment, all additional configuration of services in the environment must be performed individually on the nodes in the environment. See the following documentation in the RHEL OpenStack Platform documentation suite for information on how to get started working with your environment and performing additional configuration. Important If you change the values of settings that the installer configures when it provisions a host, the newly configured values are overwritten when a Puppet run is performed on the host. To prevent these changes from being overwritten, you must stop the puppet service on the host. Administration G uide Provides an overview of how to create and manage resources in a RHEL OpenStack Platform environment using the Horizon dashboard or client commands for administrative users. Command-Line Interface Reference Provides an overview of the client software that administrators use to manage and troubleshoot a RHEL OpenStack Platform environment. Configuration Reference G uide Provides a reference for administrative users for looking up configuration options. This guide contains lists of the configuration options available with RHEL OpenStack Platform and uses auto-generation to generate options and the descriptions from the code for each project. 86

91 Appendix A. Firewall Rules Appendix A. Firewall Rules The following table outlines the firewall rules the rhel -o sp-i nstal l er command configures. The installer uses these ports to communicate with and control other machines in the environment. This table is provided for your information; no further configuration is necessary beyond that provided by rhel -o sp-i nstal l er. Table A.1. Red Hat Enterprise Linux O penstack Platform Installer Firewall Rules Ports Protocols Service Purpose 22 TCP SSH Connecting to other machines on the private network that the installer defines. 53 TCP, UD P D NS Resolving the host names and addresses of machines on the private network that the installer defines. 67 TCP D HCP Assigning IP addresses to machines on the private network that the installer defines. 69 TCP TFTP Enabling the PXE booting of machines on the private network that the installer defines. 80, 443 TCP HTTP, HTTPS The Apache web server for hosting the installer' s user interface TCP Puppet Communication between Puppet clients and the Puppet master. 87

92 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) Appendix B. New Deployment Settings This section outlines the options available when you create a new deployment. B.1. Net work Configurat ion Set t ings The following table outlines the different network traffic types available in the Netwo rk C o nfi g urati o n step of creating a new deployment. Table B.1. Network Configuration Settings Network Traffic Type P ro vi si o ni ng /P XE Manag ement External C l uster Manag ement Ad mi n AP I P ubl i c AP I T enant Sto rag e Sto rag e C l usteri ng Description Communication with the installer. For example, to provision hosts and to allow hosts to boot over the network using the PXE service that the installer provides. Private communication amongst services. Communication between instances in the RHEL OpenStack Platform environment and external network resources. This network traffic type cannot be placed on the same subnet as other network traffic types. Pacemaker cluster management communication. Administrative communication amongst services. Access to the REST API and the Horizon dashboard. Tenant network communication for instances in the RHEL OpenStack Platform environment. Storage-related communication. This network traffic type is optional. Storage-related communication for replication and data checks in Ceph clusters. This network traffic type is optional. B.2. Services Configurat ion Set t ings The following table outlines the options available in the Servi ces C o nfi g urati o n step of creating a new deployment. Table B.2. Services Configuration Settings Service O ption Description 88

93 Appendix B. New Deployment Set t ings Service O ption Description Neutro n T enant Netwo rk T ype The type of network used for tenant networks. You can choose from the following options: VXLAN Seg mentati o n: Virtual extensible LAN. A network layout that extends the functionality of a VLAN by providing a larger network segment ID range and other features. G R E Seg mentati o n: Generic routing encapsulation segmentation. A network layout in which tunnels are used to segregate and carry network traffic over individual tenant networks. VLAN Seg mentati o n: A network layout in which multiple isolated networks are defined. If you choose this option, you must also specify the tenant VLAN range. Fl at: A simple network layout in which all instances are members of the same network. 89

94 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) Service O ption Description C o re P l ug i n T ype The core network plugin. You can choose from the following options: ML2 Core Plugin The modular layer 2 plugin. If you select this plugin, you can select the following ML2 mechanism drivers: O pen vswi tch: A software-defined networking virtual switch designed to supersede the heritage Linux software bridge. Open vswitch provides switching services to virtualized networks with support for industry-standard NetFlow, OpenFlow, and sflow. L2 P o pul ati o n: Enables horizontal scaling of broadcast, multicast, and unicast traffic on large overlay networks. L2 population implements a partial mesh for ARP resolution and MAC learning traffic whereby this traffic is sent only to the necessary agent by encapsulating it as a targeted unicast. Note that if this this item is enabled, the installer sets the Layer 3 HA Configuration (l 3_ha) to false. This is due to incompatibility to having l 3_ha and l 2po p enabled. C i sco Nexus: Enables configuration of Cisco Nexus switches. If you select this option, you must enter the Swi tch Ho stname, Swi tch IP Ad d ress, Swi tch Lo g i n, Swi tch P asswo rd, SSH P o rt, and P o rt Mappi ng s. You can add additional switches by clicking Ad d Ano ther Swi tch. N1KV Core Plugin The Cisco 1000v plugin. If you select this plugin, you must also specify the details of a virtual supervisor module: VSM IP : The IP address of the virtual supervisor module. VSM P asswo rd : A password with which to authenticate with the virtual supervisor module. 90

95 Appendix B. New Deployment Set t ings Service O ption Description No va G l ance T enant Netwo rk T ype Fl o ati ng IP rang e fo r external netwo rk Fi xed IP rang e fo r tenant netwo rks C ho o se D ri ver Backend Fl at wi th D HC P : A simple network layout in which all instances are members of the same network, and the DHCP service is also provided. VLAN: A network layout in which multiple isolated networks are defined. If you choose this option, you must also specify the tenant VLAN range. A range of IP addresses to be used for external networks. Ranges must be entered using CID R notation. For example, XX. XX. XX. 0 /24. A range of IP addresses to be used for tenant networks. Ranges must be entered using CID R notation. For example, XX. XX. XX. 0 /24. The driver to use for back-end storage of images. You can choose from the following options: Lo cal Fi l e: The local file system. This option is only available in deployments without high availability. C eph: Ceph storage. NFS: Network file system storage. If you select this option, you must also specify the NFS address in the netwo rk path text field. C i nd er C ho o se D ri ver Backend The volume driver to use for back-end storage. You can choose from the following options: LVM: Logical volume manager storage. This option is only available for deployments without high availability. NFS: Network file system storage. If you select this option, you must also specify the NFS address in the NFS UR I text field. C eph: Ceph storage. Eq ual Lo g i c: For EqualLogic storage attached network systems. If you select this option, you must also specify the details of the storage attached network, including the SAN IP Ad d r, SAN Lo g i n, SAN P asswo rd, P o o l, and G ro up. NetApp for NetApp storage systems. If you select this option, you must also specify the details of at least one storage system. The options for these fields change depending on what you choose for the Sto rag e Fami l y, and Sto rag e P ro to co l. You can add additional storage systems by clicking the Ad d Ano ther NetApp Sto rag e System. 91

96 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) Appendix C. Configuring the RHEL OpenStack Platform Installer The configuration required to provision Red Hat Enterprise Linux OpenStack Platform is performed automatically when you run the rhel -o sp-i nstal l er script, but you can also manually configure other aspects such as the location of an installation media entry, or the credentials of a Customer Portal account used to register machines with the Content D elivery Network. The information in this chapter is provided as a reference for updating the existing values specified during the installation process or for performing additional configuration. C.1. Inst allat ion Media Installation media are sources of files that the installer can use to install the base operating system on a machine when you provision RHEL OpenStack Platform. Installation media must be in the format of an operating system installation tree, and must be accessible to the machine hosting the installer through a HTTP URL. Note For information on how to use a CD or ISO file to prepare an installation tree, see Section 3.4, Preparing the Installation Medium. Note By default, the rhel -o sp-i nstal l er command prompts you to specify the location of an installation medium during the installation process, and creates a default installation media entry based on this location. If you skipped this step when running rhel -o sp-i nstal l er, you must manually edit the R ed Hat mi rro r installation media entry and specify the location of a Red Hat Enterprise Linux 7 installation medium before you can provision RHEL OpenStack Platform. Create an installation media entry in the user interface to represent an installation medium for installing a base operating system on a machine when you provision RHEL OpenStack Platform. Procedure C.1. Creating an Installation Media Entry 1. From the title bar in the main screen of the user interface, click Hosts Installation Med ia. 92

97 Appendix C. Configuring t he RHEL O penst ack Plat form Inst aller Figure C.1. The Installation Media Menu Entry 2. Click New Med i um. 3. In the Name text field, enter a name to represent the installation media entry in the user interface. 4. In the P ath text field, enter the path of a URL or an NFS share containing the installation tree. The following variables can be used in the path to represent multiple different system architectures and versions: $arch The system architecture, for example x86 _6 4. $versi o n $majo r $mi no r The operating system version, for example The operating system major version, for example 7. The operating system minor version, for example 0. 93

98 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) Example C.1. HTTP Path Example C.2. NFS Path nfs://download.example.com:/rhel/$version/server/$arch/os/ 5. Select R ed Hat from the O perati ng system fami l y list. 6. Click Submi t. If you did not configure an installation media entry when running rhel -o sp-i nstal l er, you must manually specify an installation media entry for Red Hat Enterprise Linux 7 the installer can use for provisioning. The following procedure assumes you have already created an installation media entry. Procedure C.2. Specifying the Installation Media Entry for Provisioning 1. From the title bar in the main screen of the user interface, click Configure Host groups. 2. Click the base_r ed Hat_7 host group. 3. Click the O perati ng System tab. 4. Select an installation media entry from the Med i a list. 5. Click Submi t. You have specified the installation media entry that the installer uses to install the base operating system on hosts when provisioning a RHEL OpenStack Platform environment. C.2. Operat ing Syst ems An operating system entry is a collection of options that defines the way in which the base operating system is installed on a host when you provision Red Hat Enterprise Linux OpenStack Platform. Operating system entries combine other entries in the user interface, such as installation media for installing the base operating system on a host and partition tables that define the partitioning scheme for the storage available to that host, and allow you to specify parameters specific to the operating system entry, such as the details of a Subscription Manager account. Note By default, the rhel -o sp-i nstal l er command creates an operating system entry for Red Hat Enterprise Linux 7.2 that contain the details of the subscription manager account you entered during the installation process. These operating system entries can be edited as necessary. Procedure C.3. Creating an O perating System Entry 1. Click Hosts O perating systems. 94

99 Appendix C. Configuring t he RHEL O penst ack Plat form Inst aller 2. Click New O perati ng system. Figure C.2. The New O perating System Page 3. Configure general operating system details: a. In the Name text field, enter a name to represent the operating system entry in the Red Hat Enterprise Linux OpenStack Platform installer. b. In the Majo r versi o n, enter the number corresponding to the major version of the operating system. c. In the Mi no r versi o n, enter the number corresponding to the minor version of the operating system. d. In the D escri pti o n text field, enter a description to represent the operating system entry in the Red Hat Enterprise Linux OpenStack Platform installer. e. From the O S Fami l y drop-down menu, select the operating system family to which the operating system belongs. f. In the Archi tectures section, select the check boxes for the architectures that the operating system entry can provision. 4. Configure the partition tables that the operating system entry can access: a. Click the P arti ti o n tabl e tab. b. In the Al l i tems list, click the name of a partition table entry to move that partition table entry to the Sel ected i tems list. 5. Configure the installation media that the operating system entry can access: a. Click the Instal l ati o n med i a tab. 95

100 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) b. In the Al l i tems list, click the name of an installation media entry to move that installation media entry to the Sel ected i tems list. 6. Click Submi t. You have created a new operating system entry that can be used to provision a host. By default, the installer creates an operating system entry for Red Hat Enterprise Linux 7.2 and populates the values for this operating system entry automatically based on the information you provide during the installation process. You do not need to manually configure this operating system entry to provision Red Hat Enterprise Linux OpenStack Platform 6.0 on Red Hat Enterprise Linux 7.2, but you can edit this operating system entry to update the values of the parameters such as Subscription Manager credentials and the repositories to enable on machines that the installer provisions. Procedure C.4. Updating the Values of O perating System Entry Parameters 1. Click Hosts O perating systems. 2. Click R ed Hat 7. 2 to open the details page for the Red Hat Enterprise Linux 7.2 operating system entry. 3. Click the P arameters tab. 4. Update the values of the parameters using the text fields for each parameter. 5. Click Submi t. You have updated the values of the parameters. These parameters are applied to any machines newly provisioned using the Red Hat Enterprise Linux 7.2 operating system entry. The following is a list of common parameters you can specify in an operating system entry. To provision Red Hat Enterprise Linux OpenStack Platform based on an operating system entry, you must specify the parameters for a Subscription Manager account that can be used to install packages on the hosts being provisioned. You can also specify parameters for other options such as the location of a NTP server. Table C.1. Common O perating System Entry Parameters Parameter ntp-server subscri pti o n_manag er subscri pti o n_manag er_repo s subscri pti o n_manag er_po o l Description The address of an NTP server with which to synchronize the system clock. Whether or not to use Subscription Manager. Accepted values are true or fal se. A comma-separated list of repositories to enable. The repository required to provision RHEL OpenStack Platform on Red Hat Enterprise Linux 7.2 is rhel -7-servero penstack rpms along with rhel -7-servero penstack i nstal l er-rpms, rhel -7-serverrh-co mmo n-rpms, and rhel -ha-fo r-rhel -7-serverrpms. The ID of an entitlement pool to attach. You can only specify the ID of a single entitlement pool. This value is optional, but recommended; if you do not specify an entitlement pool ID, the installer attempts to auto-attach the required entitlements to hosts it provisions. 96

101 Appendix C. Configuring t he RHEL O penst ack Plat form Inst aller Parameter subscri pti o n_manag er_usernam e subscri pti o n_manag er_passwo r d http-pro xy http-pro xy-po rt http-pro xy-user http-pro xy-passwo rd ti me-zo ne Description The username of a Customer Portal account by which to register the host with the Content D elivery Network. The password of a Customer Portal account by which to authenticate the above username. The IP address or fully qualified domain name of a HTTP proxy for Subscription Manager. The port by which to connect to the HTTP proxy for Subscription Manager. The name of the user by which to authenticate with the HTTP proxy for Subscription Manager. The password by which to authenticate with the HTTP proxy for Subscription Manager. The time zone to apply to the host. Time zones 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. C.3. Provisioning T emplat es A provisioning template is a collection of settings that defines the way in which a base operating system is installed on a host, and corresponds to a kickstart file for Red Hat Enterprise Linux systems. In the user interface, you can create and work with standalone provisioning templates in which all required settings are contained in a single template, and blocks of code that can be used across multiple provisioning templates, such as snippets, post-installation scripts, and generic installation scripts. Note The default provisioning template used to provision hosts in a RHEL OpenStack Platform environment can be edited as necessary to configure custom options. However, options that are configured using dedicated user interface elements, such as the root password, time zone, or custom repos, must be configured using the relevant operating system parameter or deployment option. Create a new provisioning template entry. Procedure C.5. Creating a Provisioning Template 1. From the title bar in the main screen of the user interface, click Hosts Provisioning templates. 2. Click New T empl ate. 3. Configure general provisioning template details: a. Enter a name for the provisioning template in the Name field. b. Enter the body of the provisioning template in the T empl ate ed i to r text area. c. Enter a comment describing the creation of the provisioning template in the Aud i t C o mment field. 4. Configure the provisioning template type: 97

102 Deploying O penst ack: Ent erprise Environment s (Red Hat Ent erprise Linux O penst ack Plat form Inst aller) a. Click the T ype tab. b. Select Sni ppet to designate the provisioning template as a snippet. A snippet is not a standalone provisioning template, but a part of a provisioning template that can be inserted into other provisioning templates. c. If you did not select the Sni ppet check box, select the type of the provisioning template from the T ype list: P XELi nux: A PXELinux template. P XEG rub: A PXEGrub template. i P XE: An ipxe template. P ro vi si o n: The main provisioning template, such as a kickstart file for Red Hat Enterprise Linux systems. fi ni sh: A post-installation script such as that specified in a kickstart file for Red Hat Enterprise Linux systems. scri pt: A generic script that can be run during the provisioning process, such as that specified in a kickstart file for Red Hat Enterprise Linux systems. user_d ata: A user_d ata block. ZT P : A Zero Touch Provisioning template. 5. Configure the provisioning template associations: a. Click the Asso ci ati o ns tab. b. From the Al l i tems list in the Appl i cabl e O perati ng Systems section, click the name of an operating system entry to move that operating system entry to the Sel ected i tems list and make the provisioning template available to that operating system entry. c. Optionally, click Ad d co mbi nati o n and select a host group from the Ho st G ro up list or an environment from the Envi ro nment list to make the provisioning template available to the specified combination of host groups and environments. 6. Click Submi t. Lock a provisioning template to prevent users from editing its properties. Procedure C.6. Locking a Provisioning Template 1. From the title bar in the main screen of the user interface, click Hosts Provisioning templates. 2. Click the disclosure arrow next to the C l o ne button for the provisioning template. 3. Click Lo ck. 98

103 Appendix C. Configuring t he RHEL O penst ack Plat form Inst aller Figure C.3. The Lock button 4. Click O K when prompted. You have locked the provisioning template, and users cannot edit the properties of that provisioning template other than its associations. You must unlock the provisioning template to edit any other properties. C.4. Part it ion T ables A partition table is a set of directives that defines the way in which the Red Hat Enterprise Linux OpenStack Platform installer configures the disks available to machines it provisions. Partition tables are applied to operating system entries. Note The default partition table entry applied to Red Hat Enterprise Linux systems is Ki ckstart d efaul t. This partition table entry uses only the first disk available to the machine being provisioned; advanced configuration involving multiple disks must be manually configured. You can edit this partition table entry to configure the preferred partitioning scheme, or create a new partition table entry and specify that entry in the Red Hat Enterprise Linux operating system entry. You can create new partition table entries that define custom partitioning schemes. Procedure C.7. Creating a Partition Table Entry 1. Click Hosts Partition tables. 2. Click New P arti ti o n T abl e. 3. In the Name text field, enter a name to represent the partition table in the user interface. 4. In the Layo ut text area, enter the layout for the disk partition: Example C.3. Red Hat Enterprise Linux Partition Table zerombr clearpart --all --initlabel autopart 99