Building a Dev/Test environment with HP CloudSystem Enterprise

Size: px
Start display at page:

Download "Building a Dev/Test environment with HP CloudSystem Enterprise"

Transcription

1 Technical white paper Building a Dev/Test environment with HP CloudSystem Enterprise Reference implementation Table of contents Executive summary... 3 Assumptions... 4 Overview... 4 Definitions... 9 Prerequisites... 9 Distribution file Application and ZIP packages System configuration HP CloudSystem Enterprise components Networking VMware vcenter HP Cloud Services HP CloudSystem Matrix Operating Environment HP infrastructure orchestration templates HP Server Automation HP Operations Orchestration HP Cloud Service Automation Resource providers Import and configure the service designs Create and publish the service offering Application Build Server deployment QA Run server deployment private cloud Developer Workstation deployment Developer code change QA Run server deployment public cloud Tear down Summary... 24

2 Appendix A Creating a Red Hat Enterprise Linux 6.2 VMware template Set up eth0 networking IPv Install VMware Tools on Linux Install the HP Server Automation agent Red Hat Enterprise Linux 6.2 kickstart file Appendix B HP Matrix infrastructure orchestration template Appendix C HP_DevTest_in_Hybrid_Cloud-1.0.zip Appendix D Resource offerings Appendix E Service designs Appendix F Creating an HP Server Automation software policy Downloading the required software packages Importing software and creating HP Server Automation policies Appendix G Software policies Appendix H Troubleshooting Appendix I Importing HP Operations Orchestration Content For more information... 42

3 Executive summary 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. HP CloudSystem delivers broad application support and helps businesses package, provision and manage cloud services to users regardless of where those services are sourced, whether from HP CloudSystem s on-premises resources or from external clouds. Automated management capabilities help ensure that performance, compliance and cost targets are met by allocating private and public cloud resources based on a client s pre-defined business policies. As a result, clients can create and deliver new services in minutes. Based on proven, market leading HP Cloud Service Automation and Converged Infrastructure, HP CloudSystem is tailored to meet 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 customers provision infrastructure and applications in minutes across private, public, and hybrid clouds. Full-scale deployment of private and hybrid cloud environments with HP CloudSystem Enterprise, which adds 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. To demonstrate a Dev/Test environment, this implementation will show how to develop and test an e-commerce web application. We will start out with the default storefront and then use HP CloudSystem Enterprise to implement a new lookand-feel and then add products to emulate a real e-commerce website. Finally, test servers will be deployed to show how testers could do Quality Assurance (QA) runs to verify the application is ready to be moved into production. The implementation described in this document details the steps needed to set up HP CloudSystem Enterprise for deploying a Hybrid Dev/Test cloud. An application build server will be deployed which will contain a Subversion source-code repository server and a Jenkins continuous integration build server. A development server will be deployed with the necessary tools to modify and commit code changes. And finally, QA deployments will be deployed into the private or public cloud to verify that the latest version of code meets appropriate standards. To emulate code changes, an open-source e-commerce tool, Magento, will be used to demonstrate how code modifications are propagated through the Dev/Test environment. A Dev/Test data flow, as shown in Figure 1, demonstrates that after an Application Build Server has been instantiated, Developers can make code changes and commit them to the Subversion code repository. At some pre-determined time, the Jenkins server creates a build with the latest code from the code repository. QA runs can be deployed at any time, picking specific builds from the Jenkins server to use as the test data. This implementation does not include feedback loops that include defect submittal/resolution or deployments to staging/production environments, more commonly known as a Dev/Ops (Development/Operations) solution. Figure 1. Dev/Test Environment HP Cloud Service Automation (CSA) is used as the deployment trigger point, HP Matrix Operating Environment (Matrix OE) is used as the service broker, and VMware vcenter and HP Cloud Services (HPCS) will provide compute resources when deploying this implementation. Magento was chosen as a sample application because it is an open-source application, has command-line installation and configuration capabilities, and is used by many well-known companies for e-commerce (magentocommerce.com). 3

4 Target audience: The target audience for this implementation is enterprise and service provider personnel who want to understand the capability, flexibility, and features of Dev/Test deployments into the hybrid cloud utilizing HP CloudSystem Enterprise. This implementation describes testing performed in May Assumptions This implementation assumes that the reader has a general understanding of the HP CloudSystem Enterprise environment and is capable of creating and deploying custom services, is comfortable with CentOS 6 and Red Hat Enterprise Linux (RHEL) 6 distributions, and able to administer these environments. The reader should have basic knowledge about HP CloudSystem Enterprise components including HP Matrix Operating Environment, HP Cloud Service Automation, HP Operations Orchestration Studio and HP Server Automation. While knowledge about Apache Web Server, MySQL, Jenkins, Ant, Subversion, and Magento are not required per se, a working understanding of these technologies will be helpful for debugging any problems that may arise. Security in any production environment is extremely important, especially in a cloud environment. However, the focus of this document is to understand the fundamentals of deploying a Dev/Test environment, not the multiple security aspects that could significantly expand the focus of this implementation. Basic security, credentials and security keys, are touched upon but the reader is advised to seek other sources for details for security recommendations. Error handling, like security, is another important topic in any public deployment. This implementation does not implement error handling in order to focus on the solution, rather than protect from the variety of failure modes. A production implementation should implement error handling to ensure a robust solution. In a real production environment, one would use the same deployment operating system (OS) for all instances to minimize possible problems. For this implementation, we violate this principle to demonstrate that it is possible to use different OS versions and solutions. Overview Today many real-world Dev/Test solutions use a source code revisioning system, a continuous integration build server, and a farm of server hardware to give developers and testers the resources needed to develop and test an application. This implementation shows how HP CloudSystem Enterprise can be used to deploy the developer components into a private cloud and then the testing components into either the private or public cloud. This flexibility provides compute resources on an as-needed basis and more importantly, the ability to release these resources when they are no longer needed. Magento (open-source e-commerce solution) is used as the main application in this example. Minor changes were made to the solution code to demonstrate a real-world Dev/Test use case. By leveraging HP CloudSystem Enterprise you can create the application framework once and simply deploy QA test runs with a single mouse-click. In this implementation, developer resources are set up in the private cloud while QA test runs can utilize compute resources in either your private or a public cloud the framework takes care of adding additional resources while your developers and testers receive the benefit of not having to worry about resource allocation or making sure that they have the latest tools and application code to do their respective tasks. Table 1 lists the main components used by HP CloudSystem Enterprise to deploy the Dev/Test hybrid cloud solution. Table 1. HP CloudSystem Enterprise components Component HP Cloud Service Automation HP Operations Orchestration What does it do? HP CSA is the manager that tells the other components what to do and when to do it as part of the cloud solution deployment process. This is where the logical cloud solution is specified and then through the customer portal, cloud solutions can be deployed by a click of the button. HP OO is the primary execution engine for HP Cloud Service Automation. It has a collection of workflows instructions or actions that perform operations such as initiating API calls to other tools or scripts on individual servers. Inside HP Cloud Service Automation, HP Operations Orchestration workflows are specified as the actions to take during a cloud deployment. 4

5 Component HP Matrix Operating Environment HP Server Automation HP BladeSystem What does it do? HP Matrix OE is the service broker that requests the compute, storage, and networking resources from the various infrastructure providers, such as vcenter or HP Cloud Services. During deployment and bursting, HP Cloud Service Automation asks HP Matrix OE to obtain additional compute resources. HP Matrix OE is also used to design the compute, storage, and networking layout of the cloud solution. HP SA provides a mechanism to deploy applications to servers that are up and running. HP Server Automation can also deploy the operating system; however, this functionality is not used in this implementation. HP BladeSystem provides the foundation of a self-aware and intelligent converged infrastructure. Architected for any workload from client to cloud, its modular, future-proof design takes advantage of proven innovations like HP Virtual Connect, Intelligent Infrastructure, and Insight Management. An HP BladeSystem comprised of HP ProLiant Gen8 blade servers provides the physical compute resources for HP CloudSystem Enterprise. For this implementation, we assume that VMware ESXi 5.0 has been installed on at least two of the blades and all private cloud compute resources will be VMware ESXi VM instances. Table 2 defines the set of Dev/Test components used in this implementation. See the For more information section at the end of this document for links to the respective components. Table 2. Dev/Test components Component Red Hat Enterprise Linux (RHEL) CentOS Subversion Jenkins Ant Apache httpd MySQL PHP Magento What does it do? Linux distribution used in the private cloud instances Linux distribution used in the public cloud instances Source-code revision control system Continuous integration build system Application build tool Web Server Database Hypertext preprocessor. General purpose scripting language especially suited for Web development and can be embedded into HTML Open-source e-commerce solution Users will be able to use HP Cloud Service Automation to launch the Application Build Server (which houses the Subversion and Jenkins servers), as shown in the dataflow in Figure 2, and any number of Developer workstations into the private cloud, as shown in Figure 3. Figures 2 and 3 show the primary components used in HP CloudSystem Enterprise and the order they are used during an application build server and developer workstation deployment. 5

6 Figure 2. Application Build Server deployment data flow Figure 3. Developer Workstation deployment data flow After a developer has made appropriate code changes and checks the changes into the Subversion source-code repository, the Jenkins build server can be told to run a new build manually, or wait until the next scheduled build completes automatically. Once the build is complete, developers or QA testers may want to test the most recent code changes. Users can use HP Cloud Service Automation to launch either single or 2-tier QA solutions into either the private or public cloud, specifying which Jenkins build they wish to test against. A single-tier solution would be used to quickly test the code functionality and a two-tier solution would be used to test a scenario that mimics a real-life production environment. 6

7 As shown in Figure 4, a single-tier solution would deploy the latest Magento code and product data from the Jenkins server on top of a Linux-Apache-MySQL-PHP (LAMP) stack. After the deployment has completed, the organization would perform appropriate testing to verify the code is ready to be delivered to production. Figure 4. Single-Tier QA deployment dataflow Figure 5 shows a two-tier public cloud deployment, allowing for a testing configuration that is closer to a production deployment. Figure 5. Two-Tier QA Deployment In the current implementation, two-tier deployments can be directed to the public cloud. The individual virtual machine instances, or tiers, cannot be split between private and public cloud boundaries. It is technically possible to do so and setup instructions are shown in the Bursting with HP CloudSystem Enterprise document if you wish to add that functionality. 7

8 When a user launches an HP Cloud Service Automation subscription through the HP Cloud Service Automation consumer portal, HP Cloud Service Automation will use an HP Operations Orchestration workflow to instruct HP Matrix Operating Environment to deploy the infrastructure components, as shown in Figure 6. Figure 6. HP Cloud Service Automation using HP Matrix Operating Environment as a compute provider to deploy virtual machines. After the VMs have been instantiated, HP Cloud Service Automation will use additional HP Operations Orchestration workflows to instruct HP Server Automation to deploy software policies onto the VM as shown in Figure 7. HP Server Automation software policies contain the packages and scripts to deploy application components. When deploying onto a remote HP Cloud Services instance, HP Cloud Service Automation will first use a separate HP Operations Orchestration workflow to deploy the HP Server Automation agent onto the remote instance. This agent is the hook that allows HP Server Automation to manage servers in both the private and public cloud. Since it was deployed to the vcenter VM template, we do not have to manually add the agent to VMs in the private cloud. Figure 7. HP Cloud Service Automation using HP Operations Orchestration and HP Server Automation to deploy software policies and agents. 8

9 After the software policies have been deployed, HP Cloud Service Automation will then utilize HP Operations Orchestration workflows to configure the application, as shown in Figure 8. These workflows will execute configuration scripts that were placed onto the respective VM instances when the software policies were deployed. These configuration scripts are specific to the respective tools (such as Apache, Subversion, Jenkins, and MySQL) that were deployed as well as configuring the Magento e-commerce application. If a different application is to be used than Magento, then a different configuration script would need to be created to allow for an automated installation and configuration process. Figure 8. HP Cloud Service Automation using HP Operations Orchestration to configure the tools on the VM instances. Definitions This section defines the cloud computing terms used in this implementation. Table 3. Term definitions Term Bursting Dev/Test Cloud Private Cloud Public Cloud Hybrid Cloud Deployment Definition Augmenting private cloud resources with resources from a different private or public cloud. Development and Testing resources and processes used to create and validate an application before releasing it into production. A collection of compute, storage, and network resources that are offered and accessed as services. Additional resources can be added or removed as needed. Cloud behind an organization s firewall and owned/controlled by a single organization. Cloud offered by a third party, such as HP, for other organizations to use. Generally available via the public Internet or outside of an organization s firewall. Combination of private and public clouds used together. The process of instantiating new cloud services, deploying an operating system (OS) onto the compute resources, setting up middle-ware applications (such as databases, application servers, or load balancers) and then deploying some set of end-user applications that are effectively the core of the web offering. Prerequisites To implement the solution described in this document, your HP CloudSystem Enterprise environment should already be installed, configured, and functioning correctly. Each component must be verified to work individually and as a complete HP CloudSystem Enterprise environment. Links to the documentation for installing, configuring, and verifying these components and their interoperability can be found in the For more information section at the end of this document. Upgrade the HP CloudSystem Enterprise components as necessary to the component versions as shown in Table 4 in the HP CloudSystem Enterprise components section. 9

