HP Helion CloudSystem 9.0 Update 1 Installation Guide

HP Helion CloudSystem 9.0 Update 1 Installation Guide About this guide This information is for use by administrators using HP Helion CloudSystem Software 9.0 Update 1, who are assigned to configure and provision compute resources for deployment and use in virtual data centers. HP Part Number: 5900-4371e Published: November 2016 Edition: 6

Copyright 2014 2016 Hewlett-Packard Development Company, L.P. Microsoft and Windows are trademarks of the Microsoft group of companies. Red Hat is a registered trademark of Red Hat, Inc. in the United States and other countries. VMware vcenter and VMware vsphere are registered trademarks of VMware, Inc. in the United States and/or other jurisdictions. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Edition Publication date CloudSystem version Edition notes 1 December 2015 9.0 Update 1 Initial edition 2 March 2016 9.0 Update 1 Clarified step 12, Configure shared GFS storage in the cluster, in Configure a management cluster (page 61). Clarified step 2, Create xml files, in Finish RHEL 7.0/7.1 cluster configuration (page 73) and Finish RHEL 6.5 cluster configuration (page 79). Clarified step 2, Turn off Red Hat Subscription Manager, in Preparing the YUM repository and loading tools (page 58). 3 June 2016 9.0 Update 1 Added steps for replacing the app.json file on the Enterprise appliances after applying an HP CSA patch in HP CSA 4.5 patch 2 (page 45). 4 June 2016 9.0 Update 1 Changed step 10, the create stonith command, to add a cipher parameter which is required in RHEL 7.1 in Preparing the three nodes in the cluster (page 61). 5 October 2016 9.0 Update 1 In Running the First-Time Installer (page 23), added a note that if you are using DHCP, you must specify the gateway for the respective network in the FTI. Updated and clarified the steps in Apply HP CSA 4.5 patch 2 (page 45). 6 November 9.0 Update 1 In Preparing the three nodes in the cluster (page 61), added step 12c, reboot each 2016 node in the KVM cluster. In Finish RHEL 7.0/7.1 cluster configuration (page 73), step 2, added that the hpcs-*.xml files must be created in the /CloudSystem directory.

Contents I HP Helion CloudSystem Installation Overview...7 1 Before you begin...8 2 Installation considerations...9 Audience and assumptions...9 Audience...9 Assumptions...9 Understanding the installation process...10 3 Understanding appliance names in CloudSystem...12 II ESXi Environment Installation...14 4 Configure the ESXi management hypervisor...15 Configure the networks accessible to the server...15 Install the operating system...16 Set network interface settings on the ESXi management host...16 Create the ESXi management cluster in vcenter, configure the network infrastructure and upload OVAs...17 Configure the management cluster and add the ESXi hypervisors...17 Download and prepare installation images and tools...18 Upload HP Helion CloudSystem images to vcenter...19 5 Create the first Management appliance...20 Install the Enterprise and Monitoring appliance drivers...21 6 Run the First-Time Installer in an ESXi environment...23 First-Time Installer field descriptions...23 7 Verify ESXi installation...28 8 Set up trunk uplinks...30 9 Installation errors...31 10 CloudSystem user interfaces...32 11 Install additional CloudSystem components...33 III CloudSystem 9.0 Update 1 patch...34 12 Back up the CloudSystem 9.0 virtual appliances and compute nodes...35 Create a snapshot of CloudSystem ESXi virtual machines...35 Create a copy of KVM virtual appliance images...36 Create a backup of compute nodes...36 13 Verify that the CloudSystem environment is ready for an update...38 14 Install the CloudSystem 9.0 Update 1 patch...39 Updating CloudSystem appliances...39 Downloading, uploading, and installing the update file...40 Retry update from the command line...41 Post-update ESXi compute cluster requirements...41 HP OO post-update connection issues...42 15 Roll back the update patch...43 16 HP CSA 4.5 patch 2...45 Apply HP CSA 4.5 patch 2...45 Contents 3

IV Appendix...47 A CloudSystem Installation Planning Worksheet...48 B Synchronize NTP servers...52 C Command line interfaces...53 csstart commands...53 Installation CLI tasks...54 Using the csstart CLI to install the first CloudSystem Management appliance...54 Enabling REST API for storage drivers...54 D KVM management hypervisor installation...56 Prepare the KVM hypervisors...57 Configure a management cluster...61 Configure a RHEL 7.1/7.0 management cluster...61 Configure a RHEL 6.5 management cluster...63 Load Qcow2 images...65 Create all appliances on node 1...66 Install the Monitoring appliance and Enterprise appliance drivers...67 (Optional) Increasing virtual appliance deployment timeout in RHEL 6.5 deployments...68 Run the CloudSystem First-Time Installer...68 First-Time Installer field descriptions...68 Set up trunk uplinks in KVM single node configurations...72 Finish cluster configuration...73 Finish RHEL 7.0/7.1 cluster configuration...73 Finish RHEL 6.5 cluster configuration...79 Health checks...84 Performing database health checks for Monitoring appliances...85 Installing additional CloudSystem components...87 E vcenter and CloudSystem optional configurations...88 Installing CloudSystem when vcenter and CloudSystem share the same host/cluster...88 Migrating standard vswitches to distributed vswitches...89 F Using cshaupdate to set virtual router IDs and change deployment timeout settings...91 G Support and other resources...92 Information to collect before contacting HP...92 How to contact HP...92 Registering for software technical support and update service...92 HP authorized resellers...92 Documentation feedback...92 Related information...93 HP Helion CloudSystem documents...93 HP Helion OpenStack documents...94 HP Insight Management documents...94 Third-party documents...94 HP 3PAR StoreServ documents...95 HP VSA StoreVirtual documents...95 HP ProLiant servers documents...95 4 Contents

