Intel Cloud Builders Reference Implementation

Intel Cloud Builders Reference Implementation HP CloudSystem Enterprise Intel Cloud Builders Reference Implementation HP CloudSystem Enterprise Intel Xeon Processor 5500 Series Intel Xeon Processor 5600 Series Intel Xeon E5 Processor Family Audience and For enterprise IT organizations, system integrators, and cloud service providers who are looking to build their own cloud infrastructure, the decision to use a cloud for the delivery of IT services is best done by starting with the knowledge and experience gained from previous work. This reference implementation demonstrates application deployment using HP CloudSystem Enterprise, Intel Xeon Processor E5 Family, and Software-as-a-Service (SaaS) products. Build full-scale deployments of private and hybrid cloud environments with HP CloudSystem Enterprise which lets customers unify management across, private, public, and hybrid clouds and adds advanced infrastructure-to-application lifecycle management. There are many reasons why HP CloudSystem Enterprise is a highly effective hybrid cloud solution. HP CloudSystem Enterprise leverages the key benefits of HP CloudSystem Matrix, such as the infrastructure service designer, automated infrastructure provisioning, and out-of-the box bursting capabilities to public and managed cloud providers such as HP Cloud Services, Amazon Web Services, and Savvis. It also adds the robustness of HP Cloud Service Automation, the software engine that provides one-touch, multi-tier provisioning, and comprehensive management of both applications and infrastructure across private and hybrid clouds. While CloudSystem Enterprise is optimized for HP infrastructure, it is open and heterogeneous and supports third-party infrastructure, plus multiple hypervisors and operating systems. The purpose of this document is to describe how to set up and take advantage of the HP CloudSystem Enterprise features in order to deploy a two-tier Linux infrastructure on both virtual and physical servers. With HP CloudSystem Enterprise, you can get the benefits of a full service deployment for both private and hybrid cloud environments. HP CloudSystem is the product of HP s experience in delivering industry-leading automation, application management, and Converged Infrastructure capabilities. It enables organizations to build and manage cloud services across private clouds, public clouds, and traditional IT. As part of HP s Converged Cloud architecture, clients have a simplified, integrated architecture that is easier to manage and provides flexibility and portability between private, public, and managed clouds. August 2012

Intel Cloud Builders Reference Implementation HP CloudSystem Enterprise The audience for this Intel Cloud Builders implementation guide includes: Enterprise IT and Line of Business (LOB) organizations deploying private and/or hybrid cloud solutions to transform their internal data center infrastructure into a cloud environment with the goal of offering better services to their internal customers or users. Intel Xeon Processor 5500 Series Intel Xeon Processor 5600 Series Intel Xeon E5 Processor Family Systems integrators looking to transform the cost structures and agility of their client offerings by providing cloud computing services and solutions that accelerate revenue potential by reducing time to market. Cloud service providers that offer public and hybrid services to consumers. This document assumes that the reader has read and followed the Intel Cloud Builders Guide to Cloud Design and Deployment for HP CloudSystem Matrix reference architecture document prior to reading this Reference Implementation document. The Intel Cloud Builders reference architecture with HP CloudSystem explains in detail the hardware and configuration requirements that will be used throughout this Reference Implementation.

Table of Contents Executive Summary...5 Software as a Service...5 Process Steps...5 Configuration...6 Summary of Hardware Requirements...6 HP CloudSystem Enterprise Components...6 Open Source and Third-Party Components...6 Network Pool Requirements...6 Storage Requirements...7 Server Pool requirements...7 Multi-Tenant Resource Pool Requirements...7 Network Topology...7 General Test Cases...8 Test Case ID: 1 Download Support Files...8 Test Case ID: 2 Import Physical LAMP IO Template...9 Test Case ID: 3 Configure Physical LAMP IO Template...10 Test Case ID: 4 Import/Configure Virtual LAMP IO Template...12 Test Case ID: 5 Download Required Software Packages...13 Test Case ID: 6 Import HP Operations Orchestration Service Designs...14 Test Case ID: 7 Import Software Packages...15 Test Case ID: 8 Create New Application Policies...17 Test Case ID: 9 Configure SiteScope...19 Test Case ID: 10 Configure SiteScope to Monitor MariaDB...19 Test Case ID: 11 Import HP SiteScope Template for Application and Server Monitoring...20 Test Case ID: 12 Configure CSA and SiteScope Monitor Credentials...21 Test Case ID: 13 Import Application into HP Application Deployment Manager (ADM)...23 Test Case ID: 14 Create a New Service Provider for HP SiteScope...24 Test Case ID: 15 Create HP Cloud Service Automation Service Offering...25 Test Case ID: 16 Request Service Subscription...26 Test Case ID: 17 Verify Requested Service Subscription...27 Test Case ID: 18 Create WordPress Users...28 Test Case ID: 19 Post Test Entries in WordPress...29 3

Test Case ID: 20 Return Resources...30 Storage Provisioning Manager (SPM)...31 Test Case ID: 21 Add 3PAR Storage Array...31 Test Case ID: 22 Add 3PAR Storage Pool...33 Test Case ID: 23 Create 3PAR Storage Template...34 Test Case ID: 24 Create On-Demand Storage IO Template...35 Test Case ID: 25 Create On-Demand Storage Service...37 Things to Consider...38 Troubleshooting...38 Conclusion...38 Glossary...38 Appendix...39 References...40 4

Executive Summary HP Converged Cloud is the industry s first hybrid delivery approach and portfolio based on a common architecture that enables customers to build, manage, secure, and consume cloud services that span private, managed, and public clouds as well as traditional IT. HP s Converged Cloud is based on open standards and supports multi-vendor, heterogeneous software and hardware. It is built on industry-leading HP Converged Infrastructure, HP Management and Security, HP Information Management, and OpenStack technologies. By extending the power of the cloud across infrastructure, applications and information, HP Converged Cloud provides choice, confidence and consistency. This enables customers to speed innovation, enhance agility, and improve financial management across their organization. HP CloudSystem is the most complete, integrated, open platform that enables enterprises and service providers to build and manage services across private, public and hybrid cloud environments. Based on proven, market leading HP Cloud Service Automation and Converged Infrastructure, HP CloudSystem is tailored for the requirements of enterprises and service providers at various stages of cloud maturity with three offerings: Entry configuration for infrastructure-as-a-service (IaaS) with HP CloudSystem Matrix that lets IT customers provision infrastructure and applications in minutes. Full-scale deployment of private and hybrid cloud environments with HP CloudSystem Enterprise, which lets customers unify management across private, public, and hybrid clouds, while adding advanced infrastructure-to-application lifecycle management. Advanced capabilities for service providers with HP CloudSystem Service Provider, facilitating deployment of public and hosted private clouds that deliver complete service aggregation and management. CloudSystem is optimized for HP Converged Infrastructure technology, including HP 3PAR Storage the high-performance FlexNetwork architecture from HP Networking, mission-critical HP-UX, and comprehensive security capabilities. HP CloudSystem also supports third-party servers, storage and networking to protect customers investments. Clients who have already invested in existing software and infrastructure equipment can easily expand their current architectures to achieve a private, public, or complete hybrid cloud environment with HP. The result is a complete cloud solution that lets enterprises gain agility and speed, and allows service providers to drive top-line growth. As a part of the HP Converged Cloud architecture, clients have a simplified, integrated architecture that is easier to manage and provides flexibility and portability between private, public, and managed clouds. Software-as-a-Service The real power and functionality of HP CloudSystem Enterprise shines when deploying Software-as-a-Service (SaaS). The following cases demonstrate how HP CloudSystem Enterprise is used to install, configure, and deploy the WordPress application on a LAMP infrastructure. LAMP is an industry acronym for Linux, Apache, MySQL/MariaDB, and PHP/Python. Instructions are provided to easily guide the reader through the configuration. The result is a functioning HP CloudSystem Enterprise environment that can automatically provision and decommission a WordPress application and infrastructure instance. Process Steps This reference implementation details the major steps required to install and configure the WordPress application. They include the following: Retrieving and unpackaging the scripts and content needed for configuring the HP CloudSystem Enterprise environment Creating the HP Infrastructure orchestration Infrastructure templates Retrieving the Linux software packages Importing and customizing the HP Operations Orchestration service designs Importing and customizing the HP Server Automation software policies Importing and configuring the application software components Creating the application service in HP Cloud Service Automation (CSA) After these steps are complete, the application is available for business users to automatically deploy using the CSA Service Request Catalog. Additional cases will demonstrate the monitoring capability of the HP SiteScope application as well as the automatic storage provisioning when using HP Storage Provisioning Manager. 5

