HP Helion CloudSystem 9.0 Installation Guide

Transcription

1 HP Helion CloudSystem 9.0 Installation Guide About this guide This information is for use by administrators using HP Helion CloudSystem Software version 9.0, who are assigned to configure and provision compute resources for deployment and use in virtual data centers. HP Part Number: Published: September 2015 Edition: 1

2 Copyright 2014, 2015 Hewlett-Packard Development Company, L.P. Microsoft and Windows are registered 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 and , 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.

3 Contents I HP Helion CloudSystem Installation Overview Before you begin Installation considerations...7 Audience and assumptions...7 Audience...7 Assumptions...7 Understanding the installation process...8 II ESXi Environment Installation Configure the ESXi management hypervisor...10 Configure the networks accessible to the server...10 Install the operating system...10 Set network interface settings on the ESXi management host...11 Create the ESXi management cluster in vcenter, configure the network infrastructure and upload OVAs...11 Configure the management cluster and add the ESXi hypervisors...11 Download and prepare installation images and tools...13 Upload HP Helion CloudSystem images to vcenter Create the first Management appliance...15 Install the Monitoring appliance and Enterprise appliance drivers Run the First-Time Installer in an ESXi environment...18 First-Time Installer field descriptions Verify ESXi installation Set up trunk uplinks Prepare Enterprise for HP CSA Installation errors CloudSystem user interfaces Install additional CloudSystem components Support and other resources...30 Information to collect before contacting HP...30 How to contact HP...30 Registering for software technical support and update service...30 HP authorized resellers...30 Documentation feedback...31 Related information...31 HP CloudSystem documents...31 HP Helion OpenStack documents...31 HP Insight Management documents...32 Third-party documents...32 HP 3PAR StoreServ documents...32 HP VSA StoreVirtual documents...33 HP ProLiant servers documents...33 III Appendix...34 Contents 3

4 A CloudSystem Installation Planning Worksheet...35 B Synchronize NTP servers...39 C Command line interfaces...40 csstart commands...40 Installation CLI tasks...41 Using the csstart CLI to install the first CloudSystem Management appliance...41 Enabling REST API for storage drivers...41 D KVM management hypervisor installation...43 Prepare KVM hypervisors...43 Configure a management cluster...47 Configure a RHEL 7.0 management cluster...48 Configure a RHEL 6.5 management cluster...49 Load Qcow2 images...51 Create all appliances on node (Optional) Increasing virtual appliance deployment timeout in RHEL 6.5 deployments...53 Install the Monitoring appliance and Enterprise appliance drivers...53 Run the CloudSystem First-Time Installer...54 First-Time Installer field descriptions...55 Prepare Enterprise for HP CSA...58 Finish cluster configuration...59 Finish RHEL 7.0 cluster configuration...59 Finish RHEL 6.5 cluster configuration...64 Installing additional CloudSystem components...73 E vcenter and CloudSystem optional configurations...74 Installing CloudSystem when vcenter and CloudSystem share the same host/cluster...74 Migrating standard vswitches to distributed vswitches...75 F Using cshaupdate to set virtual router IDs and change deployment timeout settings Contents

5 Part I HP Helion CloudSystem Installation Overview

6 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 Administrator Guide in the Enterprise Information Library. CloudSystem networking See the HP Helion CloudSystem 9.0 Network Planning Guide in the Enterprise Information Library. CloudSystem resource requirements and supported hardware, software and tools. See the HP Helion CloudSystem 9.0 Support Matrix in the Enterprise Information Library. 6 Before you begin

7 2 Installation considerations CloudSystem supports several different configuration scenarios. This installation guide explains how to install the following CloudSystem configuration: ESXi management hypervisor KVM instructions are available in the appendix. See KVM management hypervisor installation (page 43). 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 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 35). Audience and assumptions 7

8 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 Installation steps covered in the install guide 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 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 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 10). 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 15). 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 18). Step 5: Configure cloud resources using the Operations Console. This guide does not cover these specific steps. See the HP Helion CloudSystem 9.0 Administrator Guide in the Enterprise Information Library. 8 Installation considerations

9 Part II ESXi Environment Installation

10 3 Configure the ESXi management hypervisor CloudSystem requires a management cluster with at least three hosts to support CloudSystem virtual appliances. Process overview 1. Configure the networks accessible to the server (page 10) 2. Install the operating system (page 10) 3. Set network interface settings on the ESXi management host (page 11) 4. Create the ESXi management cluster in vcenter, configure the network infrastructure and upload OVAs (page 11) 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 Cloud Management Network Do not configure DHCP on this network and do not allow network service traffic to use this network. Consumer Access Network External Network Untagged networks include: PXE Network Cloud Data trunk Multiple Provider and Tenant Networks will be created from this trunk. If you are configuring a VLAN environment, a range of VLANs should be assigned for Tenant and Provider Networks. If you are configuring a VxLAN environment, an underlay VLAN should be assigned to the Cloud Data Trunk for carrying Tenant and Provider Networks. Use Tunneling for this trunk and connect to Port 2/eth1. 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 Support Matrix in the Enterprise Information Library. 10 Configure the ESXi management hypervisor

11 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. 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. Your VMware vcenter name does not contain spaces. The host/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 74). 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. Set network interface settings on the ESXi management host 11

12 Figure 2 ESX management cluster switches and ports 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 datacenter that supports CloudSystem, create the management cluster. 3. Add your host 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. 4. Verify that you have the following minimum networking pieces configured for the 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 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. 12 Configure the ESXi management hypervisor

13 Download and prepare installation images and tools The HP Helion CloudSystem 9.0 release kit is downloaded from HP Software Depot at 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 nodes. See the Compute node creation chapter of the HP Helion CloudSystem 9.0 Administrator Guide in the Enterprise Information Library. hlinux_hotrod.iso: supports object storage (OpenStack Swift) deployment. CloudSystemClient-linux tar.gz: Installs the Linux version of the commands for OpenStack Keystone, Nova, Neutron and Cinder. CloudSystemClient-windows 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 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 10). 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 Support Matrix in the Enterprise Information Library. Create the ESXi management cluster in vcenter, configure the network infrastructure and upload OVAs 13