Figures 1 CloudSystem installation process...10 2 vcenter after running the CloudSystem Management Appliance Installer...21 3 Progress bar in the First-Time Installer...23 4 vcenter view of Management trunk after running the First-Time Installer...28 5 vcenter view of Data trunk after running the First-Time Installer...28 6 vcenter view of Storage trunk after running the First-Time Installer...29 7 Progress bar in the First-Time Installer...68 8 luci GUI...81 Tables 1 Installation checklist...10 2 CloudSystem user interfaces...32 3 CloudSystem Installation Planning Worksheet...48 4 csstart commands...53 5 Default CloudSystem virtual appliance names...82 Procedures 1 Setting the Data Center Management Network interface settings...16 2 Configuring the cluster and adding the management hypervisor...17 3 Preparing the CloudSystem virtual machine images...19 4 Creating the first Management appliance...20 5 Installing the Monitoring appliance and Enterprise appliance driver...21 6 Running the First-Time Installer...23 7 Configuring trunk uplinks...30 8 Cleaning up after a failed installation...31 9 Creating a snapshot of CloudSystem ESXi virtual machines...35 10 Creating a copy of KVM virtual appliance images...36 11 Creating a snapshot of ESXi OVSvApp virtual machines...37 12 Creating a backup of Hyper-V compute nodes...37 13 Verifying the CloudSystem environment...38 14 Downloading the update file to your local computer...40 15 Uploading and installing the update file...40 16 Retrying the update from the command line...41 17 Preparing ESXi compute cluster for activation after an update...42 18 Reconfigure the HP OO URL to point to the Consumer Access Network VIP...42 19 Restoring CloudSystem 9.0 after a failed update...43 20 Restoring CloudSystem 9.0 ESXi compute hosts after a failed update...43 21 Restoring Hyper-V compute nodes after a failed update...43 22 Cleaning up after applying an update patch...44 23 Download and copy the patch to the Enterprise appliances...45 24 Stop search and services...45 25 Back up the app.json file and install the patch on each Enterprise appliance...45 26 Start search and services...46 27 Synchronizing the management hypervisor and the external time server...52 28 Using the csstart CLI to install the first CloudSystem Management appliance...54 29 Enabling REST API for storage drivers...55

30 Configuring a temporary network...57 31 Preparing the YUM repository and loading tools...58 32 Installing the RPMs on each node of the cluster...59 33 Setting up the DNS connection...59 34 Installing OpenvSwitch on the management hypervisor...60 35 Preparing the three nodes in the cluster...61 36 Preparing the three nodes in the cluster...63 37 Creating the three-node cluster using the luci web interface...64 38 Using CloudSystem Management Appliance Installer to create the first Management appliance...66 39 Installing the Monitoring appliance and Enterprise appliance driver...67 40 Running the First-Time Installer...69 41 Setting trunk uplinks in the KVM single node management hypervisor...73 42 Configuring RHEL 7.0/7.1 clusters...73 43 Starting and registering appliance virtual machines...75 44 Configuring RHEL 6.5 clusters...79 45 Checking health of Management appliances, Cloud controllers, Update appliance and SDN appliance from the HA Proxy...85 46 Checking health of Management appliances, Cloud controllers, Update appliance and SDN appliance through the Monitoring dashboard...85 47 Performing a database health check after starting multiple Monitoring appliances...85 48 Recovering the database after a failed health check when one Monitoring appliance is in a DOWN state...85 49 Recovering the database after a failed health check when all Monitoring appliance are in a DOWN state...86 50 Forcing an initializing monitoring appliance into a DOWN state...86 51 Using csstart via the command line interface to create the first Management appliance...88 52 Migrating standard switches to distributed switches...89 53 Configuring virtual router IDs...91

Part I HP Helion CloudSystem Installation Overview

1 Before you begin HP Helion CloudSystem is a robust product that requires a very precise installation. Make sure that you understand the following aspects of the product before attempting installation: CloudSystem architecture See the Understanding CloudSystem part of the HP Helion CloudSystem 9.0 Update 1 Administrator Guide in the Enterprise Information Library. CloudSystem networking See the HP Helion CloudSystem 9.0 Update 1 Network Planning Guide in the Enterprise Information Library. CloudSystem resource requirements and supported hardware, software and tools. See the HP Helion CloudSystem 9.0 Update 1 Support Matrix in the Enterprise Information Library. CloudSystem migration requirements If you plan to migrate your CloudSystem 8.1 Update 2 environment to CloudSystem 9.0 Update 1, see the HP Helion CloudSystem Migration Guide: 8.1 Update 2 to 9.0 Update 1 in the Enterprise Information Library. When configuring the hardware supporting your CloudSystem environment, you should refer to the applicable best practice recommendations outlined in the documents below: HP 3PAR StoreServ Storage and VMware vsphere 6 best practices HP 3PAR StoreServ Storage and VMware vsphere 5 best practices HPE 3PAR VMware ESX/ESXi Implementation Guide 8 Before you begin

2 Installation considerations CloudSystem supports several different configuration scenarios. This installation guide explains how to install the following CloudSystem configuration: ESXi management cluster with three management hosts KVM instructions are available in the appendix. See KVM management hypervisor installation (page 56). CloudSystem installers run in a Windows staging environment Centralized Virtual Routing Enterprise appliance included in the initial installation If your CloudSystem configuration requires a different path, consult the guidelines in the appendix for additional support. Audience and assumptions Audience Assumptions This guide is intended for experienced system administrators with a working knowledge of the following concepts. Top of Rack (ToR) switches for networking CLI commands for Windows and Linux VMware vcenter functionality VMware distributed vswitches Secure shell (ssh) and secure copy (scp) commands If you plan to use the OpenStack CLI and APIs to manage some of the cloud resources from the command line, it is helpful to have experience with OpenStack technologies such as Nova, Glance, Cinder, Keystone and Neutron. This installation guide makes the following assumptions about your readiness for the installation. Make sure these assumptions match the state of your environment before you begin the installation. All hardware required to support a CloudSystem installation is installed and configured. If you are using VMware vsphere, then VMware vcenter is installed and ready to connect to CloudSystem. If you plan to use block storage, then an HP 3PAR StoreServ or HP StoreVirtual VSA storage system is configured and ready to connect to CloudSystem. If you plan to use object storage, then you have four servers dedicated for object storage. A minimum of two servers are required for Swift PAC and two servers are required for Swift Object. HP also recommends that you use an external load balancer in a production environment. If you choose not to add the external load balancer, you can use HA Proxy on the Cloud controller. You have a list of user names and passwords for VMware vcenter and your storage systems. You have prepared a list of IP addresses that you can assign to CloudSystem virtual appliances. NOTE: Use the CloudSystem Installation Planning Worksheet to gather all of the networking and appliance details required to complete a CloudSystem installation. See CloudSystem Installation Planning Worksheet (page 48). Audience and assumptions 9