Configuration The reference implementation was tested on an HP CloudSystem Enterprise environment as shown in Figure 1. Summary of Hardware Requirements HP CloudSystem Enterprise Components Component Management Server Blade Servers Testing Environment Version HP Onboard Administrator 3.55 HP Virtual Connect Manager 3.51 HP Integrated Lights-Out 1.01 (ilo 4) HP Matrix Operating Environment HP ProLiant DL360 Gen8 HP ProLiant BL460c Gen8 Physical and virtual servers 7.1 HP Server Automation 9.13 HP SiteScope 2.01 HP Operations Orchestration 9.00 3PAR V800 HP Cloud Service Automation 2.01 3.1.1 (MU1) Contact your HP Support representative and verify that the following hot-fix has been installed: HOTFIX_CSA4M_ QX148348_26_07_2012_SAPLUGIN Open Source and Third-Party Components Figure 1: HP CloudSystem Enterprise Environment Component Operating System Version Red Hat Enterprise Linux Server 5.8 x64 Virtualization Manager VMware vcenter Server 5.0.0 Network Pool Requirements Network Name Production network Management network Name in Service Template PROD_A MGMT_A Notes Production network for communication between the web server and the database server The deployment network used to install the OS, using HP Server Automation 6

Storage Requirements CloudSystem Enterprise storage pool entries must be defined for physical server deployment. A VMware datastore must be available for virtual machine provisioning. Description Total # LUNs Size Redundant Paths to Storage Disk is Bootable Storage Pool Entry 6 40 GB Yes Yes VM Datastore N/A 100 GB Yes No Server Pool Requirements The table below lists the minimum requirements for physical and virtual servers. These values are specified in the HPIO templates and may be adjusted for your specific environment. Server name Minimum CPU frequency Minimum CPU cores Minimum memory database 1.0 GHz 2 cores 4 GB webapps 1.0 GHz 2 cores 4 GB Multi-Tenant Resource Pool Requirements The table below lists the minimum requirements for two VMware Resource Pools. These values are specified in the Resource Pool dialog when created as part of a VMware vcenter cluster. Resource Pool CPU Resources Memory Resources Boise RP 16000 MHz 32000 MB Seattle RP 8000 MHz 25000 MB Network Topology HP CloudSystem Enterprise utilizes HP BladeSystem enclosures to provide 10GbE connectivity between all the blade servers in the configuration. HP Virtual Connect (VC) modules, in addition to enabling the decoupling of the logical server from the physical hardware, were used to make multiple 10GbE connections to the external network switches. For this project, a simple flat network topology was used consisting of two full 10GbE networks, plus two 8Gb/s FCoE Storage Area Networks. It is assumed that the Virtual Connect modules and appropriate networking layouts were configured when HP CloudSystem Enterprise was installed. 1. A 10GbE Production Network that connected all the nodes of a cluster was used by the users and administrators to access the VMs. This network is referred to as the Prod_A network in many of the test cases. 2. A 10GbE Management Network was used for server hardware and software management, as well as node-to-node communications including monitoring, logging and data. This network is referred to as the Mgmt_A network in many of the test cases. 7

General Test Cases Test Case ID: 1 Download Support Files Download the HP CloudSystem Enterprise configuration scripts and files that will help deploy the LAMP WordPress Application. HP CloudSystem Enterprise environment has been configured and running. This includes the installation of HP CloudSystem Matrix (the Matrix Operating Environment, System Insight Manager, a minimal Operations Orchestration, Server Automation and SiteScope modules) with the addition of the full version of Operations Orchestration, a database server, and HP Universal Configuration Management Database (UCMDB). See the Intel Cloud Builders Guide: HP CloudSystem Matrix reference architecture (RA) document for detailed configuration settings. This step was duplicated in the RA document and can be skipped if the support file has already been downloaded. Execution Steps 1. Access the Matrix Operating Environment (OE) Central Management Server (CMS). This is the server where the Matrix OE infrastructure orchestration (IO) and HP Systems Insight Manager (SIM) were installed. 2. Open a browser to http://h71028.www7.hp.com/enterprise/us/en/partners/cloudmapsopensourcesoftware.html. 3. Retrieve and unpack the HP-LAMP-WordPRess-v2.zip file into a location that is accessible to the CMS and other servers in the CloudSystem Enterprise environment. This file can be found as part of the WordPress and SiteScope Monitoring HP CloudMap. Unpacked zip file: Folder Filename Description HP Application Deployment Manager HP Cloud Service Automation Service Design HP Insight Orchestration Templates HP SiteScope Monitors HP Server Automation Content/HP-LAMP-SA.zip HP-LAMP-Example.xml LAMP-WP.zip HP-LAMP.xml HP-LAMP-VM.xml CSA-LAMP-Application- Monitors.tmpl get_rmt_svr_ip.zip runonce startagent.sh LAMP ADM Application LAMP for WordPress Service Design LAMP physical server template LAMP VM template HP SiteScope monitor template LAMP required script to retrieve server IP addresses SA agent initialization script Shell script used to start the SA agent. 8