14 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 controller, selecting the cs-sdn.ova image that was unzipped on your staging environment. NOTE: You must create the SDN controller template, but the SDN controller is only deployed if you are configuring a VxLAN environment with the Tenant Underlay Network. 14 Configure the ESXi management hypervisor

15 4 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). Figure 3 Results of running the CloudSystem Management Appliance Installer Prerequisites You have administrator privileges to log in to VMware vcenter. Port 5000 is open. The installer will use this port. 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 stand by. 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. Procedure 4 Creating the Management appliance 1. (Optional) Disable the proxy server in your browser s LAN settings. You may need to restore your proxy settings after running csstart 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 35) 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.zip file. 5. Follow the prompts in the CloudSystem Management Appliance Installer, entering the information you gathered in step two. 15

16 6. Accept the license agreement, then click Install. Figure 4 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 Monitoring appliance and Enterprise 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 in the HP Software Depot at 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 HP Software Depot. 2. Extract libmysql-java_ _all.deb from the zip file and add it to your staging environment. 3. Using cloudadmin credentials, SSH in to the Management appliance (ma1). 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: chown cloudsystem:cloudsystem libmysql-java_ _all.deb chmod 644 libmysql-java_ _all.deb 16 Create the first Management appliance

17 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_ _all.deb chmod 644 libmysql-java_ _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_ _all.deb chmod 644 libmysql-java_ _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_ _all.deb chmod 644 libmysql-java_ _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_ _all.deb chmod 644 libmysql-java_ _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_ _all.deb chmod 644 libmysql-java_ _all.deb Install the Monitoring appliance and Enterprise appliance drivers 17

18 5 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. Figure 5 Results of running the First-Time Installer 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: 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 6 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 Monitoring appliance and Enterprise appliance drivers (page 16) 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, HP recommends that you use the default values, as this makes it easier to troubleshoot your environment. 18 Run the First-Time Installer in an ESXi environment

19 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). 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 /21. NOTE: If you select VxLAN, you will not be able to migrate your CloudSystem 8.1 environment. 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. 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: 3 native IPs + 1 VIP for the Management appliances + 3 native IPs + 1 VIP for the Cloud controllers + 3 native IPs + 1 VIP for the Enterprise appliances + 1 native IP for the Update appliance + 1 IP for each ESXi compute node, to support the OVSvApp appliance + 1 IP for the SDN controller, if you are using a VxLAN configuration 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. 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. h. Enter a CIDR range. i. If needed, enter the default gateway for all CloudSystem virtual appliances. j. In the IP Range field, use the formula below to calculate an exact number for your specific environment requirements. Formula: + 1 VIP for the Cloud controllers + 3 native IPs + 1 VIP for the Enterprise appliances First-Time Installer field descriptions 19

20 NOTE: If 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. n. Click Update Network. o. Select External Network and click Edit Network. p. Enter a unique VLAN ID for the network. 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 / Run the First-Time Installer in an ESXi environment

21 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 Support Matrix in the HP Enterprise Information Library at 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 in the HP Helion CloudSystem 9.0 Administrator Guide in the HP Enterprise Information Library at In the Time Settings field, turn the time server toggle ON or OFF according to your configuration, then select a time zone. Choose ON if you want to use external network time servers to synchronize your virtual appliances. Choose OFF if you want to use your Management appliance to synchronize time on your virtual appliances. 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. First-Time Installer field descriptions 21

22 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. You log in as admin. The Openstack user portal is the Horizon-based UI that allows users to configure and deploy virtual machine instances. You log in as admin. The HP Operations Orchestration (OO) account allows administrators to log in to Operations Orchestration to attach workflows to virtual machine lifecycle actions. You log in as 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 Support Matrix. 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 controller is only deployed in VxLAN environments configured with Centralized Virtual Routing (CVR). 22 Run the First-Time Installer in an ESXi environment

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

24 Figure 9 vcenter view of Storage trunk after running the First-Time Installer 24 Verify ESXi installation

25 7 Set up trunk uplinks When the CloudSystem virtual appliances are deployed, the vswitches, hpcs-data and hpcs-storage, are created in vcenter. After the first deployment of appliances to your ESXi management host, you must perform this one-time manual configuration to attach uplinks to the management host. Procedure 7 Configuring trunk uplinks 1. Log in to vcenter. 2. Select Inventory Networking. 3. Select the hpcs-data switch. a. Right-click and select Manage Host. b. Select the host, then check the NIC to associate with that switch. Ex: vmnic1 c. Click Next until you reach the final screen, then click Finish. 4. Select the hpcs-storage switch. a. Right-click and select Manage Host. b. Select the host, then check the NIC to associate with that switch. Ex: vmnic2 c. Click Next until you reach the final screen, then click Finish. All port groups inside the storage and data trunks must have the same load balancing policy. 25

26 8 Prepare Enterprise for HP CSA After completing the CloudSystem installation, there are a few additional steps required to prepare the Enterprise appliances for integration with HP CSA. You must verify that the content capsule installation completed on all three Enterprise appliances before you perform the procedure in this section. Content capsule installation can take up to 30 minutes after the deployment of all CloudSystem appliances. To verify that the content capsules were fully installed, look for the following message in the /var/log/upstart/os-collect-config.log file on each Enterprise appliance. Figure 10 Capsule installation completion message Once you see the message on all Enterprise appliances, you can prepare Enterprise for HP CSA. Procedure 8 Preparing Enterprise for HP CSA 1. Using cloudadmin credentials, SSH to ma1. 2. From ma1, SSH to ea1. 3. Switch to the root user: sudo i 4. Open the following file: /usr/local/hp/csa/jboss-as/standalone/deployments/csa.war/ WEB-INF/classes/csa.properties 5. Replace the line OOS_URL= with OOS_URL= and save the file. 6. Restart the HP CSA service: service csa restart 7. Repeat steps one through six on ea2. 8. Repeat steps one through six on ea3. 9. Verify that the services have been restarted using the URL 26 Prepare Enterprise for HP CSA