10 You will need a copy of the Cloud bursting with HP CloudSystem Matrix infrastructure orchestration: Matrix-to-Matrix, HP Matrix KVM Private Cloud, HP Cloud Services, and Amazon EC2 white paper, which can be found under the white papers section at hp.com/go/matrixoe/docs. Specific networking ports will need to be open between the HP CloudSystem Enterprise environment and the public Internet. These ports and the IP ranges are listed below in the Networking section. An HP Cloud Services account, from hpcloud.com, is required for bursting into the HP Cloud Services public cloud. Distribution file Download the HP_DevTest_in_Hybrid_Cloud-1.0.zip file from the HP website at and unpack the contents to a temporary location that is available to the HP Matrix OE environment. This distribution includes scripts and resource files that will be used in the system configuration. See Appendix C HP_DevTest_in_Hybrid_Cloud-1.0.zip for a list of the distribution contents and a description of each file. Application and ZIP packages Locate the Apache Web Services, PHP, MySQL, Jenkins, Ant, and Subversion packages as specified in Appendix G Software policies and make them available to the HP Matrix OE environment. These packages may exist on a local repository, the original OS media, or from the Red Hat Network. If not, then you will need to do Internet searches to download respective packages. See Appendix G Software policies for details. System configuration Before we can use HP CloudSystem Enterprise to deploy the Dev/Test components into a Hybrid cloud, there are several configuration requirements for your environment. This section will detail these requirements and specify how to configure your HP CloudSystem Enterprise system so it is ready to deploy the Dev/Test example. HP CloudSystem Enterprise components The HP CloudSystem Enterprise solution is comprised of many integrated parts. The versions of these components used during the development of this implementation are shown in Table 4. Table 4. HP CloudSystem Enterprise components. Component Management Server HP Blade Servers Storage Networking Version HP ProLiant DL360p Gen8 HP ProLiant BL460c Gen8 HP 3PAR StoreServ Storage, HP StoreFabric Switches HP 5820 Switch Series HP Onboard Administrator 3.71 HP Virtual Connect Manager 3.75 HP Integrated Lights-Out 1.20 (ilo 4) HP Matrix Operating Environment 7.2 HP Server Automation 9.14 HP Operations Orchestration 9.05 HP Cloud Service Automation 3.10 Virtualization Manager VMware vcenter Server

11 Network pool requirements For the private cloud environment, separate production and management networks are required to separate internal maintenance traffic from external production traffic. The production network must also be able to connect to the public Internet. As listed in Table 5, the Name in service template values can be different for your environment but you will need to make appropriate changes in your HP infrastructure orchestration templates to reflect these network names. Table 5. Network pool requirements Network name Name in service template Notes Production network PROD_A Production network for communication between the load balancer, web server, and the database server in the private cloud. This network also has connectivity to and from the public Internet. Management network MGMT_A The deployment network used to install the OS and software policies using HP Server Automation in the private cloud. Upon deployment, each server will obtain its networking information via DHCP; verify that there are enough free DHCP addresses on both the management and production networks to cover the number of systems you plan on deploying. For the initial deployment there will be a single system the Application Build Server. As Developer Workstation and Testing QA servers are added to the private cloud additional IP addresses will be required. Storage requirements A VMware datastore must be available for virtual machine provisioning. 100GB gives a fair amount of leeway to expand disk usage for individual VMs in the local private cloud. If you plan to deploy primarily into your local private cloud, then adjust the VM datastore size accordingly. For this implementation we have set the individual VM disk size to be 10GB. Table 6. Storage requirements Description Total # LUNs Size Redundant paths to storage Disk is bootable VM datastore N/A 100 GB Yes No Server pool requirements The table below lists the minimum requirements for virtual servers. These values are specified in the HP infrastructure orchestration templates and may be adjusted for your environment. Two different HP infrastructure orchestration templates were created and are included in the distribution file. Instructions are included below on how to load the templates into HP infrastructure orchestration. The vcenterrhel template was used to deploy VM instances into the local private cloud and the vm-hpcs template was used to deploy VM instances into the HP Cloud Services public cloud. Table 7. Server pool requirements Server Group name Minimum CPU frequency Minimum CPU cores Minimum memory vcenter 1.0 GHz 2 cores 512 MB HPCS 1.0 GHz 2 cores 512 MB 11