Understanding the installation process A high-level overview of the CloudSystem installation path is provided in the image below. The grey boxes indicate steps that are not covered in this guide. Figure 1 CloudSystem installation process 1 Configure hardware (TOR switches) 2 Prepare VMware vcenter 3 Run the Cloud Management Appliance Installer 4 Run the CloudSystem First-Time Installer 5 Finish resource configuration (Operations Console) TIP: Carefully review this checklist and make sure that you understand each step of the installation. Use the reference links provided if you need additional information. Table 1 Installation checklist Installation step Step 1: Prepare your management cluster hardware. This guide does not cover the specific steps required to accomplish this. Review the Support Matrix for a list of supported hardware, software and tools and verify that your environment meets all requirements. See the HP Helion CloudSystem 9.0 Update 1 Support Matrix in the Enterprise Information Library. Add required CloudSystem networks to the network environment of the management cluster and give each network a unique VLAN ID. See the HP Helion CloudSystem 9.0 Update 1 Network Planning Guide in the Enterprise Information Library. Step 2: Prepare VMware vcenter, add management hypervisors to the cluster and load OVAs. In this guide, see Configure the networks accessible to the server (page 15). Step 3: Launch the Cloud Management Appliance Installer to deploy the Management appliance and set up the Data Center Management Network. In this guide, see Create the first Management appliance (page 20). 10 Installation considerations

Table 1 Installation checklist (continued) Installation step Step 4: Launch the First-Time Installer to create the virtual appliances and configure networking. In this guide, see Run the First-Time Installer in an ESXi environment (page 23). Step 5: Configure cloud resources using the Operations Console. This guide does not cover these specific steps. See the HP Helion CloudSystem 9.0 Update 1 Administrator Guide in the Enterprise Information Library. Understanding the installation process 11

3 Understanding appliance names in CloudSystem Before you install CloudSystem, it is important to understand how the virtual machines are identified in the cloud environment. Management appliances CloudSystem identifies the Management appliances in the trio by the internal name assigned on the Cloud Management Network. ma1: the first Management appliance in the trio. This is the Management appliance that is installed by the CloudSystem Management Appliance Installer. ma2: the second Management appliance in the trio. ma3: the third Management appliance in the trio. You should always access a Management appliance through the first Management appliance in the trio: Accessing the Management appliances 1. Using cloudadmin credentials, SSH in to ma1. 2. From ma1, SSH to the other Management appliance you want to access. IMPORTANT: When performing maintenance on a virtual machine hosting the Management appliances, make sure that ma1 is always the last node shut down and the first node restarted. Cloud controllers CloudSystem identifies the Cloud controllers in the trio by the internal name assigned on the Cloud Management Network. cmc: the first Cloud controller in the trio. cc1: the second Cloud controller in the trio. cc2: the third Cloud controller in the trio. You should always access a Cloud controller through the first Management appliance (ma1). Accessing the Cloud controllers 1. Using cloudadmin credentials, SSH in to ma1. 2. From ma1, SSH to the Cloud controller you want to access. IMPORTANT: When performing maintenance on a virtual machine hosting the Cloud controllers, make sure that cmc is always the last node shut down and the first node restarted. Enterprise appliances CloudSystem identifies the Enterprise appliances in the trio by the internal name assigned on the Cloud Management Network. ea1: the first Enterprise appliance in the trio. ea2: the second Enterprise appliance in the trio. ea3: the third Enterprise appliance in the trio. You should always access an Enterprise appliance through the first Management appliance in the trio: 12 Understanding appliance names in CloudSystem

Accessing the Enterprise appliances 1. Using cloudadmin credentials, SSH in to ma1. 2. From ma1, SSH to the Enterprise appliance you want to access. IMPORTANT: When performing maintenance on a virtual machine hosting the Enterprise appliances, make sure that ea1 is always the last node shut down and the first node restarted. Monitoring appliances CloudSystem identifies the Monitoring appliances in the trio by the internal name assigned on the Cloud Management Network. mona1: the first Monitoring appliance in the trio. mona2: the second Monitoring appliance in the trio. mona3: the third Monitoring appliance in the trio. You should always access a Monitoring appliance through the first Management appliance (ma1). Accessing the Monitoring appliances 1. Using cloudadmin credentials, SSH in to ma1. 2. From ma1, SSH to the Monitoring appliance you want to access. IMPORTANT: When performing maintenance on a virtual machine hosting the Monitoring appliances, make sure that mona1 is always the last node shut down and the first node restarted. Update appliance An Update appliance is deployed during first-time installation. The Update appliance controls the distribution of files to the other appliances and compute nodes. CloudSystem identifies the Update appliance by the internal name assigned on the Cloud Management Network. For the Update appliance, this is ua1. If you need to log on to the Update appliance for maintenance or management tasks, SSH in to the first Management appliance (ma1), then SSH to ua1. Optionally, you can connect directly to the Data Center Management Network IP address for the Update appliance. SDN appliance An SDN appliance is deployed during first-time installation, if your environment was deployed with a VxLAN network configuration. CloudSystem identifies the SDN appliance by the internal name assigned on the Cloud Management Network. For the SDN appliance, this is sdn1. If you need to log on to the SDN appliance for maintenance or management tasks, SSH in to the first Management appliance (ma1), then SSH to sdn1. More information See the Shut down and restart CloudSystem appliances chapter in the HP Helion CloudSystem 9.0 Update 1 Administrator Guide in the Enterprise Information Library. 13