27 9 Installation errors If you experience an error in your installation, you cannot go back to the First-Time Installer, change field values and re-run the installation. You must clean up your vcenter, then run both CloudSystem installers again. Procedure 9 Cleaning up after a failed installation TIP: To find the details of your installation failure, SSH in to the Management appliance and review the /var/log/cs-avm-manager/cs-avm-manager.log file and the /var/log/pavmms/pavmm_api.log file. 1. Log in to vcenter. 2. Remove the distributed vswitch (hpcs-data and hpcs-storage). 3. Remove the networks created by the First-Time Installer: Data Center Management Network Cloud Management Network Consumer Access Network External Network PXE Network IMPORTANT: Do NOT remove the dvportgroup. 4. Remove all virtual appliances in the management cluster. a. Right-click the appliance and select Power Off. b. Right-click the appliance and select Delete from Disk. 5. Run the CloudSystem Management Appliance Installer again. 6. Run the First-Time Installer again. 27

28 10 CloudSystem user interfaces Table 2 CloudSystem user interfaces UI How to access Virtual appliance hosting UI Used in CloudSystem to... Credentials CloudSystem Operations Console Management appliance Manage the cloud environment. Set during first-time installation. OpenStack user portal Cloud controller Create, launch, and manage virtual machine instances. Set during first-time installation. This is a specialized version of OpenStack Horizon on the Management appliance used to access the Monitoring Dashboard. Log in to the Operations Console. Select General Monitoring from the main menu, then log in to Horizon with the Operations Console credentials you set during first-time installation. Management appliance Manage monitoring services. Set during first-time installation. Cloud Service Management Console (HP CSA) Enterprise appliance Create and manage service offerings and service catalogs. admin/cloud Marketplace Portal Enterprise appliance Select cloud services from a catalog and monitor and manage existing services, with subscription pricing. consumer/cloud HP Operations Orchestration Enterprise appliance Attach workflows to server lifecycle actions or schedule flows for regular execution. Set during first-time installation. 28 CloudSystem user interfaces

29 11 Install additional CloudSystem components After you ve successfully installed CloudSystem, you can use the HP Helion CloudSystem 9.0 Administrator Guide to install and configure the following resources in your cloud. Create compute nodes See the Compute node creation chapter of the HP Helion CloudSystem 9.0 Administrator Guide in the Enterprise Information Library. Install and configure OpenStack Swift object storage See the Object storage chapter of the HP Helion CloudSystem 9.0 Administrator Guide in the Enterprise Information Library. Install Platform services, including Helion Development Platform and DNS as a Service See the Platform services, including Helion Development Platform and DNS as a Service chapter of the HP Helion CloudSystem 9.0 Administrator Guide in the Enterprise Information Library. 29

30 12 Support and other resources Information to collect before contacting HP Be sure to have the following information available before you contact HP: Software product name Hardware product model number Operating system type and version Applicable error message Third-party hardware or software Technical support registration number (if applicable) How to contact HP Use the following methods to contact HP: To obtain HP contact information for any country, see the Contact HP worldwide website: Use the Get help from HP link on the HP Support Center: To contact HP by telephone in the United States, use the Contact HP Phone Assist website to determine the telephone number that precisely fits your needs. For continuous quality improvement, conversations might be recorded or monitored. Registering for software technical support and update service HP CloudSystem includes one year of 24 x 7 HP Software Technical Support and Update Service. This service provides access to HP technical resources for assistance in resolving software implementation or operations problems. The service also provides access to software updates and reference manuals, either in electronic form or on physical media as they are made available from HP. Customers who purchase an electronic license are eligible for electronic updates only. With this service, HP CloudSystem customers benefit from expedited problem resolution as well as proactive notification and delivery of software updates. For more information about this service, see the following website: Registration for this service takes place following online redemption of the license certificate. HP authorized resellers For the name of the nearest HP authorized reseller, see the following sources: In the United States, see the U.S. HP partner and store locator website: In other locations, see the Contact HP worldwide website: 30 Support and other resources

31 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send your suggestions and comments to: In your mail message, include the following information. They are located on the front cover. Document title Published date Edition number Help us pinpoint your concern by posting the document title in the Subject line of your mail message. Related information Use this section to learn about available documentation for HP CloudSystem components and related products HP CloudSystem documents The latest versions of HP CloudSystem manuals and white papers, including HP CSA and HP Operations Orchestration, can be downloaded from the Enterprise Information Library at HP Helion CloudSystem 9.0 Release Notes HP Helion CloudSystem 9.0 Installation Guide HP Helion CloudSystem 9.0 Administrator Guide HP Helion CloudSystem 9.0 Network Planning Guide HP Helion CloudSystem 9.0 Troubleshooting Guide HP Helion CloudSystem 9.0 Command Line Interface Guide HP Helion CloudSystem 9.0 Support Matrix Online help for the CloudSystem Operations Console is available by clicking the help control button in the Console user interface: HP Helion OpenStack documents The latest version of HP Helion OpenStack information is viewable from HP Helion Documentation at including information about the following products: HP Helion OpenStack HP Helion OpenStack Community HP Helion Development Platform HP Helion Eucalyptus HP Helion Public Cloud The full list of HP CSA documentation can be accessed from the HP Cloud Service Automation tab. Documentation feedback 31

32 HP Insight Management documents The latest versions of HP Matrix Operating Environment manuals, white papers, and the HP Insight Management Support Matrix can be downloaded from the HP Enterprise Information Library at including the following documents: HP Matrix Operating Environment Release Notes HP Insight Management Support Matrix HP Matrix Operating Environment Infrastructure Orchestration User Guide Cloud bursting with HP CloudSystem Matrix infrastructure orchestration Third-party documents CloudSystem incorporates OpenStack technology (listed below), and interoperates with other third-party virtualization software. OpenStack Juno OpenStack Documentation for Juno releases With few exceptions (such as installation information), OpenStack documents are always set to display the current release stream on the OpenStack document web site. Check the OpenStack appendices in the HP CloudSystem Administrator Guide to learn about unsupported OpenStack functionality in this release. VMware Cloud Administrator Guide Virtual Machine Image Guide API Quick Start Admin User Guide End User Guide Command reference Keystone commands Glance commands Neutron commands Nova commands Cinder commands VMware vsphere documents Microsoft Microsoft Windows Server documents Microsoft Hyper-V documents Red Hat Red Hat Enterprise Linux 6 documents Red Hat Enterprise Linux 7 documents HP 3PAR StoreServ documents The latest versions of HP 3PAR StoreServ Storage manuals are available from the Storage tab at the top of the Enterprise Information Library. 32 Support and other resources