12 Networking The following ports (Table 8) need to be open in your firewall to allow communication between HP CloudSystem Enterprise, the private cloud, and the HP Cloud Services public cloud instances. HP CloudSystem Enterprise requires permissions to communicate with HP Cloud Services over these ports in order to enable deployment into the public cloud. For additional security you may wish to restrict the traffic to a set of destination IP addresses. HP Cloud Services publishes the range of IP addresses that can be assigned to a public VM instance. HP Cloud Services uses /16 as the range of available public IP addresses. The network protocol for all ports listed in Table 8 is TCP. Table 8. HP Cloud Services firewall ports Source Destination Port Description SA/OO/CSA HPCS instance 22 SSH SA HPCS instance 1002 SA core manage target SA HPCS instance 1023 SA core deploy policy HP IO/HP Matrix OE HPCS identity HPCS/OpenStack HPCS Instance SA 3001 SA client registration HPCS instance Private DB instance 3306 MySQL End user (Internet) Apache Web Server 80 Application (HTTP) VMware vcenter This implementation uses VMware vcenter v5.0. A Red Hat Enterprise Linux (RHEL) 6.2 x64 VM template using only the Core and Base packages must be created. See Appendix A Creating a Red Hat Enterprise Linux 6.2 VMware template for details. HP Cloud Services See hpcloud.com for details on acquiring an HP Cloud Services account if you have not already done so. To configure HP Cloud Services, complete the following steps: 1. Access your HP Cloud Services account at 2. Determine which HP Cloud Compute region and zone you wish to deploy servers. At the writing of this implementation, there are numerous regions and zones to pick from. The US West Availability Zone 1 compute region will be used in this implementation. 3. Click on the API Keys menu item at the top of the page. Note the Access Key ID, the Secret Key (you have to click on the Show Secret Key link to make it visible), Tenant ID, and Service Endpoints Identity URL. These values will be needed when configuring HP Matrix OE. If an Access Key does not exist, click on the Manage Keys button and then the + New Key button to create an Access Key. 4. Click on the Dashboard Compute menu item and then the Manage button for the Availability Zone 1. Here we are going to create a private/public key pair. The private key will be used to access the servers that are deployed in HP Cloud Services. a. Click on the Key Pairs button and then the + Add Key Pair button. b. Supply a Key Name value (such as hpcsaccess) and then click Create Key. You can supply your own public key if you choose, see the HP Cloud Services documentation ( for details. c. An RSA private key will be shown. Copy the contents to a file on your local system and save the file as <key name>.key. When you leave this page, the private key will be gone and irretrievable from HP Cloud Services. If you lose the private key, you will not be able to access the servers that have been created with this key pair. d. This.key file will need to be copied into the /Keys directory on the HP Server Automation server and into the C:\Keys directory on the HP Operations Orchestration server. In order to communicate with HP Cloud Services VM instances using SSH, the.key file will need to be available to both servers. 12

13 HP CloudSystem Matrix Operating Environment The Cloud bursting with HP CloudSystem Matrix infrastructure orchestration: Matrix-to-Matrix, HP Matrix KVM Private Cloud, HP Cloud Services, and Amazon EC2 white paper, which can be found under the white papers section at hp.com/go/matrixoe/docs, provides instructions on how to enable the HP Cloud Services compute provider in an HP CloudSystem Enterprise environment. HP infrastructure orchestration templates For this implementation, two different HP infrastructure orchestration templates specify the networking, server, and storage requirements for the VM instances that make up the Dev/Test hybrid cloud solution. One template is used to deploy instances into the private cloud. The other template is used to deploy into the HP Cloud Services public cloud environment. If you are unfamiliar with the steps needed to import an HP infrastructure orchestration template, see Appendix B Matrix infrastructure orchestration template for step-by-step instructions for creating new templates and importing existing templates. The two HP infrastructure orchestration templates used in this implementation are included in the HP_DevTest_in_Hybrid_Cloud-1.0.zip package in the HP IO Templates folder. You will most likely need to modify both of the templates to configure the networking components so they match your production, management, and HP Cloud Services networking setup. You may need to modify the software components to match software template names in your environment, as well as any changes made to HP Cloud Services software components. After importing the templates, the Validation Status may be marked with a red X, which indicates that there are errors with the template and you need to modify the parameters to match those that work in your environment. Each HP infrastructure orchestration template will have a set of common attributes, as listed in Table 9. Table 9. HP infrastructure orchestration template common attributes Attribute Server Type Value Virtual Number of Servers Initial: 1 Maximum: 4 Processors per Server Initial: 1 Maximum: 2 Memory Size Network Assignment Type Initial: 512MB Maximum: 1024MB Automatic The attributes listed in Table 10 are the values used in this implementation for each of the respective HP infrastructure orchestration templates. You can use the templates found in the HP_DevTest_in_Hybrid_Cloud-1.0.zip package as a starting guide, but expect to modify the networking names and software templates to match your environment and any changes that occur in the HP Cloud Services software list. Note that the # in the Hostname column will be replaced by values supplied by HP CloudSystem Enterprise during deployment. If you change the template names, then you will also need to modify the corresponding TEMPLATENAME values in the HP Cloud Service Automation service designs. Table 10. HP infrastructure orchestration template requirements Template Name Network Software Group Name Hostname Disk Cloud vcenterrhel Prod, Mgmt RH62x64_Template vcenter lx-# 10GB No vm-hpcs az-1.region-a.geo-1 CentOS 6.2 Server 64-bit HPCS hp-tc-# 10GB Yes For the HP Cloud Services template, we also needed to configure the firewall settings (the templates in the distribution file already have the proper firewall settings). During deployment, HP CloudSystem Enterprise will create a security group and populate it with these firewall settings. The new security group is then assigned to the deployed VM instance for the life of the instance. Table 11 lists the firewall settings that were set for the vm-hpcs template. Figure 9 shows a screen shot of the firewall configuration dialog. 13

14 Note In the Configure Server Group popup window, the Firewall tab will be disabled unless Require In Cloud is enabled in the Config tab. Figure 9. HP infrastructure orchestration Template Firewall configuration dialog Table 11. HP infrastructure orchestration template inbound firewall settings Protocol Port IP Sources TCP /0 TCP /0 TCP /0 TCP /0 TCP /0 TCP /0 TCP /0 HP Server Automation Networking The HP Server Automation server must be configured with two NICs in order to access both the management and production networks. On the HP Server Automation server, verify that dhcpdtool (located in /opt/opsware/dhcpd/sbin) has been used to configure DHCP for both the management and production networks. The production network must have a DNS resolver capable of resolving Internet hostnames to enable communication with remote VM instances. Such a resolver is also required to configure HP Cloud instances so they are aware of the Jenkins or Subversion server s public IP address. Without the ability to connect to the public Internet, the scripts on the Developer Workstation or QA Test Run servers that determine the respective server s public (NAT) IP address will fail. Script files The HP Server Automation server will need to have the copyandinstallagent.sh file deployed in the /usr/local/sacomm directory on the HP Server Automation server. This script file can be found in the HP_DevTest_in_Hybrid_Cloud-1.0.zip package in the HP Server Automation folder. This script is used to deploy the HP Server Automation agent onto the CentOS instances created in the public HP Cloud Services cloud environment and is used by HP CloudSystem Enterprise to manage the remote agent and download software packages. 14

15 1. Login to HP Server Automation server: mkdir p /usr/local/sacomm 2. Copy the copyandinstallagent.sh file to /usr/local/sacomm (using a tool like scp). chmod +x /usr/local/sacomm/copyandinstallagent.sh Private keys Access to public deployed VMs is controlled by SSH keys, and these keys need to be added to the HP Server Automation environment to allow management of the remote VMs. For the purposes of this example these keys are stored in the /Keys directory. You may create an alternate location; however, if you use a different directory, change the KEYPAIRPATHSA property in the HP Cloud Service Automation service designs. 1. Create a /Keys directory on the HP Server Automation server. 2. Copy the private key files for HP Cloud Services to the /Keys directory on the HP Server Automation server. Software policies There are numerous software policies that need to be created in HP Server Automation. Primarily, these software policies contain (Red Hat Package Manager) and ZIP packages that will need to be loaded into HP Server Automation so that the software applications can be installed onto the VM instances after they have been deployed into the private or public clouds. The packages may already be installed on a local repository, available on the original distribution OS media, or available to you on the Red Hat Network (RHN). If you do not have access to these packages, you will need to download them from the Internet, see Appendix G Software policies for instructions. Appendix F Creating an HP Server Automation software policy details how to create a software policy if you are unfamiliar with the steps. Note When importing items into HP Server Automation and creating software policies, make sure that the items are stored in the /Package Repository/All Red Hat Linux/Red Hat Enterprise Linux Server 6 X86_64 folder and that both the CentOS 6 X86_64 and Red Hat Enterprise Linux 6 X86_64 OSs are selected. HP Server Automation will show this as Some Linux. HP Operations Orchestration HP Operations Orchestration is a workflow engine that is used by HP Cloud Service Automation to execute custom tasks, allowing HP Cloud Service Automation to take advantage of content that was developed after a development release. If you are unfamiliar with HP Operations Orchestration, see the product page hp.com/go/oo. For this implementation, make sure you are working with the full HP Operations Orchestration software that was deployed as part of HP Cloud Service Automation. Networking The HP Operations Orchestration server requires access to both the management and production networks. Private keys SSH key pairs were created when you set up the HP Cloud Services account. These keys now need to be copied to the HP Operations Orchestration server in your HP CloudSystem Enterprise environment. When certain workflows are executed, if they are operating on a remote instance that was created in the public cloud, they will use SSH to invoke commands on the remote VM. The private key is required for SSH access. Without it, SSH communication, and setup operations, will fail when HP CloudSystem Enterprise tries to deploy application software to the remote VM. To configure private keys, complete the following steps: 1. Create a C:\Keys folder on the HP Operations Orchestration server. You can create and configure a different folder in the HP Cloud Service Automation service design, but this implementation assumes that private keys are stored in C:\Keys. 2. Copy the hpcsaccess.key file for HP Cloud Services and store it in the C:\Keys folder on the HP Operations Orchestration server. 15

16 Content Patch Some environments may require Hotfix #157291, which addresses issues seen when using Matrix Operating Environment and HP Server Automation together. Please contact your Hewlett-Packard support representative to determine if this patch should be applied to your HP Cloud Service Automation content. Workflows HP Operations Orchestration workflows are the equivalent of an application tool that has been programmed to complete a very specific task. Workflows by themselves are a collection of tasks that when combined together, perform some operation that does useful work from start to finish. Through these workflows, HP Cloud Service Automation can act as the glue between the various components in HP CloudSystem Enterprise and automate tasks that would normally fall upon an individual to perform manually. For this implementation, workflows were created that would configure Jenkins and Subversion, install Magento, add a new presentation theme to Magento, install the HP Server Automation agent on a public cloud virtual machine instance, tell HP Server Automation to deploy a software policy, and download a Jenkins build from the Jenkins server and deploy it onto a local server. Import the workflows The distribution file contains the HP Operations Orchestration workflows jar file, in the oo-flows folder, required to implement the service design and run the appropriate workflows. Make sure the Dev-Test-Hybrid-Cloud- ContentInstaller.jar file is accessible from the HP Operations Orchestration server in your HP CloudSystem Enterprise environment. To make these workflows available to HP Cloud Service Automation, you must first import them into the HP Operations Orchestration repository. To import the workflows, complete the following steps on the HP Operations Orchestration server: 1. Open a command line window. 2. Change folders to the location containing the jar file. 3. Enter the following command: java Xmx1024m jar Dev-Test-Hybrid-Cloud-ContentInstaller.jar centralusername <admin_user> -centralpassword <password> 4. Upon completion, the workflows are automatically imported into HP Operations Orchestration in the /Library/CSL/Contrib/CSA3.1/DevTest in Hybrid Cloud folder. Verify that the folder structure shown in Figure 10 has been created in the HP Operations Orchestration library: Figure 10. DevTest in Hybrid Cloud HP Operations Orchestration workflows 16

17 Run process definition tool A process definition tool is set up during installation and configuration of HP Cloud Service Automation. This tool ensures that HP Cloud Service Automation can correctly locate the HP Operations Orchestration workflows needed by the HP Cloud Service Automation Service Offerings. These steps assume that the HPOOInfoInput.xml file is used to define the content available to HP Cloud Service Automation. To run the process definition tool, complete the following steps: 1. Open the following file in a text editor: %ProgramFiles%\Hewlett- Packard\CSA\Tools\ProcessDefinitionTool\HPOOInfoInput.xml. 2. Manually add the following lines at the end of the file, inside the </ooengine></ooengines> XML tags: <folder update="true" flow="false" path="/library/csl/contrib/csa3.1/devtest in Hybrid Cloud" recursive="true"/> 3. Run the following command from the process definition folder: a. For Oracle : java -Done-jar.class.path=ojdbc6.jar -jar process-defn-tool.jar -d db.properties -i HPOOInfoInput.xml b. For Microsoft SQL Server: java jar process-defn-tool.jar d db.properites i HPOOInfoInput.xml This last step makes the imported HP Operations Orchestration workflows available to HP Cloud Service Automation and can take several minutes to complete. When done, the tool should report that the process definitions were created. The db.properties file should have been created when HP Cloud Service Automation was installed and the original content was loaded. System Accounts The credentials for two system accounts need to be set up in HP Operations Orchestration Studio. SASSH will contain the credentials for the root user on the HP Server Automation server that can execute SSH scripts. vcenterrh will contain the credentials for the root user on the instantiated VMs that are created inside vcenter. These credentials are required to allow the workflows to execute scripts on the remote VM. These accounts should have already been created when importing the HP Operations Orchestration workflows, but you will need to modify the credentials to match your system. To modify a system account, follow these instructions: 1. Launch HP Operations Orchestration Studio at ( or launch the tool from the Windows Start menu at All Programs Hewlett-Packard Operations Orchestration HP Operations Orchestration Studio. 2. Navigate to Configuration System Accounts. 3. Double-click the system account (either SASSH or vcenterrh). 4. Click on the Check-Out icon to unlock the account. 5. Click on Assign Password and enter the appropriate password for SASSH or vcenterrh. 6. Click the Save icon and then the Check-In icon to add a new version in the repository. 7. Click the OK button in the Check In window to commit the changes. HP Cloud Service Automation HP Cloud Service Automation and HP CloudSystem Enterprise really provide value with their ability to automate the entire deployment process reduce the entire infrastructure, platform (tools), and application deployment down to a single click. HP Cloud Service Automation acts as the glue for all of the other HP CloudSystem Enterprise components allowing you to set up an infrastructure once and deploy it multiple times. For example, you can create one infrastructure for different groups in your organization or set up and tear down an infrastructure easily for QA or development test runs. 17

18 HP Cloud Service Automation, like most technologies, has its own vocabulary. Table 12 highlights the most important terms but the reader should refer to the documentation (see For more information section) for more details and a complete list. Table 12. HP Cloud Service Automation definitions Term Catalog Resource Provider Resource Offering Service Design Service Offering Subscription Service Access Point Definition Collection of Subscriptions that a user can pick from. A management platform that provides either Infrastructure-as-a-Service (IaaS) or Software-as-a-Service (SaaS) to the cloud. For example, a provider such as HP CloudSystem Matrix deploys virtual machines, while a provider such as HP SiteScope monitors applications. A resource offering corresponds to a capability offered by a provider (or a group of providers) that can be provisioned by HP Cloud Service Automation. For example, you can create a resource offering that corresponds to a specific VMware vcenter VM template that can be cloned by HP Cloud Service Automation to create a VM. A resource offering includes a user-specified set of lifecycle actions that are executed during the provisioning of the resource offering. A resource offering can also include actions that will be exposed to a subscriber in the Cloud Subscriber Portal. A template or blueprint for an orderable service. An instance of a service design that can be selected for deployment. A deployed service offering. The URL that points to a communication handle of a resource provider that will allow HP Cloud Service Automation to communicate with the resource provider. Resource providers A resource provider is a management platform that provides either Infrastructure-as-a-Service (IaaS) or Software-as-a- Service (SaaS) to the cloud. For example, a provider such as HP CloudSystem Matrix deploys virtual machines, while a provider such as HP SiteScope monitors applications. There are three primary resource providers utilized in the service designs for this implementation; HP Matrix OE, HP Server Automation, and HP Operations Orchestration. For each resource provider, a Service Access Point (SAP) is required. We also need to specify the credentials that allow HP Cloud Service Automation to communicate with the device. In the Name column in Table 13, Matrix refers to the HP Matrix OE server and its SOAP API, SA refers to the Server Automation server and secure HTTP, and OO refers to the HP Operations Orchestration workflow engine. The names given for each resource provider are examples and you can substitute values that are appropriate for your environment. However, when you create resource offerings in a later step, you will need to use the resource provider names you specified. Some of the resource providers shown in Table 13 may have already been added in your environment. The HP Operations Orchestration provider category is not provided out of the box. This entry will be created when the related resource offerings are imported. The process is to import the resource offerings related to a resource provider and then update the Service Access Point values and credentials for these providers to match your environment. Table 13. HP Cloud Service Automation Resource Providers Resource provider type Name Service Access Point HP Matrix Operating Environment Matrix OE_IP>:51443/hpio/controller/soap/v4 HP Server Automation SA Operations Orchestration OO To define a resource provider, follow these steps: 1. Launch HP Cloud Service Automation ( and log on with appropriate credentials. 2. Make sure the resource device is up and running. 3. Select the Resource Management tab at the top of the page, then the Providers button in the left panel, and finally the By Type tab under the Providers header bar. 18

19 4. If a specific type is not present, click on the Edit Provider Types icon, and when the Edit Provider Types window comes up, click on the Create New Provider Type icon. Then supply the name using the value listed under the Resource provider type column in Table 13 and change the icon image as appropriate. Finally, click on the Create button to create a new provider type. 5. Select the appropriate provider type and then click on the Create New Provider icon. a. Supply the name and click on the Next> button. b. Supply the credentials and the service access point (from Table 13) and then click on the Create button. Import and configure the service designs Service designs are the architectural blueprints that define how a subscription should be deployed, what resource offerings should be used, and any customizable properties that should be specified for a resource offering. For this implementation, we are going to use five difference service designs, each with its own set of service offerings and properties. See Appendix E Service designs for the list of service designs used in this implementation. A list of resource offerings are shown in tables 15 and 16 in Appendix D Resource offerings to match up with the HP Operations Orchestration workflows that will be used for executing specific actions during subscription deployment. Before importing the blueprints, complete the following steps: 1. Log on to the HP Cloud Service Automation Administrator portal using an account with administrator privileges. 2. Select the Service Design tab. 3. Select Component Types on the left side menu. 4. Add Software Component as a child to Infrastructure Service. a. Select Infrastructure Server and then the Supported Children tab. b. Click on the + and then select Software Component. c. Click on the Add button and then the Close button. 5. Add Application category to Infrastructure Service. a. Select Infrastructure Server and then the Supported Categories tab. b. Click on the + and then select Application. c. Click on the Add button and then the Close button. To import the service designs, listed in tables in Appendix E Service designs, complete the following steps for each service design: 1. Log on to the HP Cloud Service Automation Administrator portal using an account with administrator privileges. 2. Select the Service Design tab and then then Service Designs button on the left. 3. Click Import Service Design. 4. Browse to the service-designs folder in the distribution file and select the service design. 5. Click Save to import the service design. Click on the service design to bring up the summary page and then click on the Designer tab to see the tree layout. 6. Select the All Service Designs button on the left. 7. For the Public QA service design, select the Designer tab, and then select the DB infrastructure service components, and then the Properties button. Change the KEYPAIRPATHOO and KEYPAIRPATHSA values to match the path of the private key values that were downloaded from HP Cloud Services. The KEYPAIRPATHOO value should not include the C: prefix and should start with the forward slash ( \ ). The KEYPAIRPATHSA value should include the absolute path starting with the back slash ( / ). 8. For the Public QA (2-tier) service design, do this for both the DB and Web infrastructure service components. Select the Designer tab, and then select the appropriate component and then the Properties button. Change the KEYPAIRPATHOO and KEYPAIRPATHSA values to match the path of the private key values that were downloaded from HP Cloud Services. The KEYPAIRPATHOO value should not include the C: prefix and should start with the forward slash ( \ ). The KEYPAIRPATHSA value should include the absolute path starting with the back slash ( / ). Each node/component in the service design tree can have a collection of resource bindings (actual resource offerings), lifecycle actions, and property values. Tables in Appendix E Service design lists the detailed settings for each node/component in the five service designs for this implementation. For these service designs, all property values are strings, even those that contain numeric values. 19

20 After importing the service designs, for each of the resource offerings listed in Table 15, verify that a valid resource provider is assigned to each resource offering. Follow the instructions in Appendix D Resource offerings to associate a resource provider with the resource offerings. An Operations Orchestration resource provider may also need to be created, depending on your environment. See Table 13 for resource provider details. Create and publish the service offering A service offering must be created in HP Cloud Service Automation before subscribers can request services based on this service design. To create the Dev/Test service offerings, complete the following steps for each of the five service designs (as listed in Tables 17-21). 1. Log on to the HP Cloud Service Automation Administrator portal using an administrator account. 2. Select the Service Offerings tab. 3. Click Create Offering in the left panel. The Create New Service Offering dialog will open. 4. Enter a name for the new service offering. This name will be visible to the subscribers of this service. Keep track of this name; you will need to supply it when deploying the service below. 5. Select the appropriate service design. 6. Click Create. 7. After the offering is created, you can modify the pricing information, associated documents, or subscriber options for this subscription, such as the default image to display for the service offering. HP Cloud Service Automation is installed with a default global catalog named Global Shared Catalog. When you publish a service offering in this global catalog, that service offering will be visible in every organization s Cloud Subscriber Portal. To publish the service offerings in the default catalog, complete the following steps for each of the five service offerings: 1. Log on to the HP Cloud Service Automation Administrator portal using an account with administrator privileges. 2. Select the Service Catalogs tab. 3. Select Global Shared Catalog in the panel on the left. 4. Select Published Offerings in the central panel. 5. Click the Add Offering button at the bottom of the page. 6. Select the service offering that was created above and click Select. 7. For Select Category, select the Application Services category. 8. Click the Add button and then the OK button. Application Build Server deployment Now, after completing the setup of the HP CloudSystem Enterprise components, it is time to start deploying the Dev/Test components. The first deployment will consist of the Application Build Server in the private cloud. This is the virtual machine server that will hold the source code revision control server (Subversion) and the continuous integration build server (Jenkins). These components are sitting on top of a LAMP deployment and an initial build of the Magento e-commerce code will be pre-loaded into Subversion and an initial build has been launched in Jenkins. The application build server is ready to support requests for deploying developer workstations or QA test servers. Other applications, such as a wiki-server, a blogging tool, a unit test infrastructure, or a defect tracking tool (for example) could also be deployed on the application build server as appropriate for a software development team. This implementation provides the framework for other tools to be added and does not explicitly limit their addition. To launch the initial deployment, complete the following steps: 1. Launch the HP Cloud Subscriber Portal at and log on using appropriate credentials. Your organization may have a specific consumer portal which should be used instead of the default consumer portal. 2. Select the Catalog tab at the top of the page. 3. In the New Releases window (on the far right), click on the name of the service offering for the Application Build Server. You could also open the Application Services category type you selected previously, find your service offering in the list and then click on Select. 4. Supply a name for your subscription and an optional description. Leave the requested start/end dates alone. 5. In the Summary window (on the far right), click Request Now. 20

21 6. You can monitor the deployment of your subscription using the HP Cloud Service Automation Service Operations view, the HP Matrix OE infrastructure orchestration Requests view, and HP Server Automation Jobs and Sessions view. The subscription should take less than 30 minutes to complete. 7. In the HP Cloud Subscriber Portal select the Subscriptions tab and find your subscription in the list. 8. The Active icon indicates that your subscription has completed and is an active private cloud. If the Failed icon is displayed, use HP Matrix OE, HP Server Automation, and HP Operations Orchestration tools to determine the root cause. The subscriptions page refreshes itself periodically so manually refresh the screen to see updated status results. 9. Click on the View Details button for the build server subscription and scroll down to the bottom to find the IP addresses assigned to the build server. You may want to record the production IP address, as shown in Figure 11, because you will need it for testing the deployment and later when deploying developer workstations and QA run servers. Figure 11. Application Build Server Management/Production IP Addresses 10. If you will be deploying QA servers into the public cloud, you will also need to know the public IP address of the application build server. If the server has an IP address that undergoes Network Address Translation (NAT), then the actual public IP address can be found by logging into the application build server and executing curl The results should include the IP address for the application build server that is seen in the Internet. If the public address is not subject to NAT, then just supply its public IP address. 11. Verify that the server was deployed correctly and the Subversion and Jenkins services are running properly. a. Verify that Jenkins is up and running by going to the URL. b. Verify that Magento was loaded into Subversion and the first build was success by going to the URL. QA Run server deployment private cloud At this point, we can launch a QA Run to verify that the test process is working correctly. This will also allow us to see a before and after picture to verify a developer code change in a later step. Automated test tools and tests could easily be added to the framework to further automate the process for an individual organization. This step will focus on deploying a QA run single-tier server into the private cloud. To launch the initial deployment, complete the following steps: 1. Launch the HP Cloud Consumer Portal at and log on using appropriate credentials. Your organization may have a specific consumer portal which should be used instead of the default consumer portal. 2. Select the Catalog tab at the top of the page. 3. In the New Releases window (on the far right), click on the name of the service offering for the VMware QA Run. You could also open the Featured Services category type you selected previously, find your service offering in the list and then click on Select. 4. Supply a name for your subscription and an optional description. Leave the requested start/end dates alone. 5. Supply the production IP address for the Jenkins server and the latest successful build number. You can get the latest successful build by going to the URL and looking at the Build History. Since the Jenkins build server is configured to run a build every day, pick the latest build number to ensure that the artifacts are available. 6. In the Summary window (on the far right), click Request Now. 21

22 7. You can monitor the deployment of your subscription using the HP Cloud Service Automation Server Operations view, the HP Matrix OE infrastructure orchestration Requests view, and HP Server Automation Jobs and Sessions view. The subscription should take less than 30 minutes to complete. 8. In the HP Cloud Subscriber Portal select the Subscriptions tab and find your subscription in the list. 9. The Active icon indicates that your subscription has completed and is an active private cloud. If the Failed icon is displayed, use HP Matrix OE, HP Server Automation, and HP Operations Orchestration tools to determine the root cause. The subscriptions page refreshes itself periodically so manually refresh the screen to see updated status results. 10. Click on the View Details button for the QA run subscription and scroll down to the bottom to find the IP addresses assigned to the QA run server. Use the production IP address to verify that the Magento code has been installed: Developer Workstation deployment Now we can launch a Developer Workstation server for a developer who will be making storefront presentation (the lookand-feel of the website) and product changes to the Magento code and database. While this example will only show deploying a single server, in reality servers could be created for each individual developer and used for the duration of a project, or created to develop a specific task and then torn down when the developer had completed the task. After the VM instance is created, the latest version of the code base will be extracted from the Subversion server and deployed to the developer workstation. The developer can then go make code/product changes and then commit those changes back to the Subversion server. To launch the initial deployment, complete the following steps: 1. Launch the HP Cloud Consumer Portal at and log on using appropriate credentials. Your organization may have a specific consumer portal which should be used instead of the default consumer portal. 2. Select the Catalog tab at the top of the page. 3. In the New Releases window (on the far right), click on the name of the service offering for the Developer workstation. You could also open the Featured Services category type you selected previously, find your service offering in the list and then click on Select. 4. Supply a name for your subscription and an optional description. Leave the requested start/end dates alone. 5. Supply the production IP address for the Subversion server (the application build server). 6. In the Summary window (on the far right), click Request Now. 7. You can monitor the deployment of your subscription using the HP Cloud Service Automation Server Operations view, the HP Matrix OE infrastructure orchestration Requests view, and HP Server Automation Jobs and Sessions view. The subscription should take less than 30 minutes to complete. 8. In the HP Cloud Subscriber Portal select the Subscriptions tab and find your subscription in the list. 9. The Active icon indicates that your subscription has completed and is an active private cloud. If the Failed icon is displayed, use HP Matrix OE, HP Server Automation, and HP Operations Orchestration tools to determine the root cause. The subscriptions page refreshes itself periodically so manually refresh the screen to see updated status results. 10. Click on the View Details button for the developer workstation subscription and scroll down to the bottom to find the IP addresses assigned to the developer workstation server. Use the production IP address to verify that the Magento code has been installed and matches the basic Magento output: Developer code change Normally a developer would make appropriate code changes and then check them into Subversion so they could be picked up on the next Jenkins build. For this implementation, an automated way of emulating a code change that a developer could make was created to help focus on the process and not exploring the details of actually making changes to Magento. The code changes include adding a new presentation theme and adding four products into the Magento product database. These changes are then checked into the Subversion repository so they can be picked up by the next Jenkins continuous integration build. In a real-world case, developers would be doing this kind of step continuously and automating it would be a waste of time since it would be a one-time activity. 22

23 To launch the initial deployment, complete the following steps: 1. Launch the HP Cloud Subscriber Portal at and log on using appropriate credentials. Your organization may have a specific consumer portal which should be used instead of the default consumer portal. 2. In the HP Cloud Subscriber Portal select the Subscriptions tab and find your Developer Workstation subscription in the list. 3. Click on the View Details button for the developer workstation subscription and scroll down to the Workstation Tier section. Here you will want to select the Developer Code Change Action and then click on the Request Action button, as shown in Figure 12. Figure 12. Developer Code Change Action 4. You can monitor the code change deployment of your subscription using the HP Cloud Service Automation Service Operations view. 5. Use the production IP address to verify that the Magento code has been updated and matches the output shown in Figure 13 below. Figure 13. Magento Home Page with Appliances Theme QA Run server deployment public cloud Now we can launch a QA Run to verify that the code changes are working properly and did not cause other problems. This step will focus on deploying a QA run two-tier server into the public cloud. In this case, the two-tier solution means that the database will be deployed onto one server and the Magento code and web server will be deployed on a second server. The servers in the public cloud will still download the latest build from the Jenkins server (Application Build Server) residing in the private cloud. 23

24 To launch the QA Run Server deployment in the public cloud, complete the following steps: 1. Launch the HP Cloud Subscriber Portal at and log on using appropriate credentials. Your organization may have a specific consumer portal which should be used instead of the default consumer portal. 2. Select the Catalog tab at the top of the page. 3. In the New Releases window (on the far right), click on the name of the service offering for the HPCS QA Run (2- tier). You could also open the Featured Services category type you selected previously, find your service offering in the list and then click on Select. 4. Supply a name for your subscription and an optional description. Leave the requested start/end dates alone. 5. Supply the public production IP address for the Jenkins server and the latest successful build number. You can get the latest successful build by going to the URL and looking at the Build History. Since the Jenkins build server is configured to run a build every day, pick the latest build number to ensure that the artifacts are available. Note that the public production IP address is the address seen by servers in the public Internet. You can find the public production IP value by logging into the Application Build Server and executing curl 6. In the Summary window (on the far right), click Request Now. 7. You can monitor the deployment of your subscription using the HP Cloud Service Automation Server Operations view, the HP Matrix OE infrastructure orchestration Requests view, and HP Server Automation Jobs and Sessions view. The subscription should take less than 30 minutes to complete. 8. In the HP Cloud Subscriber Portal select the Subscriptions tab and find your subscription in the list. 9. The Active icon indicates that your subscription has completed and is an active private cloud. If the Failed icon is displayed, use HP Matrix OE, HP Server Automation, and HP Operations Orchestration tools to determine the root cause. The subscriptions page refreshes itself periodically so manually refresh the screen to see updated status results. 10. Click on the View Details button for the QA run subscription and scroll down to the bottom to find the IP addresses assigned to the QA run server. Use the public IP address to verify that the Magento code has been installed and matches the appliance themed output shown in Figure 13 above. Tear down To cancel any of the subscriptions and return the private and public cloud resources, complete the steps below. Note that if you cancel the Application Build Server, you will not be able to deploy Developer Workstation or QA Run servers until another Application Build Server is created. 1. Launch the HP Cloud Subscriber Portal at and log on with appropriate credentials. 2. Select the Subscriptions tab and find your subscription in the list, then click on the corresponding View Details button. 3. In the Summary window (on the far right), click Cancel Subscription. 4. Use the HP Matrix OE, HP Server Automation, and HP Operations Orchestration tools to monitor the subscription cancellation. 5. Verify that resources have been returned by monitoring the HP Matrix OE infrastructure orchestration Requests tab. Summary This implementation documents how to configure HP CloudSystem Enterprise to deploy and tear down a Dev/Test hybrid cloud environment. HP CloudSystem Enterprise: HP Cloud Server Automation working together with HP Matrix Operating Environment, HP Server Automation, and HP Operations Orchestration to create a Dev/Test hybrid cloud environment utilizing VMware and HP Cloud Services. This guide can be used as a starting point for deploying more advanced or complex applications into a Dev/Test hybrid cloud environment and as a basis for moving code to staging and production environments. 24

25 Appendix A Creating a Red Hat Enterprise Linux 6.2 VMware template These instructions can be used for creating a Red Hat Enterprise Linux (RHEL) 6.x VMware template; specific instructions for RHEL 6.2 are listed. 1. Access the Central Management Server (CMS). a. Launch the vsphere client. b. Right-click the Datacenter and select New Virtual Machine. c. Select Typical for the configuration. d. Name: RH62x64_Template. e. Select appropriate cluster and datastore. f. Select Linux, Red Hat Enterprise 6 (64-bit). g. Select 1 NIC, Mgmt_A network, E1000 Adapter. h. Select 10GB, Thin Provision. i. Click Finish. 2. Make sure the Linux Red Hat 6.2 Enterprise CD/DVD ISO image is available and can be seen by the VM image once it is powered on. 3. Create a floppy image using the recommended kickstart file attached to the distribution or from Example See VMware Knowledge Base entry #1739 for details on creating a floppy image (edit kickstart file and create a floppy out of it): a. Name the kickstart file ks.cfg before creating the virtual floppy. The name of the floppy image is not important, but the extension must be.flp so that it is recognized by vsphere. b. Make sure the floppy image can be seen by the VM image after it is powered on. 5. On the newly created VM, enable the Force BIOS Setup option (click Edit Settings, Options tab, Boot Options). 6. Power on the VM image. 7. When the BIOS window opens, make sure to move the CD-ROM boot device to be the first item in the list. Do NOT exit out of the BIOS window yet. a. Use the mount floppy icon to mount the floppy image (containing the ks.cfg kickstart file) to the newly created VM. b. Use the mount CD/DVD icon to mount the Linux Red Hat 6.2 Enterprise CD/DVD ISO image to the newly created VM. c. After mounting both the floppy and DVD images, it is ok to Save and Exit out of the BIOS application. 8. When the RHEL 6.2 install/upgrade screen is presented, you have 60 seconds to press the Tab key to bring up a text prompt. Otherwise the manual install/upgrade process will proceed. a. At the prompt, type the following for the boot sequence: vmlinuz initrd=initrd.img ks=floppy b. The install should complete without any additional user interaction required. 9. After the VM image has been installed, unmount the CD/DVD and floppy images and reboot. In case the automatic install process has rebooted the server and launched the manual install process, just unmount the images and reboot the server again. Set up eth0 networking For Red Hat Enterprise Linux 6.x, when deploying a VMware instance from a template, the new instance retains the original MAC address and networking is effectively disabled. To resolve this issue, execute the following steps to ensure that new VMware instances have knowledge of a single networking device, eth0. 1. Log on to the newly created VM as a root user. Use the password specified in the kickstart (ks.cfg) file. 2. Remove the /etc/udev/rules.d/70-persistent-net.rules file. 3. Remove the HWADDR line in the /etc/sysconfig/network-scripts/ifcfg-eth0 file. 25

26 IPv6 Make sure IPv6 is turned off by editing /etc/sysctl.conf and adding net.ipv6.conf.all.disable_ipv6 = 1 to the end of the file. Install VMware Tools on Linux 1. In vsphere client, right-click on VM, select Guest Install/Upgrade VMware Tools. This effectively mounts a CD with the tools in a zipped tar-ball that needs to be unpacked and then installed. 2. On the VM, log in as root (using credentials specified in the kickstart file), then execute the following commands: a. cd /tmp b. mkdir /mnt/cdrom (if it doesn't already exist) c. mount /dev/cdrom /mnt/cdrom d. tar zxvf /mnt/cdrom/vmwaretools-<version>.tar.gz e. umount /dev/cdrom f. cd vmware-tools-distrib g../vmware-install.pl h. Press Enter to accept defaults for all questions. Install the HP Server Automation agent The HP Server Automation Agent must be installed on all servers to allow HP Server Automation to manage the server instance. To install the HP Server Automation agent, complete the following steps: 1. Acquire the IP address of the system where you want to install the agent (this would be the VM instance that was just created). Make sure the VM instance is running and can communicate with the HP Server Automation server on the network. The following commands may be useful: ping <SA_server> (verify that the VM can reach the HP Server Automation server) ifconfig eth0 (find the local IP address) 2. Launch the HP Server Automation Java Client (HP Server Automation icon on the desktop), pointing to the HP Server Automation server. 3. Log on using administrator credentials. 4. In the Devices tab (left navigation window), under Servers, select Unmanaged Servers. 5. In both the from and to text boxes, enter the IP address of the VM Linux system as shown in Figure Click the Scan button. Figure 14. HP Server Automation unmanaged servers scan 26

27 7. Once the system has been found, right-click the VM and select Manage Server. The Manage Servers window will be displayed as shown in Figure Enter the root credentials. 9. Make sure the Action Verify prerequisites and copy agent installer to servers is selected. We do NOT want to install the agent at this time. In the steps below we will deploy a script to install the agent on the next boot. 10. Expand the Installer Options list and deselect Start the Agent after installation. Figure 15. Manage Servers dialog options 11. Click OK to copy the agent files to the VM instance. 12. Manually extract and copy the runonce, startagent.sh, and sa_agent_prep.sh files (from the distribution file in the HP Server Automation folder) to the /tmp directory on the VM instance. 13. Log on to the VM instance and navigate to the /tmp directory. 14. Edit the sa_agent_prep.sh script and change the SA_IP value to match the IP address of your HP Server Automation server. 15. Type the following command to launch the sa_agent_prep.sh script./sa_agent_prep.sh 16. Type the following command to shut down the VM gracefully shutdown -h now 17. When the VM has powered off, use the vsphere client to convert the VM instance to a template by right-clicking on the VM instance and selecting Template Convert to Template. 18. Launch Matrix Operating Environment a. Go to Tools Infrastructure Orchestration b. Select the Software tab. c. Click the refresh icon to make sure all of the VM templates are found. d. Verify that the VMware template RHEL62x64_Template is in the list of available software. 27

28 Red Hat Enterprise Linux 6.2 kickstart file This sample kickstart file, as shown in Example 1, was used when developing this implementation. Changes may be made to accommodate individual site requirements. This kickstart file sets up a default root password of password. You can modify that at your discretion, using an encrypted value if so desired, to meet your site s security requirements. Example 1: Sample kickstart file # Default Kickstart file for # Red Hat Enterprise Linux 6.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 --device eth0 --noipv6 --onboot yes 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= asprimary --grow part swap --size=1024 rootpw password auth --useshadow --enablemd5 firewall --disabled timezone US/Pacific reboot %packages # # PRE # %pre # # POST # %post #-- Turn on snmp daemon chkconfig snmpd on %end 28

29 Appendix B HP Matrix infrastructure orchestration template HP Matrix infrastructure orchestration templates are used to specify the networking, compute, and storage resources that make up a deployed service. They can be either physical or virtual components, but in this implementation we will be dealing exclusively with virtual components. What follows are step-by-step instructions on how to import an HP infrastructure orchestration template and instructions on how to create the HP infrastructure orchestration template used to deploy an Apache Web Server. Creating HP infrastructure orchestration templates are fairly straightforward but if you would like to see more examples, take a look at the LAMP and WordPress white paper at Importing HP Matrix infrastructure orchestration templates To import the HP Matrix infrastructure orchestration templates, complete the following steps: 1. Launch HP infrastructure orchestration from the browser or the Microsoft Windows Start Menu. Log on as an administrator to the HP Matrix infrastructure orchestration Designer. or use the Windows Start menu and select HP Insight Management HP Matrix infrastructure orchestration HP Matrix IO Designer. 2. Click Import and browse to the location where you unzipped the HP_DevTest_in_Hybrid_Cloud-1.0.zip package. The templates are found in the HP IO Templates folder. Select the appropriate template. 3. You will most likely 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. 5. At this point, the networking and software values will need to be modified to match those found in your environment. The software templates hosted by the HP Cloud Services website may also have to be changed and you may need to find the software image that will work for your requirements. a. To change your networking values, double-click on the network component in your template diagram to bring up the Configure Network window. Under the Config tab, select the appropriate network and then click on the OK button. b. To change the software, double-click on the virtual server group component in your template diagram to bring up the Configure Server Group window. Under the Software tab, make sure that Automatic software deployment is selected and then scroll down the list to find the entry that you want to deploy on to your VM instance after it has been created. After selecting your software entry, click on the OK button. Create Apache Web Server HP infrastructure orchestration template This HP infrastructure orchestration template is included as part of the distribution package. The following instructions are intended to provide guidance in creating a new HP infrastructure orchestration template. 1. Launch HP infrastructure orchestration from the browser or the Windows Start Menu. Log on as an administrator to the HP Matrix infrastructure orchestration Designer. or use the Windows Start menu and select HP Insight Management HP Matrix infrastructure orchestration HP Matrix IO Designer. 2. Click on the New icon to start creating a new template. 3. Drag two Network components and a Virtual Server Group component from the Components panel to the workspace. A Virtual Storage component will be automatically attached to the Virtual Server Group component. 29

30 4. Connect the network components to the server component. You should have a layout similar to the one shown in Figure 16. Figure 16. Apache Web Server HP infrastructure orchestration Template 5. Double-click on the first network component. This will bring up the Configure Network window. Select the private cloud management network you wish to use and then click OK. In this implementation, this management network will be called Mgmt_A. 6. Double-click on the second network component. For this network, select the private cloud production network you wish to use, and then click OK. In this implementation, this production network will be called Prod_A. 7. Double-click on the server component. This will bring up the Configure Server Group window. a. In the Config tab, set the Group Name to be WebServer. b. In the Networks tab, set the Hostname to be web-# and the Assignment Type for both networks to be DHCP. c. In the Software tab, select the RH62x64_Template VMware software template. See Appendix A Creating a Red Hat Enterprise Linux 6.2 VMware template for instructions for creating the VMware software template. If the desired template is not visible, you may have to click the refresh make it visible. button to d. Click OK to accept the changes. Depending on which software template you selected, you may be presented with a warning window that the selected disk size needs to be modified. Acknowledge the warning and continue. 8. The Validation Status should show a green success status. If not, click on the Show Issues button and resolve any issues. 9. Enable the Published check box so that the template can be used to deploy services. 10. Click the Save As icon and enter a unique name for the HP infrastructure orchestration template. a. Optionally enter Notes about this template for future reference. b. Finally, click Save in the Saving Template As window. 11. Verify the template shows up in the list of HP IO templates in HP infrastructure orchestration. a. Launch HP Systems Insight Manager at b. Click Tools Infrastructure orchestration. c. Select the Templates tab to show the list of HP infrastructure orchestration templates. 30

31 Appendix C HP_DevTest_in_Hybrid_Cloud-1.0.zip Table 14. HP_DevTest_in_Hybrid_Cloud-1.0.zip distribution file contents Directory File Description HP IO Templates HP Server Automation vcenterrhel.xml vm-hpcs.xml copyandinstallagent.sh runonce sa_agent_prep.sh startagent.sh HP IO templates to deploy Linux VM instances using VMware vcenter and HP Cloud Services compute providers. Linux shell script used to copy the HP Server Automation agent installer file to a remote instance in the public cloud and then launch the installer and deploy the HP Server Automation agent on the remote instance. Linux shell script used when creating a RHEL 6.2 VMware Template. Linux shell script used when creating a RHEL 6.2 VMware Template. Linux shell script used when creating a RHEL 6.2 VMware Template. Kickstart ks.cfg Sample RHEL 6.2 Kickstart file. ks.flp Floppy drive image of the RHEL 6.2 Kickstart file. oo-flows Dev-Test-Hybrid-Cloud-ContentInstaller.jar HP Operations Orchestration workflows scripts AppServerFiles.zip ZIP file containing a Linux shell script to configure the Application Build Server, the Ant build script, and the Magento installation configuration file. service-designs DevCodeChangeFiles.zip DevWorkstationFiles.zip QASetupFiles.zip SERVICE_BLUEPRINT_App_Build_Server.zip SERVICE_BLUEPRINT_Developer_Workstation.zip SERVICE_BLUEPRINT_Private_QA.zip SERVICE_BLUEPRINT_Public_QA.zip SERVICE_BLUEPRINT_Public_QA_(2-tier).zip ZIP file containing a Linux shell script to emulate the changes made by a code developer to modify the appearance theme and add additional products to the Magento database. Also includes PHP script files and images needed to perform the modifications. ZIP file containing a Linux shell script to configure the Developer Workstation server. ZIP file containing Linux shell scripts to configure the QA database server and the QA web server. HP Cloud Service Automation service designs Appendix D Resource offerings To associate a resource provider with a resource offering: 1. Log on to the HP CSA Provider Console at 2. Make sure the resource provider is up and running. 3. Select the Resource Management tab at the top of the page, then the Offerings button in the left panel, and finally the By Provider Type tab under the Offerings header bar. 4. Click on the link to the resource offering. 5. Select the Providers tab and then the Associate additional Providers to this offering icon. In the popup window, find the provider and then click on the Associate button. 6. Click Close. 31

32 Table 15 shows all of the resource offerings that were used in this implementation and Table 16 shows the mapping between the Lifecycle Actions and corresponding HP Operations Orchestration workflows. Table 15. Resource offerings Resource Offering Resource Provider Lifecycle Action Lifecycle Phase Lifecycle State MOE_SCL HP Matrix OE MOE Simple Compute Linux - Deploy MOE Simple Compute Linux - Undeploy SA_MANAGE_SERVERS HP SA Update SA Server Id on CSA Unmanage Server on SA LOAD_AGENT HP SA Copy And Install Agent Update Hostname PPTY DEPLOY_SOFTWARE HP SA Provision Software using SA Policies (MOE) Deploying Un-Deploying Deploying Un-Deploying Reserving Reserving Deploying Transition Transition Transition Transition Transition Transition Post- Transition QA_RUN_SETUP HP OO QA Servers Setup Deploying Post- Transition QA_RUN_PUBLIC_SETUP HP OO QA Servers Setup Public Deploying Transition DEV_STATION_SETUP HP OO Developer Workstation Setup Deploying Transition DEV_CODE_CHANGE HP OO Developer Code Change Deployed Table 16. Resource offerings Lifecycle Actions to HP Operations Orchestration workflows mapping Action MOE Simple Compute Linux Deploy MOE Simple Compute Linux - Undeploy Update SA Server Id on CSA Unmanage Server on SA Copy And Install Agent Update Hostname PPTY Provision Software using SA Policies (MOE) QA Servers Setup QA Servers Setup Public Developer Workstation Setup Developer Code Change Workflow /Library/CSA/3.0/Providers/Matrix Operating Environment/HP IO Lifecycle/Actions/MOE Simple Compute Linux Deploy /Library/CSA/3.0/Providers/Matrix Operating Environment/HP IO Lifecycle/Actions/MOE Simple Compute Linux Undeploy /Library/CSA/3.0/Providers/Server Automation/Manage Servers/Actions/Update SA Server Id on CSA /Library/CSA/3.0/Providers/Server Automation/Manage Servers/Actions/Unmanage Server on SA /Library/CSA/3.1/DevTest in Hybrid Cloud/HP Server Automation/Deploy SA Agent/Actions/Copy And Install Agent /Library/CSA/3.1/DevTest in Hybrid Cloud/HP Server Automation/Deploy SA Agent/Actions/Update Hostname PPTY /Library/CSA/Contrib/Provider/HP Server Automation/SA as Application Provider using SW Policies/Actions/Provision Software using SA Policies (MOE) /Library/CSA/3.1/DevTest in Hybrid Cloud/HP Server Automation/Utilities/Actions/QA Servers Setup /Library/CSA/3.1/DevTest in Hybrid Cloud/HP Server Automation/Utilities/Actions/QA Servers Setup Public /Library/CSA/3.1/DevTest in Hybrid Cloud/HP Server Automation/Utilities/Actions/Developer Workstation Setup /Library/CSA/3.1/DevTest in Hybrid Cloud/Linux Server/Actions/Developer Code Change 32

33 Appendix E Service designs Tables 17 through 21 list the components/nodes, resource bindings, and properties for each component in the five service designs that were created for this implementation. Table 17. App Build Server Service Design Content Node Type Resource Bindings Properties Build Server Service Composite Server Tier Infrastructure Service MOE_SCL SA_MANAGE_SERVERS DEPLOY_SOFTWARE TEMPLATENAME:vCenterRHEL AppBuildServer Software Component Table 18. Developer Workstation Service Design Content Node Type Resource Bindings Properties Developer Station Service Composite Workstation Tier Infrastructure Service MOE_SCL SA_MANAGE_SERVERS DEPLOY_SOFTWARE DEV_STATION_SETUP DEV_CODE_CHANGE SVN_SERVER_IP: TEMPLATENAME:vCenterRHEL Developer Workstation Developer Code Change Software Component Software Component Table 19. Private QA Service Design Content Node Type Resource Bindings Properties Local QA Service Composite DB Infrastructure Service MOE_SCL SA_MANAGE_SERVERS DEPLOY_SOFTWARE QA_RUN_SETUP JENKINS_BUILD_NUMBER: JENKINS_SERVER_IP: TEMPLATENAME:vCenterRHEL QA DB & Web Server Software Component 33

34 Table 20. Public QA Service Design Content Node Type Resource Bindings Properties Public QA Service Composite DB Infrastructure Service MOE_SCL LOAD_AGENT SA_MANAGE_SERVERS DEPLOY_SOFTWARE QA_RUN_PUBLIC_SETUP JENKINS_BUILD_NUMBER: JENKINS_SERVER_IP: KEYPAIRPATHOO:\Keys\hpcsAccess.key KEYPAIRPATHSA:/Keys/hpcsAccess.key REMOTEUSER:root TEMPLATENAME:vm-HPCS QA DB & Web Server Software Component Table 21. Public QA (2-tier) Service Design Content Node Type Resource Bindings Properties Public QA (2-tier) Service Composite DB Infrastructure Service MOE_SCL LOAD_AGENT SA_MANAGE_SERVERS DEPLOY_SOFTWARE JENKINS_BUILD_NUMBER: JENKINS_SERVER_IP: KEYPAIRPATHOO:\Keys\hpcsAccess.key KEYPAIRPATHSA:/Keys/hpcsAccess.key REMOTEUSER:root TEMPLATENAME:vm-HPCS QA DB Server Software Component Web Infrastructure Service MOE_SCL LOAD_AGENT SA_MANAGE_SERVERS DEPLOY_SOFTWARE QA_RUN_PUBLIC_SETUP JENKINS_BUILD_NUMBER: JENKINS_SERVER_IP: KEYPAIRPATHOO:\Keys\hpcsAccess.key KEYPAIRPATHSA:/Keys/hpcsAccess.key REMOTEUSER:root TEMPLATENAME:vm-HPCS QA Web Server Software Component Appendix F Creating an HP Server Automation software policy HP Server Automation software policies are essentially a collection of software packages, in this case primarily Linux packages that are grouped together. Software policies can contain other items, such as ZIP packages, scripts and other software policies. For the Dev/Test implementation example, numerous policies are created. Instead of giving a step-by-step guide on how to create each one, we will give details on how to create one policy and similar steps can be performed to create additional software policies. For this example software policy, we are going to show how to create the MySQL_ policy the contents are shown in Table 22. All packages should be imported into the /Package Repository/All Red Hat Linux/Red Hat Enterprise Linux Server 6 X86_64 folder in HP Server Automation. Make sure you select both RHEL 6 X86_64 and CentOS X86_64 OS types so that the same packages can be deployed to both operating systems. Even though the packages are physically located in just the RHEL 6 X86_64 folder, they can be used for multiple OSs. 34

35 Table 22. MySQL_ Packages Policy Name Policy Items Type MySQL_ mysql-libs el6. x86_64 perl-dbi el6. x86_64 perl-dbd-mysql el6. x86_64 mysql el6. x86_64 mysql-server el6. x86_64 Downloading the required software packages Create a temporary folder on your CMS and download the required software packages. The packages listed above were used to develop and test the implementation. Newer versions may be available and supersede those listed here. If you are unable to obtain the listed versions, be sure that new versions are compatible, and include all the necessary dependencies. These packages may already be installed on a repository that you can access, part of the Red Hat Enterprise Linux OS media, or available to you from the Red Hat Network (RHN). If you do not have access to a repository, OS media, or RHN, then you can manually download the individual packages from several sites, including: or Appendix G Software policies contains more details on all of the packages that are required for this implementation. Importing software and creating HP Server Automation policies The downloaded packages will now be imported into HP Server Automation and used in a software policy. Importing the packages To import software into HP Server Automation, complete the following steps: 1. Log in to HP Server Automation Java Client as an administrative user. Note: You can download the Java client from the Server Automation web client accessible at Core IP address>. The link to download the Java client is on the login page. Click Download Hewlett- Packard Launcher to install the application. The installer has an option to create a shortcut on your desktop. You don t need to log in to the web client. 2. Select Library from the button on the bottom left. 3. Select the By Folder tab. 4. Right-click the Library folder and select Import Software. 5. Click Browse to the right of the File(s) field and select all five packages that were listed in Table 22. The Type field should be automatically set to. 6. Change the value for Folder to /Package Repository/All Red Hat Linux/Red Hat Enterprise Linux Server 6 X86_64. Click Select. 7. Change the value for Platforms to Red Hat Enterprise Linux Server 6 X86_64 and CentOS 6 X86_ Click Import. Create a new policy 1. Right-click the Library folder and select New Software Policy. 2. Set the following values: a. Set Name to MySQL_. b. Click Select and set the Location to /Package Repository/All Red Hat Linux/Red Hat Enterprise Linux Server 6 X86_64. c. Set the OS to CentOS 6 X86_64 and Red Hat Enterprise Linux Server 5 X86_64. This will be displayed as Some Linux in HP Server Automation. 3. Select Policy Items in the Views panel. 4. Click Add in the toolbar. 5. Select the Browse Folders tab. 35

36 6. Expand the Package Repository/All Red Hat Linux/Red Hat Enterprise Linux Server 6 X86_64 folder. 7. Select the following: 8. Click Select. a. mysql-libs el6.x86_64 b. perl-dbi el6.x86_64 c. perl-dbd-mysql el6.x86_64 d. mysql el6.x86_64 e. mysql-server el6.x86_64 9. Click File Save. 10. Verify that the 5 files you selected in the steps above are listed. 11. Close the View window. Appendix G Software policies Table 25 shows a list of the Dev/Test software policies and their respective contents. See Appendix F Creating an HP Server Automation software policy for instructions on how to create a software policy if you are unfamiliar with the process. Generally software packages ( and ZIP files) are imported into HP Server Automation and then software policies, which are essentially collections of software packages, or other software policies, are created. These software policies can then be installed onto a server and provide a consistent way of deploying software onto a server or set of servers. Many of the packages needed for this Dev/Test implementation may already be installed on a repository that you can access, part of the Red Hat Enterprise Linux OS media, or available to you from the Red Hat Network (RHN). If you do not have access to a repository, OS media, or RHN, then you can either manually download the individual packages from several sites, including: or However, there are a few packages that need to be downloaded from specific Internet sites according to Table 23. The packages that are downloaded as.tar.gz files need to be wrapped as ZIP files before being imported into HP Server Automation as a software package. There are also 4 ZIP files that can be found in the HP distribution file in the scripts folder. Table 23: Server Automation software package setup scripts Software Package jre-7u9-linux-x64.rpm home-appliances.zip magento tar.gz Jenkins noarch.rpm mysql el6.x86_64.rpm mysql-libs el6.x86_64.rpm mysql-server el6.x86_64.rpm AppServerFiles.zip DevWorkstationFiles.zip DevCodeChangeFiles.zip QASetupFiles.zip Internet Location oracle.com/technetwork/java/javase/downloads/index.html expertmagentodevelopers.com/blog/download-free-magento-1.7-themes/ magentocommerce.com/download HP Distribution File HP Distribution File HP Distribution File HP Distribution File 36

37 When importing the ZIP packages, the Default Install Path needs to be changed to /tmp and the Post-Install Script content needs to be set according to the values in Table 24. Figure 17 gives a screen shot of the AppServerFiles.zip package properties, highlighting the values that need to be changed. Table 24. Server Automation software package setup scripts Software Package Default Install Path Post-Install Script QASetupFiles.zip /tmp /bin/chmod +x /tmp/*.sh DevCodeChangeFiles.zip /tmp /bin/chmod +x /tmp/*.sh home-appliances.zip /tmp DevWorkstationFiles.zip /tmp /bin/chmod +x /tmp/*.sh AppServerFiles.zip /tmp /bin/chmod +x /tmp/*.sh /tmp/setupappbuildserver.sh > /tmp/appserversetup.log magento tar.gz.zip /tmp Figure 17. AppServerFiles.zip ZIP Package properties Here are a few tips to follow when creating software policies: All of the individual items (scripts, ZIP packages, and packages) will need to be imported into HP Server Automation and stored in the /Package Repository/All Red Hat Linux/Red Hat Enterprise Linux Server 6 X86_64 folder. Verify that both Red Hat Enterprise Linux X86_64 and CentOS X86_64 are selected for the OS type for all imported software. Verify that all ZIP packages, including those wrapping.tar.gz packages, have a Default Install Path of /tmp. See Figure 17 above as an example. 37

HP CloudSystem Enterprise

HP CloudSystem Enterprise HP CloudSystem Enterprise F5 BIG-IP and Apache Load Balancing Reference Implementation Technical white paper Table of contents Introduction... 2 Background assumptions... 2 Overview... 2 Process steps...

More information

HP CloudSystem Enterprise

HP CloudSystem Enterprise Technical white paper HP CloudSystem Enterprise HP Cloud Service Automation Design for Microsoft Windows VM with HP Data Protector Table of contents Executive summary... 2 HP CloudSystem Enterprise overview...

More information

Intel Cloud Builders Reference Implementation

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

More information

HP CloudSystem Enterprise

HP CloudSystem Enterprise Technical white paper HP CloudSystem Enterprise Creating a multi-tenancy solution with HP Matrix Operating Environment and HP Cloud Service Automation Table of contents Executive summary 2 Multi-tenancy

More information

HP CloudSystem Enterprise

HP CloudSystem Enterprise Technical white paper HP CloudSystem Enterprise A LAMP and WordPress reference implementation Table of contents Introduction... 2 Background assumptions... 2 Additional requirements for SiteScope... 2

More information

Implementing the HP Cloud Map for SAS Enterprise BI on Linux

Implementing the HP Cloud Map for SAS Enterprise BI on Linux Technical white paper Implementing the HP Cloud Map for SAS Enterprise BI on Linux Table of contents Executive summary... 2 How to utilize this HP CloudSystem Matrix template... 2 Download the template...

More information

HP Cloud Service Automation

HP Cloud Service Automation Technical white paper HP Cloud Service Automation Integration with HP Service Manager Table of contents Introduction 2 Required software components 2 Configuration requirements 2 Downloading the distribution

More information

HP Cloud Map for TIBCO ActiveMatrix BusinessWorks: Importing the template

HP Cloud Map for TIBCO ActiveMatrix BusinessWorks: Importing the template HP Cloud Map for TIBCO ActiveMatrix BusinessWorks: Importing the template An HP Reference Architecture for TIBCO Technical white paper Table of contents Executive summary... 2 Solution environment... 2

More information

Interworks. Interworks Cloud Platform Installation Guide

Interworks. Interworks Cloud Platform Installation Guide Interworks Interworks Cloud Platform Installation Guide Published: March, 2014 This document contains information proprietary to Interworks and its receipt or possession does not convey any rights to reproduce,

More information

Installing and Using the vnios Trial

Installing and Using the vnios Trial Installing and Using the vnios Trial The vnios Trial is a software package designed for efficient evaluation of the Infoblox vnios appliance platform. Providing the complete suite of DNS, DHCP and IPAM

More information

Quick Start Guide for VMware and Windows 7

Quick Start Guide for VMware and Windows 7 PROPALMS VDI Version 2.1 Quick Start Guide for VMware and Windows 7 Rev. 1.1 Published: JULY-2011 1999-2011 Propalms Ltd. All rights reserved. The information contained in this document represents the

More information

Advanced Service Design

Advanced Service Design vcloud Automation Center 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions

More information

Extensibility. vcloud Automation Center 6.0 EN-001328-00

Extensibility. vcloud Automation Center 6.0 EN-001328-00 vcloud Automation Center 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions

More information

Windows Azure Pack Installation and Initial Configuration

Windows Azure Pack Installation and Initial Configuration Windows Azure Pack Installation and Initial Configuration Windows Server 2012 R2 Hands-on lab In this lab, you will learn how to install and configure the components of the Windows Azure Pack. To complete

More information

System Administration Training Guide. S100 Installation and Site Management

System Administration Training Guide. S100 Installation and Site Management System Administration Training Guide S100 Installation and Site Management Table of contents System Requirements for Acumatica ERP 4.2... 5 Learning Objects:... 5 Web Browser... 5 Server Software... 5

More information

Installing and Configuring vcenter Multi-Hypervisor Manager

Installing and Configuring vcenter Multi-Hypervisor Manager Installing and Configuring vcenter Multi-Hypervisor Manager vcenter Server 5.1 vcenter Multi-Hypervisor Manager 1.1 This document supports the version of each product listed and supports all subsequent

More information

IaaS Configuration for Cloud Platforms

IaaS Configuration for Cloud Platforms vrealize Automation 6.2.3 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions

More information

In order to upload a VM you need to have a VM image in one of the following formats:

In order to upload a VM you need to have a VM image in one of the following formats: What is VM Upload? 1. VM Upload allows you to import your own VM and add it to your environment running on CloudShare. This provides a convenient way to upload VMs and appliances which were already built.

More information

Using HP Systems Insight Manager to achieve high availability for Microsoft Team Foundation Server

Using HP Systems Insight Manager to achieve high availability for Microsoft Team Foundation Server Using HP Systems Insight Manager to achieve high availability for Microsoft Team Foundation Server Executive summary... 2 Audience... 2 Architecture... 3 Prerequisite... 4 Deploying AT servers... 5 Configuring

More information

Installing and Configuring vcloud Connector

Installing and Configuring vcloud Connector Installing and Configuring vcloud Connector vcloud Connector 2.7.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new

More information

How to Backup and Restore a VM using Veeam

How to Backup and Restore a VM using Veeam How to Backup and Restore a VM using Veeam Table of Contents Introduction... 3 Assumptions... 3 Add ESXi Server... 4 Backup a VM... 6 Restore Full VM... 12 Appendix A: Install Veeam Backup & Replication

More information

Core Protection for Virtual Machines 1

Core Protection for Virtual Machines 1 Core Protection for Virtual Machines 1 Comprehensive Threat Protection for Virtual Environments. Installation Guide e Endpoint Security Trend Micro Incorporated reserves the right to make changes to this

More information

vcenter Operations Management Pack for SAP HANA Installation and Configuration Guide

vcenter Operations Management Pack for SAP HANA Installation and Configuration Guide vcenter Operations Management Pack for SAP HANA Installation and Configuration Guide This document supports the version of each product listed and supports all subsequent versions until a new edition replaces

More information

OnCommand Performance Manager 1.1

OnCommand Performance Manager 1.1 OnCommand Performance Manager 1.1 Installation and Setup Guide For Red Hat Enterprise Linux NetApp, Inc. 495 East Java Drive Sunnyvale, CA 94089 U.S. Telephone: +1 (408) 822-6000 Fax: +1 (408) 822-4501

More information

Web Sites, Virtual Machines, Service Management Portal and Service Management API Beta Installation Guide

Web Sites, Virtual Machines, Service Management Portal and Service Management API Beta Installation Guide Web Sites, Virtual Machines, Service Management Portal and Service Management API Beta Installation Guide Contents Introduction... 2 Environment Topology... 2 Virtual Machines / System Requirements...

More information

F-Secure Messaging Security Gateway. Deployment Guide

F-Secure Messaging Security Gateway. Deployment Guide F-Secure Messaging Security Gateway Deployment Guide TOC F-Secure Messaging Security Gateway Contents Chapter 1: Deploying F-Secure Messaging Security Gateway...3 1.1 The typical product deployment model...4

More information

vsphere Replication for Disaster Recovery to Cloud

vsphere Replication for Disaster Recovery to Cloud vsphere Replication for Disaster Recovery to Cloud vsphere Replication 5.8 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

Quick Start Guide for Parallels Virtuozzo

Quick Start Guide for Parallels Virtuozzo PROPALMS VDI Version 2.1 Quick Start Guide for Parallels Virtuozzo Rev. 1.1 Published: JULY-2011 1999-2011 Propalms Ltd. All rights reserved. The information contained in this document represents the current

More information

Consolidated Monitoring, Analysis and Automated Remediation For Hybrid IT Infrastructures. Goliath Performance Monitor Installation Guide v11.

Consolidated Monitoring, Analysis and Automated Remediation For Hybrid IT Infrastructures. Goliath Performance Monitor Installation Guide v11. Consolidated Monitoring, Analysis and Automated Remediation For Hybrid IT Infrastructures Goliath Performance Monitor Installation Guide v11.5 (v11.5) Document Date: March 2015 www.goliathtechnologies.com

More information

NexentaConnect for VMware Virtual SAN

NexentaConnect for VMware Virtual SAN NexentaConnect for VMware Virtual SAN QuickStart Installation Guide 1.0.2 FP2 Date: October, 2015 Subject: NexentaConnect for VMware Virtual SAN QuickStart Installation Guide Software: NexentaConnect for

More information

NSi Mobile Installation Guide. Version 6.2

NSi Mobile Installation Guide. Version 6.2 NSi Mobile Installation Guide Version 6.2 Revision History Version Date 1.0 October 2, 2012 2.0 September 18, 2013 2 CONTENTS TABLE OF CONTENTS PREFACE... 5 Purpose of this Document... 5 Version Compatibility...

More information

Eucalyptus 3.4.2 User Console Guide

Eucalyptus 3.4.2 User Console Guide Eucalyptus 3.4.2 User Console Guide 2014-02-23 Eucalyptus Systems Eucalyptus Contents 2 Contents User Console Overview...4 Install the Eucalyptus User Console...5 Install on Centos / RHEL 6.3...5 Configure

More information

CTERA Agent for Linux

CTERA Agent for Linux User Guide CTERA Agent for Linux September 2013 Version 4.0 Copyright 2009-2013 CTERA Networks Ltd. All rights reserved. No part of this document may be reproduced in any form or by any means without written

More information

QuickStart Guide for Managing Computers. Version 9.2

QuickStart Guide for Managing Computers. Version 9.2 QuickStart Guide for Managing Computers Version 9.2 JAMF Software, LLC 2013 JAMF Software, LLC. All rights reserved. JAMF Software has made all efforts to ensure that this guide is accurate. JAMF Software

More information

ADFS 2.0 Application Director Blueprint Deployment Guide

ADFS 2.0 Application Director Blueprint Deployment Guide Introduction: ADFS 2.0 Application Director Blueprint Deployment Guide Active Directory Federation Service (ADFS) is a software component from Microsoft that allows users to use single sign-on (SSO) to

More information

Rally Installation Guide

Rally Installation Guide Rally Installation Guide Rally On-Premises release 2015.1 rallysupport@rallydev.com www.rallydev.com Version 2015.1 Table of Contents Overview... 3 Server requirements... 3 Browser requirements... 3 Access

More information

Installing and Configuring vcenter Support Assistant

Installing and Configuring vcenter Support Assistant Installing and Configuring vcenter Support Assistant vcenter Support Assistant 5.5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

Using Application Services

Using Application Services vrealize Automation 6.2.2 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions

More information

Administration Guide for the System Center Cloud Services Process Pack

Administration Guide for the System Center Cloud Services Process Pack Administration Guide for the System Center Cloud Services Process Pack Microsoft Corporation Published: May 7, 2012 Author Kathy Vinatieri Applies To System Center Cloud Services Process Pack This document

More information

vcenter Operations Manager for Horizon Supplement

vcenter Operations Manager for Horizon Supplement vcenter Operations Manager for Horizon Supplement vcenter Operations Manager for Horizon 1.6 This document supports the version of each product listed and supports all subsequent versions until the document

More information

Foundations and Concepts

Foundations and Concepts vcloud Automation Center 6.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions

More information

Cloud Services ADM. Agent Deployment Guide

Cloud Services ADM. Agent Deployment Guide Cloud Services ADM Agent Deployment Guide 10/15/2014 CONTENTS System Requirements... 1 Hardware Requirements... 1 Installation... 2 SQL Connection... 4 AD Mgmt Agent... 5 MMC... 7 Service... 8 License

More information

McAfee Public Cloud Server Security Suite

McAfee Public Cloud Server Security Suite Installation Guide McAfee Public Cloud Server Security Suite For use with McAfee epolicy Orchestrator COPYRIGHT Copyright 2015 McAfee, Inc., 2821 Mission College Boulevard, Santa Clara, CA 95054, 1.888.847.8766,

More information

Veeam Backup Enterprise Manager. Version 7.0

Veeam Backup Enterprise Manager. Version 7.0 Veeam Backup Enterprise Manager Version 7.0 User Guide August, 2013 2013 Veeam Software. All rights reserved. All trademarks are the property of their respective owners. No part of this publication may

More information

vsphere Replication for Disaster Recovery to Cloud

vsphere Replication for Disaster Recovery to Cloud vsphere Replication for Disaster Recovery to Cloud vsphere Replication 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

Table of Contents. Introduction...9. Installation...17. Program Tour...31. The Program Components...10 Main Program Features...11

Table of Contents. Introduction...9. Installation...17. Program Tour...31. The Program Components...10 Main Program Features...11 2011 AdRem Software, Inc. This document is written by AdRem Software and represents the views and opinions of AdRem Software regarding its content, as of the date the document was issued. The information

More information

Backup-as-a-Service with HP Helion CloudSystem Enterprise

Backup-as-a-Service with HP Helion CloudSystem Enterprise Technical white paper Backup-as-a-Service with HP Helion CloudSystem Enterprise Integrating HP LiveVault Service with OpenStack technology Table of contents Executive summary... 3 HP Helion CloudSystem

More information

Active Directory Management. Agent Deployment Guide

Active Directory Management. Agent Deployment Guide Active Directory Management Agent Deployment Guide Document Revision Date: April 26, 2013 Active Directory Management Deployment Guide i Contents System Requirements... 1 Hardware Requirements... 2 Agent

More information

NovaBACKUP xsp Version 15.0 Upgrade Guide

NovaBACKUP xsp Version 15.0 Upgrade Guide NovaBACKUP xsp Version 15.0 Upgrade Guide NovaStor / November 2013 2013 NovaStor, all rights reserved. All trademarks are the property of their respective owners. Features and specifications are subject

More information

http://docs.trendmicro.com

http://docs.trendmicro.com Trend Micro Incorporated reserves the right to make changes to this document and to the products described herein without notice. Before installing and using the product, please review the readme files,

More information

WhatsUp Gold v16.3 Installation and Configuration Guide

WhatsUp Gold v16.3 Installation and Configuration Guide WhatsUp Gold v16.3 Installation and Configuration Guide Contents Installing and Configuring WhatsUp Gold using WhatsUp Setup Installation Overview... 1 Overview... 1 Security considerations... 2 Standard

More information

RSA Authentication Manager 8.1 Virtual Appliance Getting Started

RSA Authentication Manager 8.1 Virtual Appliance Getting Started RSA Authentication Manager 8.1 Virtual Appliance Getting Started Thank you for purchasing RSA Authentication Manager 8.1, the world s leading two-factor authentication solution. This document provides

More information

User Manual. Onsight Management Suite Version 5.1. Another Innovation by Librestream

User Manual. Onsight Management Suite Version 5.1. Another Innovation by Librestream User Manual Onsight Management Suite Version 5.1 Another Innovation by Librestream Doc #: 400075-06 May 2012 Information in this document is subject to change without notice. Reproduction in any manner

More information

http://docs.trendmicro.com

http://docs.trendmicro.com Trend Micro Incorporated reserves the right to make changes to this document and to the products described herein without notice. Before installing and using the product, please review the readme files,

More information

Backup-as-a-Service with HP Helion CloudSystem Enterprise

Backup-as-a-Service with HP Helion CloudSystem Enterprise Technical white paper Backup-as-a-Service with HP Helion CloudSystem Enterprise Integrating HP LiveVault Service with Cloud Service Automation Table of contents Executive summary... 2 HP Helion CloudSystem

More information

Installing and Administering VMware vsphere Update Manager

Installing and Administering VMware vsphere Update Manager Installing and Administering VMware vsphere Update Manager Update 1 vsphere Update Manager 5.1 This document supports the version of each product listed and supports all subsequent versions until the document

More information

Implementing the HP Cloud Map for a 5000 mailbox Microsoft Exchange Server 2013 solution

Implementing the HP Cloud Map for a 5000 mailbox Microsoft Exchange Server 2013 solution Technical white paper Implementing the HP Cloud Map for a 5000 mailbox Microsoft Exchange Server 2013 solution Using a Windows Server 2012 Hyper-V Failover Cluster and virtual machines Table of contents

More information

Deploy XenApp 7.5 and 7.6 and XenDesktop 7.5 and 7.6 with Amazon VPC

Deploy XenApp 7.5 and 7.6 and XenDesktop 7.5 and 7.6 with Amazon VPC XenApp 7.5 and 7.6 and XenDesktop 7.5 and 7.6 Deploy XenApp 7.5 and 7.6 and XenDesktop 7.5 and 7.6 with Amazon VPC Prepared by: Peter Bats Commissioning Editor: Linda Belliveau Version: 5.0 Last Updated:

More information

Getting Started with ESXi Embedded

Getting Started with ESXi Embedded ESXi 4.1 Embedded vcenter Server 4.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent

More information

Camilyo APS package by Techno Mango Service Provide Deployment Guide Version 1.0

Camilyo APS package by Techno Mango Service Provide Deployment Guide Version 1.0 Camilyo APS package by Techno Mango Service Provide Deployment Guide Version 1.0 Contents Introduction... 3 Endpoint deployment... 3 Endpoint minimal hardware requirements:... 3 Endpoint software requirements:...

More information

1 P a g e Delivering Self -Service Cloud application service using Oracle Enterprise Manager 12c

1 P a g e Delivering Self -Service Cloud application service using Oracle Enterprise Manager 12c Delivering Self-service Cloud application services using Oracle Enterprise Manager 12c Kai Yu, Senior Principal Engineer, Oracle Solutions Engineering, Dell Inc ABSTRACT Oracle Self-Service provisioning

More information

Installing and Configuring vcloud Connector

Installing and Configuring vcloud Connector Installing and Configuring vcloud Connector vcloud Connector 2.0.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new

More information

How To Install An Aneka Cloud On A Windows 7 Computer (For Free)

How To Install An Aneka Cloud On A Windows 7 Computer (For Free) MANJRASOFT PTY LTD Aneka 3.0 Manjrasoft 5/13/2013 This document describes in detail the steps involved in installing and configuring an Aneka Cloud. It covers the prerequisites for the installation, the

More information

Remote Application Server Version 14. Last updated: 06-02-15

Remote Application Server Version 14. Last updated: 06-02-15 Remote Application Server Version 14 Last updated: 06-02-15 Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise

More information

Freshservice Discovery Probe User Guide

Freshservice Discovery Probe User Guide Freshservice Discovery Probe User Guide 1. What is Freshservice Discovery Probe? 1.1 What details does Probe fetch? 1.2 How does Probe fetch the information? 2. What are the minimum system requirements

More information

Consolidated Monitoring, Analysis and Automated Remediation For Hybrid IT Infrastructures. Goliath Performance Monitor Installation Guide v11.

Consolidated Monitoring, Analysis and Automated Remediation For Hybrid IT Infrastructures. Goliath Performance Monitor Installation Guide v11. Consolidated Monitoring, Analysis and Automated Remediation For Hybrid IT Infrastructures Goliath Performance Monitor Installation Guide v11.6 (v11.6) Document Date: August 2015 www.goliathtechnologies.com

More information

Virtual Appliance Setup Guide

Virtual Appliance Setup Guide Virtual Appliance Setup Guide 2015 Bomgar Corporation. All rights reserved worldwide. BOMGAR and the BOMGAR logo are trademarks of Bomgar Corporation; other trademarks shown are the property of their respective

More information

IaaS Configuration for Cloud Platforms

IaaS Configuration for Cloud Platforms vcloud Automation Center 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions

More information

Charter Business Desktop Security Administrator's Guide

Charter Business Desktop Security Administrator's Guide Charter Business Desktop Security Administrator's Guide Table of Contents Chapter 1: Introduction... 4 Chapter 2: Getting Started... 5 Creating a new user... 6 Recovering and changing your password...

More information

User Guide for VMware Adapter for SAP LVM VERSION 1.2

User Guide for VMware Adapter for SAP LVM VERSION 1.2 User Guide for VMware Adapter for SAP LVM VERSION 1.2 Table of Contents Introduction to VMware Adapter for SAP LVM... 3 Product Description... 3 Executive Summary... 3 Target Audience... 3 Prerequisites...

More information

INTRODUCTION APPLICATION DEPLOYMENT WITH ORACLE VIRTUAL ASSEMBLY

INTRODUCTION APPLICATION DEPLOYMENT WITH ORACLE VIRTUAL ASSEMBLY SIMPLIFYING APPLICATION DEPLOYMENT IN CLOUD USING VIRTUAL ASSEMBLIES AND EM 12C Kai Yu, Dell Inc. ABSTRACT Oracle virtual assemblies provide a great way to simply the deployment of enterprise-class multi-tier

More information

Acronis Backup & Recovery 10 Advanced Server Virtual Edition. Quick Start Guide

Acronis Backup & Recovery 10 Advanced Server Virtual Edition. Quick Start Guide Acronis Backup & Recovery 10 Advanced Server Virtual Edition Quick Start Guide Table of contents 1 Main components...3 2 License server...3 3 Supported operating systems...3 3.1 Agents... 3 3.2 License

More information

Synchronizer Installation

Synchronizer Installation Synchronizer Installation Synchronizer Installation Synchronizer Installation This document provides instructions for installing Synchronizer. Synchronizer performs all the administrative tasks for XenClient

More information

HP Server Management Packs for Microsoft System Center Essentials User Guide

HP Server Management Packs for Microsoft System Center Essentials User Guide HP Server Management Packs for Microsoft System Center Essentials User Guide Part Number 460344-001 September 2007 (First Edition) Copyright 2007 Hewlett-Packard Development Company, L.P. The information

More information

EMC Data Domain Management Center

EMC Data Domain Management Center EMC Data Domain Management Center Version 1.1 Initial Configuration Guide 302-000-071 REV 04 Copyright 2012-2015 EMC Corporation. All rights reserved. Published in USA. Published June, 2015 EMC believes

More information

Connection Broker Managing User Connections to Workstations, Blades, VDI, and More. Quick Start with Microsoft Hyper-V

Connection Broker Managing User Connections to Workstations, Blades, VDI, and More. Quick Start with Microsoft Hyper-V Connection Broker Managing User Connections to Workstations, Blades, VDI, and More Quick Start with Microsoft Hyper-V Version 8.1 October 21, 2015 Contacting Leostream Leostream Corporation http://www.leostream.com

More information

Hands on Lab: Building a Virtual Machine and Uploading VM Images to the Cloud using Windows Azure Infrastructure Services

Hands on Lab: Building a Virtual Machine and Uploading VM Images to the Cloud using Windows Azure Infrastructure Services Hands on Lab: Building a Virtual Machine and Uploading VM Images to the Cloud using Windows Azure Infrastructure Services Windows Azure Infrastructure Services provides cloud based storage, virtual networks

More information

SHAREPOINT 2013 IN INFRASTRUCTURE AS A SERVICE

SHAREPOINT 2013 IN INFRASTRUCTURE AS A SERVICE SHAREPOINT 2013 IN INFRASTRUCTURE AS A SERVICE Contents Introduction... 3 Step 1 Create Azure Components... 5 Step 1.1 Virtual Network... 5 Step 1.1.1 Virtual Network Details... 6 Step 1.1.2 DNS Servers

More information

JAMF Software Server Installation Guide for Linux. Version 8.6

JAMF Software Server Installation Guide for Linux. Version 8.6 JAMF Software Server Installation Guide for Linux Version 8.6 JAMF Software, LLC 2012 JAMF Software, LLC. All rights reserved. JAMF Software has made all efforts to ensure that this guide is accurate.

More information

Installation and Deployment

Installation and Deployment Installation and Deployment Help Documentation This document was auto-created from web content and is subject to change at any time. Copyright (c) 2016 SmarterTools Inc. Installation and Deployment SmarterStats

More information

Moving to Plesk Automation 11.5

Moving to Plesk Automation 11.5 Moving to Plesk Automation 11.5 Last updated: 2 June 2015 Contents About This Document 4 Introduction 5 Preparing for the Move 7 1. Install the PA Moving Tool... 8 2. Install Mail Sync Software (Windows

More information

Parallels Plesk Automation

Parallels Plesk Automation Parallels Plesk Automation Contents Get Started 3 Infrastructure Configuration... 4 Network Configuration... 6 Installing Parallels Plesk Automation 7 Deploying Infrastructure 9 Installing License Keys

More information

Issue Tracking Anywhere Installation Guide

Issue Tracking Anywhere Installation Guide TM Issue Tracking Anywhere Installation Guide The leading developer of version control and issue tracking software Table of Contents Introduction...3 Installation Guide...3 Installation Prerequisites...3

More information

VMware vrealize Operations for Horizon Administration

VMware vrealize Operations for Horizon Administration VMware vrealize Operations for Horizon Administration vrealize Operations for Horizon 6.1 This document supports the version of each product listed and supports all subsequent versions until the document

More information

User's Guide - Beta 1 Draft

User's Guide - Beta 1 Draft IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft Hyper-V Server Agent vnext User's Guide - Beta 1 Draft SC27-2319-05 IBM Tivoli Composite Application Manager for Microsoft

More information

Pearl Echo Installation Checklist

Pearl Echo Installation Checklist Pearl Echo Installation Checklist Use this checklist to enter critical installation and setup information that will be required to install Pearl Echo in your network. For detailed deployment instructions

More information

VMware vsphere 5.0 Evaluation Guide

VMware vsphere 5.0 Evaluation Guide VMware vsphere 5.0 Evaluation Guide Auto Deploy TECHNICAL WHITE PAPER Table of Contents About This Guide.... 4 System Requirements... 4 Hardware Requirements.... 4 Servers.... 4 Storage.... 4 Networking....

More information

HP CloudSystem Matrix: Collecting Usage Data for Showback, Charge-back, and Billing Purposes

HP CloudSystem Matrix: Collecting Usage Data for Showback, Charge-back, and Billing Purposes HP CloudSystem Matrix: Collecting Usage Data for Showback, Charge-back, and Billing Purposes Technical white paper Table of contents Abstract... 2 Overview... 2 CloudSystem Matrix... 4 The CloudSystem

More information

NEFSIS DEDICATED SERVER

NEFSIS DEDICATED SERVER NEFSIS TRAINING SERIES Nefsis Dedicated Server version 5.2.0.XXX (DRAFT Document) Requirements and Implementation Guide (Rev5-113009) REQUIREMENTS AND INSTALLATION OF THE NEFSIS DEDICATED SERVER Nefsis

More information

AT&T CLOUD SERVICES. AT&T Synaptic Compute as a Service SM : How to Get Started. Version 2.0 January 2012

AT&T CLOUD SERVICES. AT&T Synaptic Compute as a Service SM : How to Get Started. Version 2.0 January 2012 Version 2.0 January 2012 AT&T CLOUD SERVICES AT&T Synaptic Compute as a Service SM : How to Get Started 2012 AT&T Intellectual Property. All rights reserved. Notice Copyright AT&T Intellectual Property.

More information

HP Operations Orchestration Software

HP Operations Orchestration Software HP Operations Orchestration Software Software Version: 9.00 HP Business Availability Center Integration Document Release Date: June 2010 Software Release Date: June 2010 Legal Notices Warranty The only

More information

insync Installation Guide

insync Installation Guide insync Installation Guide 5.2 Private Cloud Druva Software June 21, 13 Copyright 2007-2013 Druva Inc. All Rights Reserved. Table of Contents Deploying insync Private Cloud... 4 Installing insync Private

More information

Implementing Microsoft Windows Server Failover Clustering (WSFC) and SQL Server 2012 AlwaysOn Availability Groups in the AWS Cloud

Implementing Microsoft Windows Server Failover Clustering (WSFC) and SQL Server 2012 AlwaysOn Availability Groups in the AWS Cloud Implementing Microsoft Windows Server Failover Clustering (WSFC) and SQL Server 2012 AlwaysOn Availability Groups in the AWS Cloud David Pae, Ulf Schoo June 2013 (Please consult http://aws.amazon.com/windows/

More information

Virtual Data Centre. User Guide

Virtual Data Centre. User Guide Virtual Data Centre User Guide 2 P age Table of Contents Getting Started with vcloud Director... 8 1. Understanding vcloud Director... 8 2. Log In to the Web Console... 9 3. Using vcloud Director... 10

More information

Getting Started with Database Provisioning

Getting Started with Database Provisioning Getting Started with Database Provisioning VMware vfabric Data Director 2.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

User's Manual. Intego Remote Management Console User's Manual Page 1

User's Manual. Intego Remote Management Console User's Manual Page 1 User's Manual Intego Remote Management Console User's Manual Page 1 Intego Remote Management Console for Macintosh 2007 Intego, Inc. All Rights Reserved Intego, Inc. www.intego.com This manual was written

More information

Reconfiguring VMware vsphere Update Manager

Reconfiguring VMware vsphere Update Manager Reconfiguring VMware vsphere Update Manager vsphere Update Manager 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a

More information

HP Intelligent Management Center v7.1 Virtualization Monitor Administrator Guide

HP Intelligent Management Center v7.1 Virtualization Monitor Administrator Guide HP Intelligent Management Center v7.1 Virtualization Monitor Administrator Guide Abstract This guide describes the Virtualization Monitor (vmon), an add-on service module of the HP Intelligent Management

More information

Deployment and Configuration Guide

Deployment and Configuration Guide vcenter Operations Manager 5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions

More information

Installation and Configuration Guide for Windows and Linux

Installation and Configuration Guide for Windows and Linux Installation and Configuration Guide for Windows and Linux vcenter Operations Manager 5.7 This document supports the version of each product listed and supports all subsequent versions until the document

More information