Test Case ID: 2 Import Physical LAMP IO Template Import the LAMP physical IO Template HP CloudSystem Enterprise installed and configured. Server, storage, and network resources have been allocated and configured. Virtual (VMware) and Physical (HP Server Automation (SA)) RHEL5.8 x64 templates have been created and are visible in HP CloudSystem Matrix. A SPArchitect user has been created, added to the HPIO_Architect group, and the credentials for this user account are known. The HP-LAMP-WordPress-v2.zip package has been downloaded, unpackaged, and is visible to the HP CloudSystem Enterprise environment. Execution Steps 1. Launch HP Matrix IO Designer from the browser (https://<cms_ip>:51443/hpio/designer) or the Windows Start Menu (All Programs > HP Insight Management > HP Matrix Infrastructure Orchestration > HP Matrix IO Designer) and log on as an administrator. 2. Click Import and browse to the location where you unpacked HP-LAMP-Wordpress-v2.zip. The templates are found in the HP Matrix infrastructure orchestration template folder. Select the HP-LAMP.xml template. 3. You will get a warning that the imported template references software that is not found on this CMS. You can ignore this message because the software deployment jobs will be configured in a later step. 4. Click Finish to complete the import. The Validation Status will be marked with a red X, which indicates that there are errors. In the next steps, you will configure software deployment jobs and server groups for the template to fix the errors. Physical LAMP IO Template has been imported into HP Matrix IO Designer. 9

Test Case ID: 3 Configure Physical LAMP IO Template To configure the appropriate networks and software deployment jobs for the template. Virtual (VMware) and Physical (SA) RHEL5.8 x64 templates have been created. Physical LAMP IO Template has been imported into HP Matrix IO Designer. Execution Steps 1. Click Show Issues in the Validation Status area to see the issues which require attention. The issues are indicated with red boxes, as shown in the image below. 2. Right-click the network icon MGMT_A and select Edit Network Configuration. 3. Select the Select a specific network option in the Configure Network dialog. The Management network must be the network used to connect to Server Automation. 4. Select the network you want to use. If you are unsure of which to use, check with your CloudSystem Enterprise system administrator. 5. Click OK. 6. Repeat steps 2-5 for the PROD_A network component. 10

Execution Steps Configuring server groups To configure the server groups, complete the following steps: 1. Right-click the webapps server and select Edit Server Group Configuration. 2. Select the Config tab in the Configure Server Group dialog. Modify the attributes for the servers in the group if desired. You can keep the defaults or change these values as necessary. These values are used to select appropriate servers during deployment, so be sure you have servers available that match any processor or memory requirement you set. The minimum values provided are acceptable for the LAMP deployment. You should not change the Group Name. 3. Select the Networks tab. Verify that PROD_A is selected as the Primary Interface. Set the Assignment Type for the MGMT_A and PROD_A networks. You may get this information from the CloudSystem Matrix administrator. 4. Select the Software tab. 5. Select software where the Source is SA (Server Automation) and the OS Type is Linux. Consult your Server Automation administrator if necessary to ensure you are choosing the appropriate Linux distribution. A sample kickstart file for OS deployment is included in the Appendix. 6. Click OK. 7. Repeat steps 1-6 for the database server. The errors should now be resolved for the HP-LAMP template. The Validation Status will be marked with a green check mark. You can now change the template to Published by selecting the Published option. Click Save to save the template, and then close the dialog box. The HP-LAMP physical template has now been successfully configured. Physical IO LAMP Template has been configured and is ready for deployment. 11

Test Case ID: 4 Import/Configure Virtual LAMP IO Template Import and configure the LAMP Virtual IO Template. Execution Steps Virtual (VMware) and Physical (SA) RHEL5.8 x64 templates have been created. Steps for setting up the VMware template with a HP Server Automation (SA) agent were included in the RA document. Repeat the steps in Test Case ID: 2 and Test Case ID: 3 to import the HP-LAMP-VM template. The software selected for the VM template must be a RHEL 5.8 VMware template. For the virtual LAMP IO template, the Source field indicates VMware and the VMware template must include the Server Automation agent installation software and configuration scripts. Virtual IO LAMP Template has been imported and configured in HPIO Designer. The template will look similar to this: 12

Test Case ID: 5 Download Required Software Packages Acquire software packages that will be deployed as part of the LAMP WordPress deployment. Execution Steps Networking has been configured so that access to the Internet is available. If security settings inhibit full access, then the required software packages will have to be acquired from a system that does have full access to the Internet. From there, files can be made visible to the HP CloudSystem Enterprise environment according to local security guidelines. Create a temporary folder on your CMS and download the required software packages. The packages listed below were used to develop and test the reference implementation. Newer versions may be available and supersede those listed here. If you are unable to obtain the versions listed below, be sure that new versions are compatible, and include all necessary dependencies. Download the following RPM packages for Red Hat EL 5 from http://pkgs.org/centos-5-rhel-5/ius-x86_64/: epel-release-5.4.noarch gmp-4.1.4-12.3_2.el5.x86_64 ius-release-1.0-10.ius.el5.noarch libtool-ltdl-1.5.22-7.el5_4.x86_64 perl-dbi-1.52-2.el5.x86_64 php52-5.2.17-6.ius.el5.x86_64 php52-cli-5.2.17-6.ius.el5.x86_64 php52-common-5.2.17-6.ius.el5.x86_64 php52-ldap-5.2.17-6.ius.el5.x86_64 php52-mysql-5.2.17-6.ius.el5.x86_64 php52-pdo-5.2.17-6.ius.el5.x86_64 sysstat-7.0.2-11.5.x86_64 Download the following packages from http://mariadb.org/: MariaDB-client-5.3.7-116.el5.x86_64 MariaDB-server-5.3.7-116.el5. x86_64 MariaDB-shared-5.3.7-116.el5.x86_64 Download the WordPress application in zip file format from http://wordpress.org/download/: wordpress-3.4.1.zip You can also download a WordPress logo to customize your CSA Service Request Offering from http:// wordpress.org/about/logos/. 15 RPM and 1 zip software packages exist in a temporary folder accessible to the CMS and CloudSystem Enterprise environment. 13

Test Case ID: 6 Import HP Operations Orchestration Service Designs Install HP Operations Orchestration workflows that contain instructions for deploying and configuring software packages. HP-LAMP-WordPress-v2.zip package has been downloaded and unpackaged. The LAMP-WP.zip file is found in the HP Cloud Service Automation Service Design folder and contains the HP Operations Orchestration workflows for the reference implementation. Access to the server running the full version of HP Operations Orchestration OO. Execution Steps 1. Unzip LAMP-WP.zip to a convenient location that can be accessed by the Cloud Server Automation (CSA) server. 2. On the HP Cloud Service Automation server, open HP Operations Orchestration Studio in the Windows Start menu in Hewlett-Packard > Operations Orchestration > HP Operations Orchestration Studio. 3. Log on as admin. Important: Be sure you are connected to the repository on the HP Cloud Service Automation server, and not the CMS. 4. Click Repository > Import Repository in the main menu. 5. Enter IO LAMP-Application Monitoring for the repository name. 6. Navigate to the folder where you unzipped the distribution files. Select the LAMP SiteScope Example folder and click OK. 7. Click Repository > Set Target Repository and select Default Public Repository. 8. Click Repository > Publish Source to Target Preview. 9. In the Publish/Update dialog, expand the folders under Library so you can see the new workflows. 10. Click Apply then OK to the successful import dialog box. 11. In HP Operations Orchestration Studio, check that the newly added workflows are in the Default Public Repository, and are checked out. You can find them in the My Changes/Checkouts panel. 12. Right-click the HP folder (Library -> CSA -> Contrib -> HP) and select Check In Tree to check in the newly added workflows. 13. Expand the Configuration folder and Selection Lists and double-click to open HPIO Templates. 14

14. If the HP-LAMP or HP-LAMP-VM templates are not listed, or there are other items in the list besides HP-LAMP and HP-LAMP-VM: a. Click Lock to check out the HPIO Templates Selection List for editing. b. Click Add in the right panel. c. Add the HP-LAMP template by replacing the default New Selection name. d. Click Add again to add the HP-LAMP-VM template. 15. Remove any other pre-existing templates (besides HP-LAMP or HP-LAMP-VM) by selecting the template and clicking Remove. 16. Click Lock to save and check in your changes. Enter a comment or leave blank on the Check In dialog box, then click OK. 17. Close HP Operations Orchestration Studio. HPIO Template LAMP workflow was imported and checked into the Operations Orchestration default repository. Test Case ID: 7 Import Software Packages Import the WordPress and MariaDB software packages. RPM/ZIP software packages have been downloaded and are accessible to the CMS and other systems in the CloudSystem Enterprise environment (from Test Case ID: 5). HP Server Automation Java Client has been installed. See the RA document for instructions on how to install the client software. Execution Steps 1. Log in to HP Server Automation Java Client as an administrative user (for example hpsa_admin). 2. Click on the Library button on the bottom left. Click on the By Folder tab and Right-click on the Library folder and select Import Software. 3. Click Browse to the right of the File(s) field and select all of the RPM packages that were downloaded in the Test Case ID:5. The Type field should be automatically set to RPM (and there should be 15 RPM files). 4. Change the value for Folder to /Package Repository/All Red Hat Linux/Red Hat Enterprise Linux Server 5 X86_64. Click Select. 5. Change the value for Platforms to Red Hat Enterprise Linux Server 5 X86_64. 6. Click Import. 15

Execution Steps 7. Import the wordpress-3.2.1.zip package: a. Right-click Library and select Import Software. b. Click Browse to the right of the File(s) field and select wordpress-3.4.1.zip. The Type field should be automatically set to ZIP Archive. c. Change the value for Folder to /Package Repository/All Red Hat Linux/Red Hat Enterprise Linux Server 5 X86_64. Click Select. d. Change the value for Platforms to Red Hat Enterprise Linux Server 5 X86_64. e. Click Import. 8. Import the get_rmt_srvr_ip.zip package. This file is included in the HP-LAMP-WordPress-v2.zip file under the HP Server Automation Content folder. a. Right-click Library and select Import Software. b. Click Browse to the right of the File(s) field and select get_rmt_srvr_ip.zip from the HP Server Automation Content folder. The Type field should be automatically set to ZIP Archive. c. Change the value for Folder to /Package Repository/All Red Hat Linux/Red Hat Enterprise Linux Server 5 X86_64. Click Select. d. Change the value for Platforms to Red Hat Enterprise Linux Server 5 X86_64. e. Click Import. 9. Browse to Library/Package Repository/All Red Hat Linux/Red Hat Enterprise Linux Server 5 X86_64. 10. Right-click on get_rmt_srvr_ip.zip package and select Open. 11. Change the Default Install Path value to /tmp. Click on File and Save to save your changes. Close the window. 15 RPM and 2 ZIP Software packages installed in Server Automation (SA) under the Red Hat Enterprise Linux Server 5 X86_64 Package Repository. 16

Test Case ID: 8 Create New Application Policies Application Deployment Manager (ADM) Policies for each application, MariaDB and WordPress, are created to specify installation/deployment instructions Execution Steps RPM/ZIP software packages have been downloaded and imported into SA. Three new policies are required. The first is ApacheWordPress which is created using the following steps: 1. Right-click the Library folder and select New > Software Policy. 2. Set the following values: a. Set Name to ApacheWordPress. b. Click Select and set the Location to /Package Repository/All Red Hat Linux/Red Hat Enterprise Linux Server 5 X86_64. c. Set the OS to Red Hat Enterprise Linux Server 5 X86_64. 3. Select Policy Items in the Views panel. 4. Click Add in the toolbar. Click on the Browse Folders tab. 5. Add Red Hat policies: 6. Expand the Package Repository/All Red Hat Linux/Red Hat Enterprise Linux Server 5 X86_64 folder. a. Select the following: epel-release-5.4.noarch get_rmt_srvr_ip.zip gmp-4.1.4-12.3_ 2.el5.x86_64 ius-release-1.0-10.ius.el5.noarch libtool-ltdl-1.5.22-7.el5_4.x86_64 php52-5.2.17-6.ius.el5.x86_64 php52-cli-5.2.17-6.ius.el5.x86_64 php52-common-5.2.17-6.ius.el5.x86_64 php52-ldap-5.2.17-6.ius.el5.x86_64 php52-mysql-5.2.17-6.ius.el5.x86_64 php52-pdo-5.2.17-6.ius.el5.x86_64 wordpress-3.4.1.zip b. Click Select. 7. Click Add in the toolbar. Click on the Browse Folders tab. 8. Add Python policies: a. Browse to the Library/Opsware/Tools/Python Opsware API Access folder. b. Select OPSWagent_tools_unix-45.0.19256.0.zip. c. Click Select. 9. Click File > Save to save the ApacheWordPress policy. 10. Verify that the 13 files you selected in the steps above are listed. 11. Close the View window. 17

Execution Steps The second is the MariaDB policy, which is created using the following steps: 1. Right-click the Library folder and select New > Software Policy. 2. Set the following values: a. Set Name to MariaDB. b. Click Select and browse to set the Location to /Package Repository/All Red Hat Linux/Red Hat Enterprise Linux Server 5 X86_64. c. Set the OS to Red Hat Enterprise Linux Server 5 X86_64. 3. Select Policy Items in the Views panel. 4. Click Add in the toolbar. Click on the Browse Folders tab. 5. Browse to the /Package Repository/All Red Hat Linux/Red Hat Enterprise Linux Server 5 X86_64 folder. 6. Select the following: get_rmt_srvr_ip.zip perl-dbi-1.52-2.el5.x86-64 sysstat-7.0.2-11.el5.x86_64 7. Click Select. 8. Click Add in the toolbar. Click on the Browse Folders tab. 9. Browse to the /Opsware/Tools/Python Opsware API Access folder. 10. Select OPSWagent_tools_unix-45.0.19256.0.zip. 11. On the File menu, click Save to save the MariaDB software policy. 12. Verify that the 4 files you selected in step 6 are listed. 13. Close the window. The third is the MariaDBPackage policy, which is created using the following steps: 1. Right-click the Library folder and select New > Software Policy. 2. Set the following values: a. Set Name to MariaDBPackage. b. Click Select and browse to set the Location to /Package Repository/All Red Hat Linux/Red Hat Enterprise Linux Server 5 X86_64. c. Set the OS to Red Hat Enterprise Linux Server 5 X86_64. 3. Select Policy Items in the Views panel. 4. Click Add in the toolbar. Click on the Browse Folders tab. 5. Browse to the /Package Repository/All Red Hat Linux/Red Hat Enterprise Linux Server 5 X86_64 folder. 6. Select the following: MariaDB-client-5.3.7-116.el5.x86_64 MariaDB-server-5.3.7-116.el5.x86_64 MariaDB-shared-5.3.7-116.el5.x86_64 7. Click Select. 8. On the File menu, click Save to save the MariaDBPackage software policy. 9. Verify that the 3 files you selected in step 6 above are listed. 10. Close the window. MariaDB and WordPress software policies have been added to the SA software policies list. 18

Test Case ID: 9 Configure SiteScope Verify that SiteScope, HP s advanced monitoring tool, is configured and running properly. HP CloudSystem Enterprise installed and configured. SiteScope server is accessible and administrator credentials are known. Execution Steps 1. From the CMS, launch SiteScope as admin using http://<sis_server>:8080/sitescope. a. If no content appears, install Java from http://www.java.com. 2. Preferences tab (lower left corner), General Preferences, expand Licenses section. 3. If Points license does not exist, or is less than 10, obtain a license file and then Import. SiteScope content is viewable, license file has been imported and at least 10 license points are available. Test Case ID: 10 Configure SiteScope to Monitor MariaDB HP SiteScope requires a JDBC driver for MariaDB. You can use the MySQL driver because it is compatible with MariaDB. HP CloudSystem Enterprise installed and configured. SiteScope server is accessible and administrator credentials are known. Execution Steps 1. Download the MySQL JDBC driver zip file from the MySQL website at http://www.mysql.com to a folder on the SiteScope server. 2. You can find the download link by selecting the Downloads tab and then scrolling down to Connector/J, which is in the MySQL Connectors section. 3. Uncompress the files to a temporary folder and locate mysql-connector-java-5.1.20-bin.jar (or a later version of this file). 4. Copy mysql-connector-java-5.1.20-bin.jar (or the later version of this file) to the <HP SiteScope folder>\web-inf\lib folder on the HP SiteScope server. 5. Stop and restart the SiteScope service from the Windows Services console. JDBC driver for MariaDB has been downloaded, installed, and the HP SiteScope service has been successfully restarted. 19

Test Case ID: 11 Import HP SiteScope Template for Application and Server Monitoring Import the HP SiteScope templates so that when the web and database servers are deployed as part of the 2-tier infrastructure LAMP deployment, the hooks are in place to monitor the Apache server and database utilization parameters. Memory, storage, and CPU utilization will also be monitored for each deployed server. HP CloudSystem Enterprise installed and configured. SiteScope server is accessible and administrator credentials are known. Execution Steps 1. The SiteScope template CSA-LAMP-Application-Monitors.tmpl is in the HP SiteScope Monitors folder extracted from the HP-LAMP-WordPress-v2.zip file. 2. Record the folder path and the name of this template file. You will need this information later. 3. Open http://<sitescope Server>:8080. 4. Select the Templates tab. 5. Right-click the CSA Templates folder and select Import. 6. Enter the file name and path that you recorded in step 3. 7. Click Ok. 8. Expand SiteScope/CSA Templates/LINUX-database. 9. Select user. Validate that the default value for the user is root. Click Save to save any changes. 10. Select password. Set the password for root access on the database virtual machine. Check the Password variable box to hide the password value. Click Save. You can close the browser window to SiteScope. 11. Expand SiteScope/CSA Templates/LINUX-webapps. 12. Select user. Validate that the default value for the user is root. Click Save to save any changes. 13. Select password. Set the password for root access on the web server virtual machine. Check the Password variable box to hide the password value. Click Save. JDBC driver for MariaDB has been downloaded, installed, and the HP SiteScope service has been successfully restarted. 20

Test Case ID: 12 Configure CSA and SiteScope Monitor Credentials Set the default credentials for the WINDOWS-CSA-TARGETS and LINUX-CSA-TARGETS. HP CloudSystem Enterprise installed and configured. Administrator access to both the CSA server and SiteScope server. Execution Steps 1. Copy the entire C:\Program Files\Hewlett-Packard\CSA\scripts\sis folder from the HP Cloud Service Automation server to a temporary location on the HP SiteScope server. HP SiteScope and HP Cloud Service Automation cannot run on the same server. a. For example, remote desktop into the CSA server and use winscp to copy the entire directory. b. Copy the directory contents to a temporary folder on a server accessible by both the CSA server and the SiS server. 2. In the temporary sis folder on the SiS server, open csainstall.properties in a text editor. This file contains all configurable installation parameters. 3. You must provide the following installation parameter for the HP SiteScope server: a. sisdir = <HP SiteScope install directory> (this is usually C:\Sitescope) 4. Confirm that the following installation parameters are correct: a. SiSFQDN = <SiteScope Server Hostname or IP address> b. SiSIPPort = <SiteScope Port Number> 8080 c. SiSUserName = <SiteScope Server Login Name> admin d. SiSPassword = <SiteScope Server Password> admin 21

Execution Steps 5. In the temporary sis folder on the SiS server, run install.bat from a command window. a. Warning: Do not run install.bat on the HP Cloud Service Automation server. Doing so will prevent the HP Cloud Service Automation flows from running correctly. 6. Access SiteScope from a browser (http:<sis server>:8080/sitescope). b. In the menu on the left, click Preferences > Credential Preferences. c. Enter the user name and password for LINUX-CSA-PREFERENCES and WINDOWS-CSA-PREFERENCES. i. These are the credentials (user name and password) that were used for the Windows and Linux VM templates. ii. If you are going to deploy both virtual and physical solutions, the password needs to match for both the VM and Physical deployments, so make sure the same password is used in the VMware and SA RHEL template (usually specified in the kickstart.cfg file). Inside HP SiteScope Credential Preferences, the Login credentials have been configured for the WINDOWS- CSA-TARGETS and LINUX-CSA-TARGETS entries. 22

Test Case ID: 13 Import Application into HP Application Deployment Manager (ADM) Test Case ID: 13 Import Application into HP Application Deployment Manager (ADM) Adobe Flash 10 installed on the CMS, the HP SA Application Deployment Manager tool configured and available (Application Deployment Manager will not launch unless Flash 10 or greater has been installed). See steps for installing Adobe flash in the RA document. HP-LAMP-WordPress-v2.zip archive package downloaded from HP, unpacked, and visible to the HP CloudSystem Enterprise environment. Root access to the HP Server Automation server. Execution Steps 1. Copy HP-LAMP-Example.xml under the HP Application Deployment Manager Application folder to the / tmp directory on your HP Server Automation server. You can use a tool such as the scp command or WinSCP to copy from the CMS. scp HP-LAMP-Example.xml root@<sa _ host>:/tmp/hp-lamp-example.xml 2. Log in to the HP Server Automation server: ssh -l root <ip address of SA> 3. Change directories: cd /opt/opsware/da/bin 4. Run the admtool.sh script to import the application:./admtool.sh -i -importfile /tmp/hp-lamp-example.xml -importconflict skip 5. Type exit to close your ssh session. 6. Login to the HP Server Automation Java Client as an administrative user. 7. Click Tools > Application Deployment in the main menu. 8. Select the Applications tab in the lower-left panel. 9. Select CSA > HP Lamp Example > Initial Release in the drop-down list located at the top of the Applications panel. 10. At this point you must update the SITESCOPE_IP_ADDRESS variable in the sitescope_mariadb_config.sh script so it matches the actual IP address of the HP SiteScope server. The default value is 192.168.153.24. To update the IP address, complete the following steps: a. Select the sitescope_mariadb_config.sh script in the left panel. This is located in the MariaDB tier. The source code for the script opens in the Content area on the right. b. Change the Value field for the parameter SS_Address variable in the script source code. c. Click File > Save. 11. Click Manage Applications to create a new version. 12. Expand CSA > HP LAMP Example and select Monitor Release. 13. Click Create Version. 14. Keep the default values in the Create New Version dialog and click Create. Note: The Version should be automatically set to 1. When the progress bar reaches 100%, the application import is complete. Close the Create New Version and Manage Applications dialogs. You may close the ADM session. HP LAMP Application (WordPress and MariaDB deployment instructions) installed in HP Server Automation. 23

Test Case ID: 14 Create a New Service Provider for HP SiteScope Create a Service Provider entry in CSA for HP SiteScope so that HP Cloud Service Automation can talk to HP SiteScope. HP CloudSystem Enterprise installed and configured. SiteScope server is accessible and administrator credentials are known. Execution Steps 1. Go to https://<csa server ip address>:8444/csa/. 2. Select the Provider Management tab. 3. Select the Monitoring category. 4. If you see a SiteScope application monitoring provider in the provider list, then you may skip the remaining steps in this section. 5. Click Create a New Provider. 6. Set the following options in the Provider Creation Wizard: a. Category: Monitoring b. Vendor: Hewlett Packard c. Product: SiteScope d. Service Access Point: http://<sitescope server management IP address>:8080 e. User: admin f. Password: <SiteScope admin password> 7. Click the Next button. 8. Enter a name for the provider, such as HP SiteScope Application Monitoring. You can leave the remaining fields blank. 9. Click the Create button. HP SiteScope service provider has been added to HP Cloud Service Automation. 24

Test Case ID: 15 Create HP Cloud Service Automation Service Offering Create a HP Cloud Service Automation service offering item so that users can select the item for deployment. HP CloudSystem Enterprise installed and configured. Server, Storage, and Network resources have been allocated. HP LAMP Application installed in HP Server Automation. Execution Steps 1. Log in to the HP Cloud Service Automation Provider Console as admin at https://<csa server ip address>:8444/csa/. 2. Select the Service Offerings tab. 3. Click Create a new Service Offering. 4. Set the following options in this dialog: a. Click Browse and browse to the template Library\CSA\Contrib\HP\LAMP Sitescope Example\IO LAMP Application Monitoring with Sitescope\[Matrix Provisioned Cloud(Compute and Applications)]\Matrix Provisioned Cloud (LAMP and Application Monitoring with Sitescope) and click Select. Note that you may need to click Refresh to see the content. b. Name the service offering WordPress Deployment. c. The Category and Description fields will be visible to the user from the Service Request Catalog. An example category you can use is Infrastructure + Application + Monitoring. d. Enter your desired values for the remaining fields. 5. If you want to use a WordPress logo, such as wordpress.png, copy it to your CSA server. For example, if the image is located in c:\progam Files\Hewlett-Packard\CSA\apache-tomcat-6.0.30\webapps\ROOT, the URL field would contain: https://<csa server ip address>: 8081/wordpress.png. 6. Click the Create button. The new Service Offering will be displayed in the list, and its details will be visible in the lower panel when you select a service. 25

Test Case ID: 16 Request Service Subscription Deploy the Infrastructure, Application, and Monitoring components by requesting a service subscription. HP CloudSystem Enterprise has been installed and configured. The server, storage, and network resources have been allocated and are available for deployment. HP LAMP WordPress application service offering has been added to HP Cloud Service Automation. vcenter cluster has been configured. Execution Steps 1. Log in to the HP Service Request Catalog by entering the following address in a browser: https://<csa server ip address>:8444/src. 2. For the credentials fields, use your e-mail address as the User Name and leave the Password field blank (the service request will fail with an invalid e-mail address). 3. Select the Services tab. 4. Click Browse Catalog to the right of the Services heading. 5. Choose the Category you specified when you created the service offering (Infrastructure + Applications + Monitoring was suggested). 6. Click Request in the WordPress Deployment service section. 7. Click on the orange Request button. 8. For Template, select HP-LAMP to deploy physical servers or HP-LAMP-VM to deploy virtual machines. Click Continue. 9. Click on Request. 10. Enter a subscription name and description. 11. Click Continue. 12. Click on Submit. Your subscription ID will be displayed in the Confirmation dialog. Note: your service deployment time will vary depending on the hardware environment, and whether you are doing a virtual or physical deployment. 13. Click Details to view the status of your subscription. Should be Pending until the subscription status goes Active. LAMP Application Service Subscription has been deployed on either virtual or physical hardware. 26

Test Case ID: 17 Verify Requested Service Subscription To verify that the LAMP Service Subscription was deployed successfully. HP CloudSystem Enterprise installed and configured. Server, Storage, and Network resources have been allocated. LAMP Service Description has been deployed. Execution Steps To view the completed subscription request in the Service Request Catalog, complete the following steps: 1. Log in to the HP Service Request Catalog by entering the following address in a browser: https://<csa server ip address>:8444/src. 2. Select the Subscriptions tab. 3. Click Detail to view more information about the service. Note the IP address of the web server. You will need this to complete the WordPress installation. 4. Click View all servers to see more details about the servers. You can also log in to the HP Cloud Service Automation Provider Console to view the service subscription status. 1. Log in to the CSA console by entering the following address in a browser: https://<csa server ip address>:8444/csa. 2. Select the Service Instances tab. You may need to hit the refresh icon to see the new instances. 3. Select the service subscription for WordPress Deployment that you just created. 4. The lifecycle state and service ID will be displayed in the lower panel. The first part of the deployment process is the creation of the service through HPIO. Login to Matrix OE as SPAdmin. Go to Tools > Infrastructure orchestration and click on the Requests tab and you can track the progress of the deployment request in progress. Once HPIO is successful, you can check the progress of the service deployment process in SA Application Deployment. Launch the HP Server Automation Java Client. Click Tools > Application Deployment in the main menu. Select Jobs tab in the left panel to track the progress of the job for the current service deployment. 27

Execution Steps Log on to HP SiteScope at http://<sitescope server management IP address>:8080 and verify that the servers are correctly monitored. The service requestor user log in, as defined in the Service Request Catalog, is created as a parent folder. When the service has been deployed, the HP SiteScope server monitors for CPU, memory, and disk usage, and the application monitors for Apache and MariaDB will show up in the HP SiteScope interface under a folder with the HP Cloud Service Automation requestor username. In the example shown below, the requestor is csa.user@hp.com. LAMP Application Service Subscription was completed successfully. LAMP WordPress infrastructure deployed on either virtual or physical VMs. HP SiteScope monitors for CPU, memory, disk, and servers are active. Test Case ID:18 Create WordPress Users Create an administrator and WordPress user in order to test the deployed application and infrastructure stack. HP CloudSystem Enterprise installed and configured. LAMP Application infrastructure and application components have been deployed, configured, and are up and running. IP Addresses for the web server created in a previous test run. Look in HP SA s Manager Servers for list of IP addresses if necessary or in HPIO, under the Request tab, service details, NIC Details will show the hostname/ip address assigned to the web and database servers. Execution Steps 1. Using the web server IP address obtained in a previous test case, open the following URL in a web browser: http://<web server ip address>/wp-admin/install.php. 2. Enter a website title of your choice and create a new WordPress admin user account. 3. Click on the Install WordPress button. 4. Log in to WordPress using the admin account. 28

Execution Steps 5. Click Users in the left column. 6. Click Add New under Users. 7. Enter details for the new user. 8. Click Add New User to complete the process. 9. Change the role of your new user to Author. Click Edit to open the Edit User menu. Scroll to the bottom and click Update User to accept your edits. 10. Log out of the admin account by clicking on the drop down menu of the admin name at the top right corner of the page. A new user was added to the WordPress blogging application inside the recently deployed LAMP Application/Infrastructure. Test Case ID: 19 Post Test Entries in WordPress Posting a test entry in WordPress will show you that the LAMP stack is working correctly. LAMP servers have been deployed, are powered on, and the web server s IP address is known. Execution Steps 1. Open the following URL in a Web browser: http://<web server ip address>/. Click on Log in and enter your newly added user name and password on the login screen. 2. Click Posts > Add New at the top of the WordPress page. 3. Enter a title and some content. 4. Click Publish. 5. Click View Post to verify your newly created page. Your new post should be visible in the blog, http://<web server ip address>/, which demonstrates that the LAMP stack is working correctly. 29

Test Case ID: 20 Return Resources Cancel the subscription to return the resources to appropriate pools. LAMP servers have been deployed, are powered on, and the web server s IP address is known. Execution Steps 1. Log in to the HP Service Request Catalog by entering the following address in a browser: https://<csa server ip address>:8444/src. 2. Select the Subscriptions tab. a. Locate your subscription and click Cancel. Note: your cancellation time may vary depending on the hardware in your environment and you will be notified by email that the service has been cancelled. 3. To verify that the subscription has been cancelled, complete the following steps: a. Log in as an administrator to the HP Cloud Service Automation Provider Console by entering the following address in a browser: https://<csa server ip address>:8444/csa. b. Select the Service Instances tab. c. Locate the service subscription, and verify that the Subscription State is set to Cancelled. This may take a while for services deployed on physical servers. d. While the Operational State is In Progress, look at the Requests tab in HP MOE infrastructure orchestration to monitor the cancel request. Resources have been returned to the HP CloudSystem Enterprise environment. 30

Storage Provisioning Manager (SPM) The following tests are used to show the Storage Provisioning Manager (SPM) feature set; specifically the ability to provision storage volumes dynamically on an as-needed basis. Previous tests have all required a Storage Pool Entry (SPE) to be previously allocated in the storage array and configured in HP CloudSystem Enterprise. In this test set, we are specifically showing the steps for on-demand storage provisioning for a 3PAR storage array. Setting up a HP EVA array is very similar. Test Case ID: 21 Add 3PAR Storage Array Register a storage array with the SPM. 3PAR Storage Array installed and configured so that it is visible to the CMS. Administrator credentials are available. Networks to the SAN switches (to which the 3PAR is connected) have been created and imported into SPM. Connections to two SAN fabrics are expected if configuring for redundant SAN storage. Execution Steps 1. Launch SPM (https://<cms>:8000). 2. In the navigation pane on the left, under Resources, click on Arrays. 3. Click on the Import Arrays button (bottom-right corner). 4. If you are connecting a 3PAR array: a. Select 3PAR F&T Series Arrays and then click on the Next button b. Enter the hostname, SMI-S port (default is 5989), and credentials (3paradm/3pardata) and then click on the Next button. c. If you encounter problems here, check your firewall and 3PAR settings. d. Select the array and then the Next button. e. Select Matrix Security Group and make sure the Import Arrays normally option is selected and then the Next button. f. De-select the Launch the Import Storage Pool Wizard after completion option and then click on the Finish button. 31

Execution Steps 5. If you are connecting an EVA array: a. Select HP P6000/EVA Disk Arrays. b. Enter the server host and credentials. 6. Click on the Arrays tab and verify that the new SAN array is visible. 3PAR disk array is added to the list of storage arrays visible to SPM. 32

Test Case ID: 22 Add 3PAR Storage Pool Register a storage pool. 3PAR Storage Array added to the Storage Provisioning Manager. Common Provisioning Group (3PAR) created on the respective Storage Array (Storage Pool in SPM parlance). Execution Steps 1. Launch SPM (https://<cms>:8000). 2. In the navigation pane on the left, select Resources -> Storage Pools. 3. Click on the Import Storage Pools button in the bottom-right corner. 4. Select the 3PAR array in the list and then click on the Next button. 5. Select the storage pool to use and then the Next button. 6. Storage Pool Properties: a. Select Matrix Security Group. b. Select Import storage pools normally. c. Next button. 7. Summary: a. Deselect the Launch the Import Volume wizard after completion option. b. Finish button. 8. Verify the new storage pool is in the Storage Pools list. A 3Par Common Provisioning Group item was added to the Storage Provisioning Manager as a new Storage Pool item. 33

Test Case ID: 23 Create 3PAR Storage Template Create a storage template that can be referenced in an IO template for on-demand storage provisioning. 3PAR Storage Pool added to the Storage Provisioning Manager. Execution Steps 1. Launch SPM (https://<cms>:8000). 2. In the navigation pane on the left, select Storage Services -> Templates. 3. Click on the Create Template button and then the Next Button to skip over the Create Template Wizard dialog if it appears. 4. Template Properties dialog: a. Service type: SAN Connected Volume Service b. Template name: <unique name> (e.g. Matrix 3PAR) c. Description: <optional your choice> d. Base template: HP Matrix Default Storage Template e. Copy the selected template as a starting point for this template f. Next button 5. Read-only Requirements dialog: a. Resource Existence Volume Recommended b. Service Deactivation Policy Destroy Data Recommended c. Use Resource <3PAR Array Storage Pool> Required d. Next button 6. In the Allowed Requirement Types dialog, click on the Next button. 7. In the Default Values dialog, click on the Next button. 8. Security dialog: a. Template security group: Matrix Security Group b. Service security group: Matrix Security Group c. Next button 9. In the Summary dialog, click on the Finish button. A 3Par Storage Template was added to the Storage Provisioning Manager and is visible in IO under Storage Templates and in IO Designer. 34

Test Case ID: 24 Create On-Demand Storage IO Template Create an On-Demand storage IO template that can be used to provision and deploy server, network, and storage elements. Matrix 3PAR Storage Template created in Storage Provisioning Manager (name created in Test Case ID: 27). Dual SAN fabrics have been configured and registered. RHEL58x64 physical server template set up in HP Server Automation. Familiar with previous test cases involving IO Template creation. Execution Steps 1. Launch IO Designer (https://<cms>:51443/hpio/designer) using SPAdmin credentials. 2. Click New button. 3. Drag Network, Physical Server Group, and Physical Storage items from the Components pane to the work area. 4. Connect Network to Physical Server Group and Physical Server Group to the Physical Storage. 5. Edit Network Configuration. a. Select appropriate network (e.g. Mgmt_A). 6. Edit Server Group Configuration. a. Config Tab: i. Group Name: web1 ii. Processor Architecture: x86 64-bit b. Networks Tab: i. Hostname: web# ii. Assignment Type: Automatic c. Software Tab: i. RHEL58_x64 (with a SA Source Type) d. Click OK Button. 7. Edit Storage Configuration. a. Click on Select a storage template. b. Select the name of the SPM Storage Template you created previously. c. Enable the Disk is bootable option. d. If you have dual fabric SAN connections, enable the Redundant SAN paths to disk option to enable Multi-path redundancy. e. Click OK button. 35

Execution Steps 8. If Validation Status is Green, enable the published checkbox, and save the IO Template. 9. Verify the IO Template appears in the Templates tab in HP Matrix IO. IO Template created with storage utilizing an on-demand SPM storage template. 36

Test Case ID: 25 Create On-Demand Storage Service Create a physical cloud service solution that deploys a RHEL 5.8 x64 server including networking and ondemand generated storage. IO Template with On-Demand Storage selection created. Server and Networking Resources available, 3PAR connected to SAN. Server resources in a named server pool. Execution Steps This test case will take about 45 minutes to complete once the request has been submitted for processing. 1. Launch IO Portal (https://<cms>:51443/hpio/portal). 2. Storage tab: a. Deactivate any unused stand-alone SPE (under the Volumes list) or they will get selected. 3. Templates tab: a. Select the template created in IO Designer (previous test case). 4. Create Service: a. Service Name: <unique name> (e.g. Svc-3_1) b. Hostname Completion :<some identifier> (e.g. rc-01) c. Options button: i. Email address ii. Verify appropriate physical server pool is in the Selected Server Pools list d. Submit button. e. View Request. i. Monitor Progress. 5. Storage tab: ii. When Complete, login to the deployed system. a. When complete, reactivate all stand-alone SPE so they can be used in other service requests. Linux VM deployed with storage allocated dynamically. 37

Things to Consider While HP has reviewed and tested the test cases in this document, there may be variations in hardware and individual system configurations that required different or additional steps. Please consult the documentation found in the References section below for specific details and guidance. Troubleshooting Physical servers are not cleaned up properly after service is deleted This problem can occur if the boot order is not properly set for servers being used for physical server deployment. Boot order must be set to PXE boot from NIC first. Even if the boot order is properly set prior to deployment, sometimes it gets reset to the default boot order. You can check the boot order of a blade from the Onboard Administrator. Select the blade, and choose Boot Options. In the section showing IPL Device; (Boot order) verify that PXE NIC 1 and PXE NIC 2 are at the top. Move them up to the top with the arrow buttons if they are not in the correct order. Click on the Apply button. You can also use the Onboard Administrator CLI to set boot order for blade servers. Blades with local disks will not boot from SAN when provisioned with Server Automation Even though the Virtual Connect profile is set to boot from SAN, if there are local drives present, a scripted Linux installation will fail. Remove the drives or disable the Array Controller. Deployment fails in CSA, but provisioning completes successfully in HP IO One cause could be that the links to HP Server Automation policies inside the ADM Application HP LAMP example are not working correctly. To check this, do the following in the ADM console: From the Application tab, click on the policy links to determine if they open Server Automation policies. If a link does not open a policy, click Change and search for the policy by name. Then click on OK to update the link. Do this for all the policies. Next, from the Administration tab, check the links at the Tier level to ensure they open the correct policies. Correct the ones that are not working properly. Check the ADM Jobs tab and search for any jobs that failed after the infrastructure was provisioned. Requirements for Linux installation SELinux must be disabled or the WordPress configuration will fail. Disable it in the kickstart files used for Linux installation. Verify that it is not included in any captured virtual machine templates. The configuration file for SELinux is /etc/selinux/config. Do not include the Web Server package in the kickstart file or in any VM template. The required packages are included in the HP Server Automation policies deployed on the web server during application deployment. Conclusion After completing these test cases, you should be able to understand the power and flexibility that HP CloudSystem Enterprise can provide to your organization when it comes to quickly and efficiently deploying SaaS cloud solutions on both virtual and physical infrastructure deployments. Please see http://www.hp.com/go/cloudsystem for more details on how HP CloudSystem can work for your organization. Glossary Term ADM CSA CSA4M HP IO CMS IaaS IO LAMP HP Matrix OE OO RA RI SA SAN SaaS SiS SPE SPM UCMDB Expanded Application Deployment Manager HP Cloud Service Automation HP Cloud Service Automation for Matrix HP Infrastructure Orchestration Central Management Server where HP Matrix OE is installed Infrastructure-as-a-Service HP Infrastructure orchestration Linux, Apache, MySQL/MariaDB, PHP/Python/ Perl HP Matrix Operating Environment HP Operations Orchestration Reference Architecture Reference Implementation HP Server Automation Storage Array Network Software as a Service HP SiteScope Storage Pool Entry Storage Provisioning Manager Universal Configuration Management Database 38

Appendix HP Server Automation Sample Kickstart File for Red Hat Linux This kickstart file was used for testing. Note the steps in the PRE section. These steps are required to properly install the HP Server: Automation agent. Change the IP address shown to the address of the HP Server Automation core server. It is also important to set SELinux to disabled. Be sure to save your kickstart file in UNIX format prior to uploading to HP Server Automation. Note that the OS Installation Profile defined in HP Server Automation must include a Custom Attribute Name kernel_ arguments with a Value of mpath to enable multipath access to storage. # Default Kickstart file for # Red Hat Enterprise Linux 5.y x86-64 # # For information on the kickstart installation mechanism, # see the Red Hat Linux customization guide. # lang en_us # Red Hat installation key # Use --skip for only core server package availability key --skip network --bootproto=dhcp install keyboard "us" text zerombr selinux --disabled #------------------------------------------------------------------ ---- # Automatic LVM-based partition configuration # # For LVM based automatic partitioning use autopart. Red Hat makes the # decisions on drive devices, partitions, and their sizes. #autopart #--------------------------------------------------------------------- bootloader grub --append="pci=bfsort" mpath clearpart --all --initlabel part /boot --fstype ext3 --size=200 --asprimary part / --fstype ext3 --size=1500 --asprimary --grow part swap --size=1024 rootpw password auth --useshadow --enablemd5 firewall --disabled timezone US/Pacific reboot %packages @ Core @ Administration Tools @ Legacy Software Support @ System Tools @ X Window System @ Development Libraries @ Development Tools @ Legacy Software Development @ DNS Name Server @ Legacy Network Server @ Network Servers @ Server Configuration Tools @ Windows File Server @ Editors lm_sensors net-snmp libnl # # CPU monitoring # sysstat # # PRE # %pre # # POST # %post #-- Turn on snmp daemon ------------------------------------ chkconfig snmpd on 39

References For more information on HP CloudSystem, visit http://www.hp.com/go/cloudsystem. The reference implementation zip file (HP-LAMP-WP-RI.zip) can be found at http://h71028.www7.hp.com/enterprise/us/en/partners/ cloudmaps-opensourcesoftware.html. HP software product manuals and documentation for the following products can be found at http://h20230.www2.hp.com/selfsolve/ manuals. You will need an HP Passport to sign in and gain access. HP Cloud Service Automation HP Server Automation HP Operations Orchestration HP CSA for Matrix HP SiteScope HP Storage Provisioning Manager HP Matrix Operating Environment product manuals and documentation can be found at http://h18004.www1.hp.com/products/ solutions/insightdynamics/info-library.html. To learn more about deployment of cloud solutions, visit www.intel.com/cloudbuilders. 2012 Hewlett-Packard Development Company, L.P. 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. 40

Disclaimers Intel processor numbers are not a measure of performance. Processor numbers differentiate features within each processor family, not across different processor families. See www.intel.com/ products/processor_number for details. INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROP- ERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. UNLESS OTHERWISE AGREED IN WRITING BY INTEL, THE INTEL PRODUCTS ARE NOT DESIGNED NOR INTENDED FOR ANY APPLICATION IN WHICH THE FAILURE OF THE INTEL PRODUCT COULD CREATE A SITUATION WHERE PERSONAL INJURY OR DEATH MAY OCCUR. Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked reserved or undefined. Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The information here is subject to change without notice. Do not finalize a design with this information. The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request. Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order. Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling 1-800-548-4725, or by visiting Intel s Web site at www.intel.com. Copyright 2012 Intel Corporation. All rights reserved. Intel, the Intel logo, Xeon, Xeon inside, and Intel Intelligent Power Node Manager are trademarks of Intel Corporation in the U.S. and other countries. *Other names and brands may be claimed as the property of others.