33 HP 3PAR StoreServ Storage manuals can also be downloaded from the HP Support Center, including the following documents: HP 3PAR StoreServ Storage Concepts Guide HP 3PAR StoreServ Storage Troubleshooting Guide HP VSA StoreVirtual documents The latest versions of HP VSA StoreVirtual Storage manuals are available from the Storage tab at the top of the Enterprise Information Library. HP VSA StoreVirtual Storage manuals can also be downloaded from the HP Support Center, including the following document: HP StoreVirtual Storage User Guide HP ProLiant servers documents The HP Integrated Lights-Out QuickSpecs contain support information and are available from the ilo product website: HP ProLiant servers: ProLiant BL BladeSystem servers: ProLiant DL, ML, and SL servers: Related information 33

34 Part III Appendix

35 A CloudSystem Installation Planning Worksheet Use the worksheet below to gather your CloudSystem environment details before you begin the installation process. Enter your environment details into the fields provided and then use that information as you step through the CloudSystem installers. Table 3 CloudSystem Installation Planning Worksheet Installation Preparation Images Source release package unpacked and added to your staging environment Names Disk Format Thin Provision (recommended) Installation script (csstartgui.bat) Source release package unpacked and added to your staging environment Target CloudSystem Management Appliance Installer Management hypervisor type vcenter IP address vcenter user name vcenter password Cluster Management appliance image name Hostname Example: my.ma.hpiscmgmt.local Host IP type IP Address *If using static IP address assignment. Gateway *If using static IP address assignment. Netmask *If using static IP address assignment. CS key (optional) CS certificate (optional) First Time Installer NOTE: If you are not sure what information to provide in a field below, refer to Run the First-Time Installer in an ESXi environment (page 18). Management hypervisor Verify the information 35

36 Appliance images Make sure image names match what you created in vcenter. Use the default VM names for easier troubleshooting. Enterprise appliance Migrate Cloud Data Trunk Yes or No Yes or No VLAN or VxLAN Network Settings: Management Trunk Data Center Management Network VLAN ID Domain name Use DHCP Primary DNS Secondary DNS (optional) Appliance IP ranges (optional) Routes (optional) Network Settings: Management Trunk Consumer Access Network VLAN ID Use DHCP CIDR Domain name Network Settings: Management Trunk Cloud Management Network VLAN ID Use DHCP CIDR Domain name Network Settings: Management Trunk External Network VLAN ID Network Settings: Storage Trunk Block Storage Network VLAN ID Use DHCP IP Address *If using static IP address assignment. CIDR *If using static IP address assignment. 36 CloudSystem Installation Planning Worksheet

37 Table 3 CloudSystem Installation Planning Worksheet (continued) Routes (optional) VLAN ID Use DHCP CIDR *If using static IP address assignment. Network Settings: Storage Trunk Object Proxy Network Data Center Management FQDN for the Management appliance Data Center Management Virtual IP address for the Management appliance Data Center Management FQDN for the Cloud controller Data Center Management Virtual IP address for the Cloud controller Consumer Access Network FQDN for the Cloud controller (optional) Consumer Access Network Virtual IP address for the Cloud controller Consumer Access Network Public Address (optional) Data Center Management FQDN for the Enterprise appliance Data Center Management Virtual IP address for the Enterprise appliance Consumer Access Network FQDN for the Enterprise appliance (optional) Consumer Access Network Virtual IP address for the Enterprise appliance Consumer Access Network Public Address (optional) Disk Size (GB) Network Settings: Public Access Point Address Management appliance Network Settings: Public Access Point Address Cloud controller Network Settings: Public Access Point Address Enterprise appliance Glance Disk Size Time Settings If using an external time zone, you must inform at least one time server. * Use Time Zone Yes or No Time Zone 37

38 Table 3 CloudSystem Installation Planning Worksheet (continued) Time Server 1 (optional) Time Server 2 (optional) Time Server 3 (optional) HTTP/HTTPS Proxy HTTP/HTTPS Proxy Address HTTP/HTTPS Proxy Address HTTP/HTTPS Proxy All HTTP/HTTPS Proxy fields are optional. * Administrator Account Passwords OS account for CloudSystem appliances (cloudadmin) Operations Console and Portal (admin) Operations Orchestration (Administrator) Password: Password: Password: 38 CloudSystem Installation Planning Worksheet

39 B Synchronize NTP servers For KVM environments, use this procedure if you want to use an external time server to synchronize time on the virtual appliances in your cloud environment. You must synchronize the management hypervisor and the external time server before deploying CloudSystem. Prerequisties An external time server is installed. Procedure 10 Synchronizing the management hypervisor and the external time server 1. Log on to the management hypervisor. 2. Add the NTP server IP address in the /etc/ntp.conf file. a. Open the configuration file: vi /etc/ntp.conf b. Add the server IP address in the server field. 3. Set the date and time using the NTP server you just created: ntpdate <ntp_server_ip> 4. Restart the service: service ntpd restart 5. To verify the edits to the configuration file, run the following command: ntpq p 39