Part II ESXi Environment Installation

4 Configure the ESXi management hypervisor Process overview Configure the networks accessible to the server (page 15) Install the operating system (page 16) Set network interface settings on the ESXi management host (page 16) Create the ESXi management cluster in vcenter, configure the network infrastructure and upload OVAs (page 17) CloudSystem supports two management cluster configurations in vcenter: A management cluster with three hosts is strongly recommended. This configuration offers high availability and performance benefits for robust production use. A management cluster with a single host is supported for small development, test, or production environments where physical high availability is not a requirement. Single host management clusters can support a maximum of 32 compute nodes and 1280 VM instances. If you plan to use this configuration, your single host must have enough resources to support a full CloudSystem deployment. CloudSystem includes 13 virtual appliances in a VLAN configuration or 14 virtual appliances in a VxLAN configuration. All of these appliances are installed on the single node. For virtual appliance resource requirements, see the HP Helion CloudSystem 9.0 Update 1 Support Matrix in the Enterprise Information Library. NOTE: You can install CloudSystem on a single host and later decide to add hosts to the management cluster. See the Manage the management hypervisor cluster chapter of the HP Helion CloudSystem 9.0 Update 1 Administrator Guide in the Enterprise Information Library. Configure the networks accessible to the server In the network infrastructure that leads up to the physical server, configure three trunks: Management, Cloud Data and Storage. The following networks are included in each trunk as part of the CloudSystem installation process. Management trunk Tagged networks include: Data Center Management Network If you plan to migrate from CloudSystem 8.1 Update 2 (U2) to CloudSystem 9.0 Update 1 (U1), make sure that the VLAN ID you assign is the same VLAN ID assigned to the Data Center Management Network in the 8.1 U2 environment. You must also have a range large enough to accommodate IP addresses for resources in both environments. If you do not have a range that can support the required number of IP addresses, you can use a different Data Center Management Network for each environment, as long as they are routed together to allow CloudSystem 9.0 U1 appliances to access CloudSystem 8.1 U2 appliances. Cloud Management Network Do not configure DHCP on this network and do not allow network service traffic to use this network. If you plan to migrate from CloudSystem 8.1 U2 to CloudSystem 9.0 U1, make sure that the VLAN ID you assign is different from the VLAN ID assigned to this network in CloudSystem 8.1 U2. Configure the networks accessible to the server 15

Consumer Access Network If you plan to migrate from CloudSystem 8.1 U2 to CloudSystem 9.0 U1, make sure that the VLAN ID you assign is the same VLAN ID assigned to the Consumer Access Network in the 8.1 U2 environment. You must also have a range large enough to accommodate IP addresses for resources in both environments. External Network If you plan to migrate from CloudSystem 8.1 U2 to CloudSystem 9.0 U1, make sure that the VLAN ID you assign is the same VLAN ID assigned to the External Network in the 8.1 U2 environment. Untagged networks include: PXE Network Cloud Data trunk Multiple Provider and Tenant Networks are created from this trunk. If you are configuring a VLAN environment, assign a range of VLANs for Tenant and Provider Networks. If you are configuring a VxLAN environment, assign an underlay VLAN to the Cloud Data Trunk for carrying Tenant and Provider Networks. If you plan to migrate from CloudSystem 8.1 U2 to CloudSystem 9.0 U1, you can only configure a VLAN environment and the VLAN ID assigned to the Cloud Data Trunk must be the same as the VLAN ID assigned to the Cloud Data Trunk in CloudSystem 8.1 U2. Migration does not support VxLAN. Storage trunk All networks in this trunk are tagged. Block Storage Network Object Proxy Network Install the operating system Install a supported version of the ESXi operating system on each management hypervisor in the management cluster. For a list of supported operating systems, see the HP Helion CloudSystem 9.0 Update 1 Support Matrix in the Enterprise Information Library. Set network interface settings on the ESXi management host During the first boot, the ESXi management hypervisor should have vmnic0, vmnic1, and vmnic2 interfaces up. The host is not network ready until you configure the network to match the server profile. Procedure 1 Setting the Data Center Management Network interface settings 1. Log in to the ESXi host console and select Configure Management Network. This is the Data Center Management Network. 2. In the VLAN section, enter the Data Center Management Network VLAN ID. 3. In the IP Configuration section, add the IP address of the hypervisor. 4. Save and restart the network. 5. To verify that the network is configured properly, ping the Data Center Management IP address. 16 Configure the ESXi management hypervisor

Create the ESXi management cluster in vcenter, configure the network infrastructure and upload OVAs Configure the management cluster and add the ESXi hypervisors Prerequisites You have administrator privileges to log in to VMware vcenter. One large datastore is created with 8 TB of storage (plus any glance storage you require) to support the virtual appliance boot drives. Additional storage is also available for OpenStack images. If a trio of management hosts is configured in the cluster, all hosts share the same volume. Your VMware vcenter name does not contain spaces. The cluster where CloudSystem will be installed is configured to use distributed vswitches. If standard vswitches are present, you must migrate them before starting the CloudSystem installation. See vcenter and CloudSystem optional configurations (page 88). NOTE: If you have a mixture of different versions of ESXi hosts in your environment and you have an existing distributed vswitch (DVS) that you want to reuse, then make sure that you have created the DVS with the oldest version of ESXi on the hosts. For example, if you have three ESXi 5.5 hosts and one ESXi 5.1 host and you want to use your existing DVS, then the DVS must be version ESXi 5.1. All port groups inside the distributed vswitch where the Data Center Management Network is located have the same load balancing policy. During installation, port groups are created based on the load balancing policy already configured on the existing port groups. A consistent policy ensures a smooth configuration of new port groups. If DRS is enabled in vcenter to manage cluster resources for multiple hosts, then it is configured according to VMware best practices. Procedure 2 Configuring the cluster and adding the management hypervisor 1. Log in to vcenter with the administrator user name and password. NOTE: Do not use unsupported vcenter password characters. You can find a list of unsupported characters on the VMware Knowledge Base. You must use a local administrator account (not a domain administrator account). 2. In the data center that supports CloudSystem, create the management cluster. 3. Add your hosts to the cluster. a. Right-click on the cluster and select Add Host. b. Enter the IP address of the ESXi hypervisor that you configured in the previous section. c. Enter the credentials. d. Take all default options. e. Repeat until all hosts are added. Create the ESXi management cluster in vcenter, configure the network infrastructure and upload OVAs 17