40 C Command line interfaces Three command line interfaces (CLIs) are packaged in the HP Helion CloudSystem Tools release download. csstart.exe (Windows), csstart (Linux): provides command line access to run CloudSystem installation commands. This executable is packaged in the HP-Helion-CloudSystem-Tools zip, inside either the Windows csstart.zip or the Linux-csstart.tar.gz file. windows-cloudsystemclient zip: provides the ability to run CloudSystem and OpenStack command lines from a Windows command prompt. This executable is packaged in the HP-Helion-CloudSystem-Tools zip. linux-cloudsystemclient tar.gz: provides the ability to run CloudSystem and OpenStack command lines from a Linux system. This executable is packaged in the HP-Helion-CloudSystem-Tools zip. For more information on preparing CLIs and the use of CLI commands, see the HP Helion CloudSystem 9.0 Command Line Interface Guide in the Enterprise Information Library. csstart commands Table 4 csstart commands Task CLI command Example What it does View the EULA before accepting it save-eula csstart save-eula This command saves a copy of the EULA to your local directory. Search for eula.html. You can open the file and read the EULA before accepting it. Create a sample configuration file create-config [--config] csstart create-config This command creates the configuration file. The default name is deployer.conf. The [--config] flag allows you to create a unique name for the file, if you don t want to use the default name. Create the first Management appliance start [--config] --eula-accepted csstart start --eula-accepted This command must be run from the CLI. It creates the first Management appliance (ma1) and configures the Data Center Management Network. It also assigns a temporary VLAN ID to the Cloud Management Network. The [--config] flag allows you to specify a configuration file, if you didn t use the default deployer.conf name. The EULA is automatically accepted. Start a web server listening on a specific port gui [--listen ipaddr --port portvalue] csstart gui [--listen port 5000] The ipaddr:port defaults to :5000 which means the webs server only listens to a web browser running on the local host. A very common value for the listen flag is --listen port The web server listens for connections 40 Command line interfaces

41 Table 4 csstart commands (continued) Task CLI command Example What it does from any host, such as your workstation. Installation CLI tasks Using the csstart CLI to install the first CloudSystem Management appliance (page 41) Enabling REST API for storage drivers (page 41) Using the csstart CLI to install the first CloudSystem Management appliance Procedure 11 Using the csstart CLI to install the first CloudSystem Management appliance 1. Log in to the management hypervisor. 2. Create the deployer.conf configuration file:./csstart create-config This will create a sample configuration file. The default name is deployer.conf, but you can specify a unique name by putting it inside the [--config] tag. 3. Open the config file: vi deployer.conf 4. Fill in the Hypervisor section of the configuration file. The hints provided in the configuration file explain the hypervisor entries. 5. Fill in the Management section of the configuration file. For image, if you are installing on a KVM management hypervisor, append the directory path /CloudSystem to the image name. Ex: /CloudSystem/cs-mgmt 6. Fill in the SSL section of the configuration file using your certificate information and key. This is an optional section. 7. Save and close the configuration file: :wq 8. Run the script to create the first Management appliance (ma1):./csstart start --eula-accepted NOTE: You can modify the above command if you want to generate a log file, which is helpful in the event of an error. Use./csstart start v --log-file <name of log file>. 9. Verify that the CloudSystem Management appliance was created on the management hypervisor. IMPORTANT: Do not move or delete images after you create the CloudSystem Management appliance. In order to speed up virtual machine boot times and save disk space, csstart does not make a full copy of the image. A copy is shared across all of the virtual machines. Enabling REST API for storage drivers This is a condensed version of the OpenStack instructions. You can see the complete instructions here: Enabling the HP 3PAR Fibre Channel and iscsi Drivers Prerequisites HP3PARFCDriver is installed with OpenStack software HP3PARISCSIDriver is installed with OpenStack software Installation CLI tasks 41

42 Procedure 12 Enabling REST API for storage drivers Verify that the HP 3PAR WebServices API server is enabled and running on the HP 3PAR StoreServ storage system. a. Using administrator credentials, log on to the HP 3PAR StoreServ storage system: #ssh EPAR IP Address> b. Check the current state of the WebServices API server: #showwsapi c. If the WebService API server is disabled, then start it: #startwsapi d. If the HTTP or HTTPS state is disabled, enable one of them: #setwsapi http enable #setwsapi https enable NOTE: If you need a list of WebService API commands, run the command setwsapi h. A list of Web Service commands will display. 42 Command line interfaces

43 D KVM management hypervisor installation This appendix covers the installation of KVM management hypervisors. If you want to install KVM compute nodes, see the Compute node creation chapter of the HP Helion CloudSystem 9.0 Administrator Guide in the Enterprise Information Library. CloudSystem requires a management cluster with at least three hosts to support CloudSystem virtual appliances. You have several deployment decisions to make if you plan to use KVM management hypervisors. If using Centralized Virtual Routing, you can choose: VLAN support for Provider and Tenant Networks via a range of VLAN IDs in the Cloud Data Trunk. This option supports ESXi, KVM, or Hyper-V compute nodes. VxLAN support for Provider and Tenant Networks via a Tenant Underlay Network. This option supports ESXi or KVM compute nodes. NOTE: If you select VxLAN, you will not be able to migrate your CloudSystem 8.1 environment. Migration is not supported in VxLAN environments. KVM, ESXi or Hyper-V compute nodes If using Distributed Virtual Routing, you can choose: VxLAN only KVM compute nodes only IMPORTANT: Follow the best practices recommended by Red Hat when configuring clusters. Process overview 1. Prepare KVM hypervisors (page 43) 2. Configure a management cluster (page 47) 3. Load Qcow2 images (page 51) 4. Create all appliances on node 1 (page 52) 5. Run the CloudSystem First-Time Installer (page 54) 6. Prepare Enterprise for HP CSA (page 58) 7. Finish cluster configuration (page 59) Prepare KVM hypervisors Configure the server profile On the management hypervisor, configure the server profile to include three trunks: Management, Cloud Data and Storage. The following networks are included in each trunk as part of the CloudSystem installation process. Additional networks can be added later. Management trunk All networks in this trunk are tagged and connect to Port 1/eth0. Data Center Management Network Cloud Management Network Consumer Access Network Prepare KVM hypervisors 43

44 External Network PXE Network (untagged) Cloud Data trunk Multiple Provider and Tenant Networks will be created from this trunk. If you are configuring a VLAN environment, a range of VLANs should be assigned for Tenant and Provider Networks. If you are configuring a VxLAN environment, an underlay VLAN should be assigned to the Cloud Data Trunk for carrying Tenant and Provider Networks. Use Tunneling for this trunk and connect to Port 2/eth1. Storage trunk All networks in this trunk are tagged and connect to Port 3/eth2. Block Storage Network Object Proxy Network Install the operating system on the management hypervisor CloudSystem supports both RHEL 7.0 and RHEL 6.5 operating systems. For best performance results, RHEL 7.0 is recommended. RHEL 7.0 OS Prerequisites When installing the OS, select Virtualization Host for the base environment and select Virtualization Platform in the Add-Ons for Selected Environments section. After installing the OS, install the libguestfs-tools by running: yum install libguestfs-tools Make sure that you have the following required packages. The minimum supported version is listed below: glusterfs-libs el7.x86_64 glusterfs-api el7.x86_64 glusterfs el7.x86_64 boost-system el7.x86_64 boost-thread el7.x86_64 1:librados el7.x86_64 1:librbd el7.x86_64 10:qemu-kvm-common el7.x86_64 10:qemu-img el7.x86_64 10:qemu-kvm el7.x86_64 44 KVM management hypervisor installation

45 RHEL 6.5 OS Prerequisties When installing the OS, select Virtualization Host for the type of installation and select the following characteristics in the Additional Repository section: High Availability Resilient Storage ScalableFileSystem After installing the OS, install the libguestfs-tools by running: yum install libguestfs-tools Configure the operating system Procedure 13 Configuring network interfaces 1. Using the ilo IP address for the KVM hypervisor, log in to the ilo console. 2. Enable temporary access to the Data Center Management Network. RHEL 7.0 Example ip link add link enp2s0f0 name enp2s0f0.<dcm VLAN ID> type vlan id <DCM VLAN ID> ip a add <host ip address>/21 dev enp2s0f0.<dcm VLAN ID> ip route add default via <gateway_ip> ping <gateway_ip> RHEL 6.5 Example vconfig add eth0.<vlan_id_data_center_management_network> ifconfig eth0 <VLAN_ID> xx/21 route add net default gw <gateway_ip> ping <gateway_ip> Procedure 14 Set up the DNS connection 1. Add the DNS server addresses to the /etc/resolv.conf file: nameserver <primary DNS address> nameserver <secondary DNS address> 2. Export proxy information by adding the following lines to the /etc/profile.d/proxy.sh file: export http_proxy= export https_proxy= 3. If needed, source the file, or log back in to see the changes in your environment. Procedure 15 Install Openvswitch on the management hypervisor 1. Using root credentials, SSH in to the KVM hypervisor and install OpenvSwitch. For RHEL 7.0, run: curl -O /openvswitch el7.x86_64.rpm rpm -i <openvswitch.rpm> service openvswitch restart ovs-vsctl show chkconfig --level 345 openvswitch on For RHEL 6.5 run: curl -O openstack/openstack-icehouse/epel-6/openvswitch _8ce28d-1.el6ost.x86_64.rpm rpm -i <openvswitch.rpm> service openvswitch restart ovs-vsctl show chkconfig --level 345 openvswitch on Prepare KVM hypervisors 45

46 2. To create a management bridge, run the following commands: ovs-vsctl add-br hpcs-mgmt ovs-vsctl add-port hpcs-mgmt dcm tag=<vlan ID> -- set interface dcm type=internal 3. Update the configuration file for the eth0 interface (ifcfg-eth0). Example configuration file DEVICE=eth0 ONBOOT=yes DEVICETYPE=ovs TYPE=OVSPort OVS_BRIDGE=hpcs-mgmt BOOTPROTO=none HOTPLUG=no 4. Create the configuration file for the Data Center Management Network (ifcfg-dcm). Example configuration file DEVICE=dcm ONBOOT=yes DEVICETYPE=ovs TYPE=OVSIntPort OVS_BRIDGE=hpcs-mgmt OVS_OPTIONS=tag=<VLAN_ID> OVS_EXTRA= set interface $DEVICE type=internal BOOTPROTO=static IPADDR=<YOUR_IP_ADDRESS> NETMASK=<YOUR_NETMASK> GATEWAY=<YOUR_GATEWAY> HOTPLUG=no 5. Create the management bridge configuration file. Example configuration file DEVICE=hpcs-mgmt ONBOOT=yes DEVICETYPE=ovs TYPE=OVSBridge BOOTPROTO=none HOTPLUG=no 6. To connect eth0 to the bridge, run: ovs-vsctl add-port hpcs-mgmt eth0 7. If needed, modify the NIC RX frag size to a. Verify that you are using the NIC driver be2net and check the current rx_frag_size value: ethtool -i eth0 driver: be2net cat /sys/module/be2net/parameters/ rx_frag_size 2048 b. To change the rx_frag_size, add the following line to the /etc/modprobe.d/be2net.conf file on the compute node: options be2net rx_frag_size=8192 NOTE: Create this file if it does not exist. 8. Reboot your system. 9. To verify the network changes, run: ovs-vsctl show 46 KVM management hypervisor installation

47 Prepare the local YUM repository on the management hypervisor Procedure 16 Preparing the YUM repository and loading tools 1. Create a yum repository by adding the following comments to /etc/yum.repos.d/rhel-dvd.repo: Set the name and identify the baseurl, or you can use an external repository that is accessible to the compute node. Example: [RHELDVD] name=<locally Mounted RHEL DVD baseurl=file:///rhel-dvd enabled=1 2. To create a local repository using the DVD image that loads the RHEL ISO in the ilo, run: mount /dev/cdrom /mnt/ mkdir /RHEL-DVD/ cp -r /mnt/* /RHEL-DVD/ rpm --import /etc/pki/rpm-gpg/rpm-gpg-key-redhat-release 3. To turn off the Red Hat Subscription Manager, modify /etc/yum/pluginconf.d/subscription-manager.conf: [main] enabled=0 4. To verify the repository, run: yum clean all yum update 5. Speed up the connection speed by updating the SSH service: For RHEL 7.0, run: vi /etc/ssh/sshd_config GSSAPIAuthentication no service sshd restart For RHEL 6.5, run: vi /etc/ssh/sshd_config UseDNS no service sshd restart 6. Install the following additional tools: yum install libguestfs-tools Optional: yum groupinstall "X Window System" Desktop yum install <supported_browser> Configure a management cluster Configure a RHEL 7.0 management cluster (page 48) Configure a RHEL 6.5 management cluster (page 49) Configure a management cluster 47