4. Verify that you have the following minimum networking pieces configured for each host that you added to the cluster: One distributed vswitch with a name that is unique across all switches in vcenter VMware vmkernel Management trunk VLAN ID is the same as the VLAN ID assigned to the Data Center Management Network If you are using standard switches for the switch that includes the VM management network, migrate that switch from standard to distributed for the ESXi hypervisor you just added to the cluster. 5. Configure each host in the cluster to use an external time server. See Configuring Network Time Protocol (NTP) on ESX/ESXi hosts using the vsphere Client Download and prepare installation images and tools The HP Helion CloudSystem 9.0 release kit is downloaded from Software Depot at www.hp.com/ go/cloudsystem/download. You will need the following release files to perform the procedures in this chapter. HP Helion CloudSystem Enterprise ESXi 9.0-Sept 2015: Contains the OVA image for the Enterprise virtual appliance. HP Helion CloudSystem Foundation ESXi 9.0-Sept 2015: Contains the OVA images for the Management appliance, Cloud controller, Monitoring appliance, SDN appliance, and Update appliance. HP Helion CloudSystem Tools 9.0-Sept 2015: linux-csstart.tar.gz: Contains the command line to install CloudSystem from a Linux system. windows-csstart.zip: Contains the command line to install CloudSystem from a Windows system. The csstartgui.bat is part of this zip file, which launches the CloudSystem Management Appliance Installer. cs-ovsvapp.ova: OVA image for the OVSvApp appliance, which provides security for ESXi compute hosts. You will prepare this image when you create ESXi compute clusters. See the Compute node creation chapter of the HP Helion CloudSystem 9.0 Update 1 Administrator Guide in the Enterprise Information Library. hlinux_hotrod.iso: supports object storage (OpenStack Swift) deployment. CloudSystemClient-linux-9.0.0.tar.gz: Installs the Linux version of the commands for OpenStack Keystone, Nova, Neutron and Cinder. CloudSystemClient-windows-9.0.0.zip: Installs the Windows version of the commands for OpenStack Keystone, Nova, Neutron and Cinder. MySQL-ConnectorJ.zip: Contains an updated driver for the Monitoring and Enterprise appliances. This must be installed on the first Management appliance before running the First-Time Installer. NOTE: You can use the following links to help you verify the integrity of the files after a download. HP GPG or RPM Signature Verification Microsoft MD5 verification 18 Configure the ESXi management hypervisor

Upload HP Helion CloudSystem images to vcenter Prerequisites The management hypervisor network infrastructure is in place. See Configure the networks accessible to the server (page 15). You have administrator privileges to log in to vcenter. vcenter has a security certificate. See the VMware Knowledge Base for instructions on implementing certificates with vsphere. One large datastore is created with 8 TB of storage (plus any glance storage you require) to support the virtual appliance boot drives plus additional storage for OpenStack images. For additional details on image sizing, see the Hardware requirements section of the HP Helion CloudSystem 9.0 Update 1 Support Matrix in the Enterprise Information Library. The csstartgui.bat and the full csstart folder are extracted from HP_Helion-CloudSystem-Tools.zip and added to your staging environment. The OVAs are unzipped from the Foundation and Enterprise release packages on your staging environment. Procedure 3 Preparing the CloudSystem virtual machine images 1. Log in to vcenter using the VMware vsphere Client or a web browser. 2. Select Inventory Hosts and Clusters and select your management cluster. 3. Select File Deploy OVF template. 4. Follow the screen prompts. a. Point to the Management appliance image, cs-mgmt.ova, that was unzipped on your staging environment. Give the image a unique name that is not currently used in vcenter. b. Best practice is to select thin provisioning. Installation is much faster with this option. 5. Verify that the virtual machine was created. It should be listed on the left side of the screen under the VMs and templates view. Do NOT boot the virtual machine. 6. To convert the new virtual machine to a template, right-click the virtual machine and select Template Convert to Template. The csstart installation script uses this template during deployment. 7. Repeat steps 3-6 for the Cloud controller, selecting the cs-cloud.ova image that was unzipped on your staging environment. 8. Repeat steps 3-6 for the Enterprise appliance, selecting the cs-enterprise.ova image that was unzipped on your staging environment. 9. Repeat steps 3-6 for the Monitoring appliance, selecting the cs-monitoring.ova image file that was unzipped on your staging environment. 10. Repeat steps 3-6 for the Update appliance, selecting the cs-update.ova image that was unzipped on your staging environment. 11. Repeat steps 3-6 for the SDN appliance, selecting the cs-sdn.ova image that was unzipped on your staging environment. NOTE: You must create the SDN appliance template, but the SDN appliance is only deployed if you are configuring a VxLAN environment with the Tenant Underlay Network. Create the ESXi management cluster in vcenter, configure the network infrastructure and upload OVAs 19