48 Configure a RHEL 7.0 management cluster Procedure 17 Preparing the three nodes in the cluster 1. On all three nodes, add the cluster repository to /etc/yum.repos.d/rhel-dvd.repo. [RHELDVDHA] name=locally Mounted RHEL DVD HA baseurl=file:///rhel-dvd/addons/highavailability enabled=1 [RHELDVDRS] name=locally Mounted RHEL DVD RS baseurl=file:///rhel-dvd/addons/resilientstorage enabled=1 2. Verify the repository. yum clean all yum update 3. Install cluster packages. yum install pcs fence-agents-all lvm2-cluster gfs2-utils -y 4. Open firewall rules on all three nodes in the cluster: firewall-cmd --permanent --add-service=high-availability firewall-cmd --add-service=high-availability firewall-cmd --zone=public --add-port= /tcp --permanent firewall-cmd --reload 5. Configure selinux on all three nodes in the cluster: change selinux to permissive setenforce 0 vi /etc/selinux/config SELINUX=permissive 6. Start cluster services on all three nodes: systemctl start pcsd.service systemctl enable pcsd.service systemctl enable corosync.service systemctl enable pacemaker.service 7. Create a password for the hacluster user on all three nodes: passwd hacluster 8. Using pcs, create cluster on one node: pcs cluster auth node1 node2 node3 -u hacluster -p password pcs cluster setup --name CLUSTERNAME node1 node2 node3 9. Using pcs, start the cluster on node 1: pcs cluster start --all 10. Create stonith and fence devices: pcs stonith create hpilo1 fence_ilo4 ipaddr="10.xx.xxx.xxx" login="admin" passwd="pwd" action="reboot" pcmk_host_list="node1" pcs stonith create hpilo2 fence_ilo4 ipaddr="10.xx.xxx.xxx" login="admin" passwd="pwd" action="reboot" pcmk_host_list="node2" pcs stonith create hpilo3 fence_ilo4 ipaddr="10.xx.xxx.xxx" login="admin" passwd="pwd" action="reboot" pcmk_host_list="node3" 11. Verify the status of the cluster: pcs status 48 KVM management hypervisor installation

49 12. Configure shared GFS storage in the cluster. For more details, consult RHEL documentation. The steps below assume you have a VSA configuration and iscsi volume presented to all nodes in the cluster as /dev/sdb. a. On node 1, run: pcs property set no-quorum-policy=freeze pcs resource create dlm ocf:pacemaker:controld op monitor interval=30s on-fail=fence clone interleave=true ordered=true b. Enable the lvm cluster on all nodes: /sbin/lvmconf --enable-cluster c. On node 1, run: pcs resource create clvmd ocf:heartbeat:clvm op monitor interval=30s on-fail=fence clone interleave=true ordered=true pcs constraint order start dlm-clone then clvmd-clone pcs constraint colocation add clvmd-clone with dlm-clone d. On node 1, create the volume: pvcreate /dev/sdb vgcreate vg_cloudsystem /dev/sdb lvcreate -L 7.99T -n lv_cloudsystem vg_cloudsystem e. Mount the file system using the clustername cscluster and fsname cloud: mkfs.gfs2 -p lock_dlm -t cscluster:cloud -j 3 /dev/vg_cloudsystem/lv_cloudsystem pcs resource create clusterfs Filesystem device="/dev/mapper/ vg_cloudsystem-lv_cloudsystem" directory="/cloudsystem" fstype="gfs2" "options=noatime" op monitor interval=10s on-fail=fence clone interleave=true pcs constraint order start clvmd-clone then clusterfs-clone pcs constraint colocation add clusterfs-clone with clvmd-clone Configure a RHEL 6.5 management cluster Procedure 18 Preparing the three nodes in the cluster 1. Open firewall rules on all three nodes in the cluster: iptables -i INPUT -m state --state NEW -p udp -m multiport --dports 5404,5405 -j ACCEPT iptables -i INPUT -m addrtype --dst-type MULTICAST -j ACCEPT iptables -i INPUT -p tcp -m state --state NEW -m tcp --dport j ACCEPT iptables -i INPUT -p tcp -m state --state NEW -m tcp --dport j ACCEPT iptables -i INPUT -p tcp -m state --state NEW -m tcp --dport j ACCEPT iptables -i INPUT -m state --state NEW -p tcp -m multiport --dport 41966,41967,41968, j ACCEPT iptables -I INPUT -p tcp -m state --state NEW -m tcp --dport j ACCEPT service iptables save 2. Configure selinux on all three nodes in the cluster: change selinux to permissive setenforce 0 Configure a management cluster 49

50 vi /etc/selinux/config SELINUX=permissive 3. Using root permissions, create Corosync keys on the first node in the cluster: corosync-keygen 4. Copy the keys to the other two nodes in the cluster: scp /etc/corosync/authkey node2:/etc/corosync/authkey scp /etc/corosync/authkey node3:/etc/corosync/authkey 5. Disable the Network Manager. Cluster services cannot be started until the Network Manager is disabled. service NetworkManager stop chkconfig NetworkManager off 6. Set the password for the ricci user on all three nodes: passwd ricci NOTE: When you add each node in your cluster, you will be prompted for a password. Use this ricci user password. 7. Start the cluster GUI (luci) on one node: service luci start chkconfig luci on iptables -i INPUT -p tcp -m state --state NEW -m tcp --dport j ACCEPT service iptables save access gui via: Use the OS user. Procedure 19 Creating the three-node cluster using the luci web interface 1. Start the luci web interface that you installed on one node in the cluster. Using the OS user, you can access the luci GUI via 2. From Manage Clusters, click Create and add the node information. a. Enter a cluster name. b. Enter a node name, password, Ricci hostname and Ricci port for each node in the cluster. c. Click Use Locally Installed Packages. d. Click Enable Shared Storage Support. e. Click Create Cluster. 3. Create fence devices. See Configuring Fence Devices in the Redhat Customer Portal. 4. Create a failover domain. See Configuring a Failover Domain in the Redhat Customer Portal. 5. Configure GFS storage and share it between the three nodes. VSA or 3PAR iscsi storage must be presented to all nodes in the cluster as /dev/sdb. a. On the first node in the cluster, run the create command: pvcreate /dev/sdb vgcreate vg_cloudsystem /dev/sdb lvcreate -L 7.99T -n lv_cloudsystem vg_cloudsystem b. Mount the file system using clustername cscluster and fsname cloud: mkfs.gfs2 -p lock_dlm -t cscluster:cloud -j 3 /dev/vg_cloudsystem/ lv_cloudsystem mount -o acl -t gfs2 /dev/vg_cloudsystem/ lv_cloudsystem /CloudSystem c. Create a /CloudSystem directory on each node of the cluster. d. Add all nodes to /etc/fstab: 50 KVM management hypervisor installation

51 /dev/mapper/vg_cloudsystem-lv_cloudsystem /CloudSystem gfs2 noatime 0 0 e. Start the clvmd and gfs2 services on each node: service clvdm start chkconfig clvmd on service fgs2 on chkconfig gfs2 on f. Configure the remaining nodes to automatically mount the shared data disk: mount a g. Update the timeout specified in /etc/sysconfig/csman: CMAN_QUORUM_TIMEOUT=0 h. Enable the lvm cluster on all three nodes: lvmconf --enable-cluster service gfs2 start chkconfig gfs2 start 6. Start cluster services on all three nodes: service ricci start chkconfig ricci on service cman start chkconfig cman on service rgmanager start chkconfig rgmanager on Load Qcow2 images The HP Helion CloudSystem 9.0 release kit is downloaded from HP Software Depot at go/cloudsystem/download. You will need the following release files to perform the procedures in this chapter. HP Helion CloudSystem Enterprise KVM 9.0-Sept 2015: Contains the QCOW2 image for the Enterprise virtual appliance. HP Helion CloudSystem Foundation KVM 9.0-Sept 2015: Contains the QCOW2 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. hlinux_hotrod.iso: supports object storage (OpenStack Swift) deployment. CloudSystemClient-linux tar.gz: Installs the Linux version of the commands for OpenStack Keystone, Nova, Neutron and Cinder. CloudSystemClient-windows 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. Load Qcow2 images 51

52 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 The following image files must be downloaded from the HP Software Depot and put into the /CloudSystem directory on the management hypervisor. HP Helion CloudSystem Enterprise qcow cs-enterprise.qcow2 HP Helion CloudSystem Foundation qcow cs-mgmt.qcow2 cs-cloud.qcow2 cs-monitoring.qcow2 cs-update.qcow2 cs-sdn.qcow2 NOTE: The SDN controller image must be included in the /CloudSystem directory, but the SDN controller is only deployed if your environment supports VxLAN and the Tenant Underlay Network. The following file must be downloaded from the HP Software Depot and unpacked and copied to your staging environment. HP Helion CloudSystem Tools windows-csstart.zip OR linux-csstart.tar.gz Create all appliances on node 1 Prerequisites All virtual appliance QCOW2 images are copied to the /CloudSystem directory on the management hypervisor. The csstart folder is unpacked from the CloudSystem Tools zip file and added to your staging environment. Procedure 20 Using CloudSystem Management Appliance Installer to create 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 csstart 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 35). 3. From your staging environment, launch the csstartgui.bat file that you extracted from the HP Helion CloudSystem Tools zip file. 4. Select KVM for the hypervisor type. 5. In the KVM Management Server field, enter the FQDN of the first node in your cluster. In a later procedure you will distribute virtual appliances across all nodes in the cluster. 6. In the User Name field, enter the name of the user with root privileges to log in to the KVM host. 7. In the Password field, enter the password for the root user. 52 KVM management hypervisor installation

53 8. In the Image field, verify that the path points to your management appliance image. 9. In the Hostname field, enter the FQDN of the Management appliance (ma1). 10. In the Host IP Type field, select the method for IP address assignment. If you select static, enter an IP address, gateway and netmask. 11. (Optional) Enter a CS Key and certificate. CloudSystem automatically provides a certificate and key if you do not enter one in these fields. 12. Accept the license agreement, then click Install. After the installation is complete, close the command window. 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. IMPORTANT: After running csstart, 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. (Optional) Increasing virtual appliance deployment timeout in RHEL 6.5 deployments If you are deploying CloudSystem on KVM management hypervisors with RHEL 6.5 operating systems, then you will need to increase the amount of time allotted for the virtual appliance deployment. If you do not update this setting, then your deployment may fail due to a timeout issue. Before running the First-Time Installer, perform the procedure in Using cshaupdate to set virtual router IDs and change deployment timeout settings (page 77). Install the Monitoring appliance and Enterprise 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 in the HP Software Depot at 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 21 Installing the Monitoring appliance and Enterprise appliance driver 1. Download the MySQL Connector/J (JDBC driver) package from the HP Software Depot. 2. Extract libmysql-java_ _all.deb from the zip file and add it to your staging environment. 3. Using cloudadmin credentials, SSH in to the Management appliance (ma1). 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: chown cloudsystem:cloudsystem libmysql-java_ _all.deb chmod 644 libmysql-java_ _all.deb d. Change the directory to /boot/cloudsystem/cs-monasca-controller1/. e. Copy the MySQL JDBC driver to the directory. (Optional) Increasing virtual appliance deployment timeout in RHEL 6.5 deployments 53

54 f. Update the MySQL JDBC driver file permissions: chown cloudsystem:cloudsystem libmysql-java_ _all.deb chmod 644 libmysql-java_ _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_ _all.deb chmod 644 libmysql-java_ _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_ _all.deb chmod 644 libmysql-java_ _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_ _all.deb chmod 644 libmysql-java_ _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_ _all.deb chmod 644 libmysql-java_ _all.deb Run the CloudSystem First-Time Installer 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. Figure 11 Results of running the First-Time Installer 54 KVM management hypervisor installation