5 Create the first Management appliance The CloudSystem Management Appliance Installer is the first of two CloudSystem installers. This installer creates the first Management appliance and configures the Data Center Management Network. A temporary VLAN ID is assigned to the Cloud Management Network, but you can assign a different VLAN ID when you fill out the network details in the second CloudSystem installer (First-Time Installer). Prerequisites You have administrator privileges to log in to VMware vcenter. Port 5000 is open. The installer will use this port. If you plan to migrate from CloudSystem 8.1 U2 to CloudSystem 9.0 U1, the VLAN ID for the Data Center Management Network is the same VLAN ID assigned to the Data Center Management Network in the 8.1 U2 environment. The dvswitch containing the vmkernel portgroup, which will be used by CloudSystem as the Management trunk, exists in vcenter. None of the hosts in the cluster where you are installing the Management appliance are in maintenance mode, shut down or on standby. All virtual appliance OVAs are deployed as templates in vcenter. Make sure that the templates are in the same datastore where CloudSystem will be deployed. Optional: You have a certificate and private key, if you are using your company s existing certificate authority (CA) or you are generating your own certificate and private key. See Manage certificates in CloudSystem in the HP Helion CloudSystem 9.0 Update 1 Administrator Guide in the Enterprise Information Library. Procedure 4 Creating the first Management appliance 1. (Optional) Disable the proxy server in your browser s LAN settings. You may need to restore your proxy settings after running the installer if your network administrator has not configured these settings to reset automatically. 2. Use the planning worksheet to gather the information you need for the installation. See CloudSystem Installation Planning Worksheet (page 48) 3. Log on to the staging environment that has network connectivity to the vcenter managing the management hypervisor. 4. Launch the csstartgui.bat file that you extracted from the HP_Helion-CloudSystem-Tools file. 5. Fill out the fields in the CloudSystem Management Appliance Installer, entering the information you gathered in the CloudSystem Installation Planning Worksheet. a. For the Management Hypervisor Information section: Enter the vcenter FQDN or IP address, user name, password and cluster name. b. For the Management Appliance Information section: When you select an ESXi hypervisor type, the image field requires the name of the Management appliance image you loaded in vcenter and converted to a template. c. To enter a certificate key and certificate, browse to the location of the key and certificate in your local environment. If you leave these fields blank, CloudSystem will automatically generate a certificate and key. See the Manage certificates in CloudSystem chapter of the HP Helion CloudSystem 9.0 Update 1 Administrator Guide in the Enterprise Information Library. 20 Create the first Management appliance

6. Accept the license agreement, then click Install. Figure 2 vcenter after running the CloudSystem Management Appliance Installer IMPORTANT: Close the CloudSystem Management Appliance Installer after completing the installation. Do not install the Management appliance a second time from the installer. After running the CloudSystem Management Appliance Installer, a deployer.conf file is created in the csstart folder you downloaded to your staging environment. This file contains sensitive information that should be protected. Make sure this file is secure. Only the administrator who installed CloudSystem should have access to the file. If the installation fails, review the deploy.log file for error messages, then try the installation again. The deploy.log file is located in the csstart folder you downloaded to your staging environment. Install the Enterprise and Monitoring appliance drivers Before installing the remaining CloudSystem virtual appliances, the Monitoring appliance and Enterprise appliance drivers must be installed. The MySQL Connector/J (JDBC driver) is available from the MySQL-ConnectorJ.zip on the Software Depot at www.hp.com/go/cloudsystem/download. Customers must download this driver, even if CloudSystem is pre-installed or a technical services agent is engaged to assist with the installation. After downloading the driver, install it on the Management appliance (ma1) in the boot directory for each Monitoring appliance and Enterprise appliance. If the driver is not installed, CloudSystem deployment will fail. Procedure 5 Installing the Monitoring appliance and Enterprise appliance driver 1. Download the MySQL Connector/J (JDBC driver) package from the Software Depot. 2. Extract libmysql-java_5.1.32-1_all.deb from the zip file and add it to your staging environment. 3. Using cloudadmin credentials, SSH in to the Management appliance (ma1). Use the default credentials, cloudadmin/cloudadmin. When you run the First-Time Installer, you will have an opportunity to change the default password. 4. Switch to the root user: sudo -i 5. Install the driver for the Monitoring appliance. a. Change the directory to /boot/cloudsystem/cs-monasca-controller/ b. Copy the MySQL JDBC driver to the directory. c. Update the MySQL JDBC driver file permissions: Install the Enterprise and Monitoring appliance drivers 21

chown cloudsystem:cloudsystem libmysql-java_5.1.32-1_all.deb chmod 644 libmysql-java_5.1.32-1_all.deb d. Change the directory to /boot/cloudsystem/cs-monasca-controller1/ e. Copy the MySQL JDBC driver to the directory. f. Update the MySQL JDBC driver file permissions: chown cloudsystem:cloudsystem libmysql-java_5.1.32-1_all.deb chmod 644 libmysql-java_5.1.32-1_all.deb g. Change the directory to /boot/cloudsystem/cs-monasca-controller2/ h. Copy the MySQL JDBC driver to the directory. i. Update the MySQL JDBC driver file permissions: chown cloudsystem:cloudsystem libmysql-java_5.1.32-1_all.deb chmod 644 libmysql-java_5.1.32-1_all.deb 6. Install the driver for the Enterprise appliance, if you plan to deploy it during First-Time Installation. a. Change the directory to /boot/cloudsystem/cs-enterprise/ b. Copy the MySQL JDBC driver to the directory. c. Update the MySQL JDBC driver file permissions: chown cloudsystem:cloudsystem libmysql-java_5.1.32-1_all.deb chmod 644 libmysql-java_5.1.32-1_all.deb d. Change the directory to /boot/cloudsystem/cs-enterprise1/ e. Copy the MySQL JDBC driver to the directory. f. Update the MySQL JDBC driver file permissions: chown cloudsystem:cloudsystem libmysql-java_5.1.32-1_all.deb chmod 644 libmysql-java_5.1.32-1_all.deb g. Change the directory to /boot/cloudsystem/cs-enterprise2/ h. Copy the MySQL JDBC driver to the directory. i. Update the MySQL JDBC driver file permissions: chown cloudsystem:cloudsystem libmysql-java_5.1.32-1_all.deb chmod 644 libmysql-java_5.1.32-1_all.deb 22 Create the first Management appliance

6 Run the First-Time Installer in an ESXi environment After you create the Management appliance using the CloudSystem Management Appliance Installer, you can run the CloudSystem First-Time Installer to launch the remaining virtual appliances and connect the network infrastructure. First-Time Installer field descriptions The First-Time Installer is launched using the URL of the Management appliance you created in the previous section. Example: http://<ma_ip_address> When the installer opens, you will notice a progress bar at the top of the screen. This bar tracks your progress through the installer fields. When you ve completed all of the fields, progress displays as 100%. Figure 3 Progress bar in the First-Time Installer IMPORTANT: Do not start the First-Time Installer until you ve installed the Monitoring appliance and Enterprise appliance drivers. See Install the Enterprise and Monitoring appliance drivers (page 21). Procedure 6 Running the First-Time Installer 1. Verify the Management hypervisor settings displayed in the first section of the installer. These settings confirm the information you entered in the CloudSystem Management Appliance Installer. 2. Scroll to the Appliance Images section and make sure that the default image names match the OVA template names you created in vcenter. If the image names do not match, change the image names listed in the table to match the template names you created in vcenter. TIP: While virtual machine names can be changed in this table, best practice is to use the default values, as this makes it easier to troubleshoot your environment. 3. In the HP Helion CloudSystem Enterprise section, set the toggle button to ON to install the Enterprise appliance trio. You can set the toggle to OFF if you want to install CloudSystem Enterprise at a later time. After CloudSystem is installed, use the Appliances screen of the Operations Console to install Enterprise. 4. In the Network Settings: Data Trunk section, select VLAN or VxLAN. VLAN configurations support Centralized Virtual Routing (CVR). If you plan to migrate from CloudSystem 8.1 U2 to CloudSystem 9.0 U1, make sure that the VLAN ID is the same as the VLAN ID assigned to the Cloud Data Trunk in the CloudSystem 8.1 U2 environment. VxLAN configurations support Centralized Virtual Routing (CVR) and Distributed Virtual Routers (DVR). Specify the underlay VLAN ID that is trunked in the Cloud Data Trunk. The CIDR range is optional. If you leave this field blank, the default value is 192.168.248.0/21. First-Time Installer field descriptions 23

NOTE: If you select VxLAN, you will not be able to migrate your CloudSystem 8.1 U2 environment to CloudSystem 9.0 U1. Migration is not supported in VxLAN configurations. 5. In the Network Settings: Management Trunk section, edit the network details for each required network. a. Select the Data Center Management Network and click Edit Network. b. Enter the Primary DNS server IP address. This field is required if you entered a FQDN for vcenter when you ran the CloudSystem Management Appliance Installer, or if you plan to register ESXi compute clusters using a FQDN. This field is optional if you entered an IP address for vcenter when you ran the CloudSystem Management Appliance Installer. c. If you are using static IP addresses, set the IP range. The recommended range for this network to support the maximum supported cloud is /23. For proof of concept installs, plan for 14 IP addresses, or use the formula below to calculate an exact number for your specific environment requirements. Formula: 2 native IPs for the Management appliances + 3 native IPs for the Cloud controllers + 3 native IPs for the Enterprise appliances + 1 native IP for the Update appliance + 1 IP for each ESXi host within the compute cluster, to support the OVSvApp appliance + 1 IP for the SDN appliance, if you are using a VxLAN configuration If you plan to migrate from CloudSystem 8.1 U2 to CloudSystem 9.0 U1, make sure that the range you identify can support resource requirements in BOTH environments. d. Add a route for each remote network. Since the Consumer Access Network is defined as the default gateway for all CloudSystem virtual appliances, you need to add a route that allows the appliances on the Data Center Management Network to access remote networks from the Data Center Management Network. For example, you will need a route to access the OpenStack user portal on the Cloud controller and HP CSA on the Enterprise appliance. NOTE: section. If you are using DHCP, you must add the DHCP gateway IP address in this Alternatively, you can add the gateway IP address after installation from the Operations Console System Networking Update Management Trunk. Destination: Add a network CIDR range for any external network you need to reach. Next hop: Add a gateway on this network that can route to the remote network. e. Click Update Network. f. Select the Consumer Access Network and click Edit Network. g. Enter a unique VLAN ID for the network. If you plan to migrate from CloudSystem 8.1 U2 to CloudSystem 9.0 U1, make sure that the VLAN ID is the same as the VLAN ID assigned to the Consumer Access Network in the CloudSystem 8.1 U2 environment. h. Enter a CIDR range. i. Enter the default gateway for all CloudSystem virtual appliances. 24 Run the First-Time Installer in an ESXi environment

NOTE: section. If you are using DHCP, you must add the DHCP gateway IP address in this Alternatively, you can add the gateway IP address after installation from the Operations Console System Networking Update Management Trunk. j. In the IP Range field, use the formula below to calculate an exact number for your specific environment requirements. Formula: + 3 native IPs for the Enterprise appliances NOTE: If you are using DHCP, make sure that you have a DHCP server in the Consumer Access Network. k. Click Update Network. l. Select the Cloud Management Network and click Edit Network. m. Enter a unique VLAN ID for the network. If you plan to migrate from CloudSystem 8.1 U2 to CloudSystem 9.0 U1, make sure that the VLAN ID is different from the VLAN ID assigned to the Cloud Management Network in the CloudSystem 8.1 U2 environment. You cannot use the same VLAN ID for this network in both environments. n. Click Update Network. o. Select External Network and click Edit Network. p. Enter a unique VLAN ID for the network. If you plan to migrate from CloudSystem 8.1 U2 to CloudSystem 9.0 U1, make sure that the VLAN ID is the same as the VLAN ID assigned to the External Network in the CloudSystem 8.1 U2 environment. q. Click Update Network. 6. In the Network Settings: Storage Trunk section, add the storage networks that support the type of storage used in your environment. a. Select the Block Storage Network and click Edit Network. b. Enter a unique VLAN ID for the network. c. If you are using static IP addresses, enter a CIDR range. You need six IP addresses to support storage. Add routes if there are storage devices on a remote network that routes to the Block Storage Network. d. Select the Object Proxy Network and click Edit Network. e. Enter a unique VLAN ID for the network. f. (Optional) Change the default CIDR range by entering a new value in the CIDR field. The default value is 192.168.210.0/26. First-Time Installer field descriptions 25

7. In the Network Settings: Appliance Settings section, edit the settings for the virtual appliances. a. Select the Management appliance and click Edit Appliance Network Settings. i. In the DCM Fully Qualified Domain Name (FQDN) field, enter the FQDN associated with the VIP address that you registered in the DNS server. This is not the FQDN you entered in the Cloud System Management Appliance Installer. ii. Click Update Appliance Network Settings. b. Select the Cloud controller and click Edit Appliance Network Settings. i. In the DCM VIP field, enter the IP address registered in the DNS server with the FQDN of the Cloud controller on the Data Center Management Network. This is not the native IP address. ii. In the CAN VIP field, enter the IP address registered in the DNS server with the FQDN of the Cloud controller on the Consumer Access Network. This is not the native IP address. iii. In the CAN Public Address field, enter the optional IP address that allows you to access the Consumer Access Network if your data center is behind a firewall. Make sure this IP address is mapped to the CAN VIP. iv. Click Update Appliance Network Settings. c. If you chose to install CloudSystem Enterprise using the First-Time Installer, select the Enterprise appliance and click Edit Appliance Network Settings. i. In the DCM VIP field, enter the IP address registered in the DNS server with the FQDN of the Enterprise appliance on the Data Center Management Network. This is not the native IP address. ii. In the CAN VIP field, enter the IP address registered in the DNS server with the FQDN of the Enterprise appliance on the Consumer Access Network. This is not the native IP address. iii. In the CAN Public Address field, enter the optional IP address that allows you to access the Consumer Access Network if your data center is behind a firewall. Make sure this IP address is mapped to the CAN VIP. iv. Click Update Appliance Network Settings. 8. In the Glance: Disk Size section, enter the storage required for the virtual machine images that will be used to deploy instances in the cloud. The recommended value is 512 GB. For image sizing guidelines, see the HP Helion CloudSystem 9.0 Update 1 Support Matrix in the Enterprise Information Library. NOTE: If you need additional storage space for virtual machine images, you can change the size of the Glance disk after installation. See the Image management chapter of the HP Helion CloudSystem 9.0 Update 1 Administrator Guide in the Enterprise Information Library. 9. In the Time Settings field, turn the time server toggle ON or OFF according to your configuration, then select a time zone. (Recommended) Choose ON if you want to use external network time servers to synchronize your virtual appliances. This must be the same external network time server configured on the KVM/ESXi hosts. Choose OFF if you want to use your Management appliance to synchronize time on your virtual appliances. For ESXi, each host in the management cluster must be synchronized with an external time server. See Configuring Network Time Protocol (NTP) on ESX/ESXi hosts using the vsphere Client. 26 Run the First-Time Installer in an ESXi environment

10. In the HTTP/HTTPS proxy section, set the toggle to ON or OFF according to your configuration. Choose ON if you want to allow CloudSystem to connect to the internet to access software downloads and additional cloud content. Choose OFF if you want to block internet access. 11. In the Administrator Account Password section, set the default passwords for your administrator accounts. NOTE: Your administrator password can only contain alphanumeric characters. The Operating System account for CloudSystem Appliances is the account that allows administrators to log on to the CloudSystem virtual appliances as cloudadmin. The Operations Console is the administrative portal that provides access to the primary resource management areas of the appliance for compute, networking, and storage resources, and for appliance administration. The username is admin. The OpenStack user portal is the Horizon-based UI that allows users to configure and deploy virtual machine instances. The username is admin. NOTE: If you plan to integrate with OpenLDAP or Active Directory, specify a complex password for admin that contains upper case, lower case and digits 0 through 9. Special characters are not supported. The HP Operations Orchestration (OO) account allows administrators to log in to Operations Orchestration to attach workflows to virtual machine lifecycle actions. The username is Administrator. 12. Click Complete. 13. Review the installation information on the verification screen. IMPORTANT: Before you begin the installation, make sure that you have the required amount of disk space to support all CloudSystem virtual appliances. The installer does not check the disk space before initiating the installation. You can review resource requirements in the HP Helion CloudSystem 9.0 Update 1 Support Matrix in the Enterprise Information Library. 14. To start the installation, click Begin Installation. Tracking installation progress An Installation Progress screen displays once you start the installation. You will see a list of installation steps, along with a status indicator for each step. When an installation step is complete, the status indicator turns green. Some installation steps include nested actions. For example, the Deploy step has many nested actions that must complete before Deploy is considered complete. While the nested actions are in progress, the Deploy status appears yellow to indicate that the step is waiting on the nested actions. A progress bar is also located along the bottom of the Installation Progress window. Progress is tracked at major installation milestones so you may notice the indicator sitting at one stage for a long period of time. The biggest jump in progress will occur after all appliances are deployed. The SDN appliance is only deployed in VxLAN environments configured with Centralized Virtual Routing (CVR). NOTE: For a more detailed view of installation progress, see the Activity Dashboard at http://<ma vip>:81/#/dashboard/file/activity. First-Time Installer field descriptions 27

7 Verify ESXi installation Confirm that you have the following network configuration for CloudSystem in vcenter. Figure 4 vcenter view of Management trunk after running the First-Time Installer Figure 5 vcenter view of Data trunk after running the First-Time Installer 28 Verify ESXi installation

Figure 6 vcenter view of Storage trunk after running the First-Time Installer 29