HP Cloud Service Automation with Red Hat Enterprise Linux OpenStack Platform

Transcription

1 Technical white paper HP Cloud Service Automation with Red Hat Enterprise Linux OpenStack Platform Delivered on HP ConvergedSystem 700x Table of contents Executive summary... 2 Introduction... 2 Overview... 2 About OpenStack... 2 About Red Hat Enterprise Linux OpenStack Platform... 2 About HP Cloud Service Automation... 3 About HP Operations Orchestration... 5 About HP ConvergedSystem 700x... 5 Solution components... 7 Hardware requirements... 8 Software requirements... 8 Configuration guidance... 9 Configuration requirements... 9 Installation and configuration of the Content Pack... 9 Verification of content pack installation Configuration of offerings in HP CSA Service management Subscribe to a service Cancel a subscription Summary Implementing a proof-of-concept Appendix Support matrix Known issues For more information Click here to verify the latest version of this document

2 2 Executive summary HP Cloud Service Automation plus OpenStack make offering enterprise Infrastructure as a Service (IaaS) Private Cloud a reality. The Red Hat Enterprise Linux OpenStack Platform delivers the foundation to create, deploy, and scale a public or private OpenStack cloud, but it does not specify hardware infrastructure deployment or optimization. This white paper includes specific recommendations and best practices for deploying a small but scalable OpenStack cloud on an HP ConvergedSystem 700x system. HP ConvergedSystem 700x is part of a family of solutions offering simplified, efficient, and reliable application deployment platforms. This solution is built on HP Converged Infrastructure, with integrated and optimized models for Red Hat Enterprise Linux (RHEL) and Red Hat Enterprise Virtualization (RHEV) virtualized workloads. Based on a modular design, ConvergedSystem 700x provides options for components and services to meet a broad set of requirements, deliver seamless scalability and provide an open on-ramp to the cloud. HP Cloud Service Automation (HP CSA) is a unique platform that orchestrates the deployment of compute and infrastructure resources and of complex multi-tier application architectures. HP CSA integrates and leverages the strengths of several HP data center management and automation products, adding resource management, service offering design, and a customer portal to create a comprehensive service automation solution. This integration is part of HP CSA Content Pack and demonstrates how to integrate HP CSA with OpenStack private cloud environment. This paper provides information about an HP lab implementation of HP Cloud Service Automation with Red Hat Enterprise Linux OpenStack Platform 4.0 on HP ConvergedSystem 700x. Target audience: This document is intended for cloud or data center administrators, managers, and staff wishing to learn more about HP Cloud Service Automation and Red Hat Enterprise Linux OpenStack on ConvergedSystem 700x deployment. A working knowledge of Linux, OpenStack, VLANs, iptables, HP servers, storage, HP Virtual Connect, Integrated Lights-Out (ilo) and virtualization is recommended. Document purpose: The purpose of this document is to describe the lab environment and offer ideas on how deployment can be streamlined and optimized. This white paper describes test deployment performed in July Introduction This white paper has been created to provide guidance in the deployment and integration of HP Cloud Service Automation (HP CSA) with Red Hat Enterprise Linux OpenStack Platform 4.0 cloud on the HP ConvergedSystem 700x. The ConvergedSystem 700x has been chosen, and we describe the steps necessary to successfully integrate and use HP CSA with Red Hat Enterprise Linux OpenStack Platform 4.0 on this hardware, providing a small private cloud which may be scaled up by using additional compute nodes. Overview About OpenStack OpenStack is an open source platform that builds an Infrastructure as a Service (IaaS) cloud that runs on commodity hardware. OpenStack is designed for scalability so that new compute and storage resources can be easily added to grow a cloud over time. Large organizations such as HP have built massive public clouds on top of OpenStack. OpenStack is more than a standard software package; it integrates a number of different technologies to construct a cloud. Although the number of options to do this may appear daunting at first, the OpenStack approach provides the greatest amount of flexibility to the users. About Red Hat Enterprise Linux OpenStack Platform Red Hat Enterprise Linux OpenStack Platform provides the foundation to build a private or public IaaS cloud on top of Red Hat Enterprise Linux. It offers a massively scalable, fault-tolerant platform for the development of cloud-enabled workloads. Red Hat Enterprise Linux OpenStack Platform 4.0 is based on OpenStack Havana, and packaged so that available physical hardware can be turned into a private, public, or hybrid cloud platform including: Fully distributed object storage Persistent block-level storage Virtual-machine provisioning engine and image storage Authentication and authorization mechanism

3 Integrated networking Web browser-based GUI for both users and administration The Red Hat Enterprise Linux OpenStack Platform IaaS cloud is implemented by a collection of interacting services that control its computing, storage and networking resources. The cloud is managed using a web-based interface that allows administrators to control, provision and automate OpenStack resources. Additionally, the OpenStack infrastructure is facilitated through an extensive API, which is also available to end users of the cloud. About HP Cloud Service Automation HP Cloud Service Automation (CSA) is the industry s most complete, open and heterogeneous cloud management platform for managing application and infrastructure services, including OpenStack-based private clouds. HP Cloud Service Automation helps your organization increase agility by reducing service deployment time from months to minutes, deliver greater value to customers by improving responsiveness, and reduce costs by automating service provisioning. The solution features an open, extensible architecture that supports HP and third-party management tools, enabling you to quickly adapt to changing business requirements while supporting heterogeneous IT environments. HP Cloud Service Automation is a unique platform that orchestrates the deployment of compute and infrastructure resources and of complex multi-tier application architectures. HP CSA integrates and leverages the strengths of several HP data center management and automation products, adding resource management, service offering design, and a customer portal to create a comprehensive service automation solution. The HP Cloud Service Automation subscription, service design and resource utilization capabilities provide three key requirements for implementing a private cloud: The HP CSA Marketplace Portal provides a customer interface for requesting new cloud services and for monitoring and managing existing services, with subscription pricing to meet the business requirements of all. The HP CSA graphical service design and content portability tools simplify developing, leveraging, and sharing an array of service offerings that can be tailored to the needs of the customer. The HP CSA lifecycle framework and resource utilization features ease the complexity of mapping the cloud fulfillment infrastructure into reusable, automated resource offerings for on-time and on-budget delivery. As shown in Figure 1, HP CSA provides a task- and role-based approach, supporting these user roles: CSA Consumer The Consumer uses the Marketplace Portal to manage cloud services, including subscribing to service offerings, managing service subscriptions, and performing actions on service instances. Consumer Service Administrator The Consumer Service Administrator configures and manages consumer and provider organizations. CSA Administrator The Administrator has access to all functionality in the Cloud Service Management Console. Resource Supply Manager The Resource Supply Manager creates and manages cloud resources, such as providers and resource offerings. Service Business Manager The Service Business Manager creates and manages the service offerings and service catalogs. Service Designer The Service Designer designs, implements, and maintains service designs (also referred to as blueprints), component palettes, component types, component templates, and resource offerings. Service Operations Manager The Service Operations Manager views and manages subscriptions and service instances. 3

4 Figure 1. HP CSA task- and role-based capabilities Cloud services requests and management Customers can request new cloud services and manage their existing services with the HP CSA Marketplace Portal. The following tasks can be completed using the Marketplace Portal. Request subscriptions for services offered to their groups View status of pending requests, pending approvals and approved subscriptions, including detailed component information Request service modifications and other actions for their cloud services Cancel subscriptions Groups using Marketplace Portal The groups of people who will use Marketplace Portal include these customers, subscribers and approvers: Consumers who use cloud services Subscribers who request cloud services for themselves or on behalf of others Approvers who grant others requests for services when an approval is required Figure 2. HP Cloud Service Automation portal 4

5 About HP Operations Orchestration HP Cloud Service Automation uses HP Operations Orchestration (HP OO), an industry-leading solution for IT process automation and runbook automation, to interface with different providers such as Red Hat Enterprise Linux OpenStack Platform. HP OO is a system for creating and using actions in structured sequences (called flows) which maintain, troubleshoot, repair and provision IT resources by: Checking the health, diagnosing and repairing networks, servers, services, software applications and individual workstations Checking client, server, and virtual machines for software and updates, and performing the necessary installations, updates, and distributions when required Performing repetitive tasks, such as checking status on internal or external website pages In many companies, the following issues can result in poor service quality, delayed time-to-market, and high operating costs. Incidents huge numbers of alerts and unnecessary escalations Change and releases too many manual errors and lack of audit trails Process management need for processes for complex tasks such as disaster recovery Virtualization inconsistent management of physical and virtual assets Automation and orchestration of IT processes with HP OO can help address those issues: Element automation automation of networks, servers or storage, spanning tasks from provisioning and change management to compliance enforcement and reporting Runbook automation automation of common and repeatable IT processes across all infrastructure tiers, IT groups, and systems Integrated automation of applications, servers, networks, storage, and common processes across the data center Automation of the business service, with continuous control of each phase of the service lifecycle, across the data center and client end points, from automated operations to monitoring and ticketing Key benefits of HP OO The key benefits of HP OO include: Reduced operational cost with automation of common tasks and processes Improved service quality with accelerated incident resolution Improved audit compliance through documentation generation and reporting Integration with current IT environment to ensure minimal impact on procedures and tools More than 5000 pre-built operations and flows and 80+ integrations for rapid time to value About HP ConvergedSystem 700x The ConvergedSystem 700x family of solutions offers simplified and reliable application deployment platforms built on HP Converged Infrastructure. The solutions have a modular architecture and a large array of options to provide access to the cloud, including: Accelerated business outcomes with greater simplicity Reduced time to value from pre-optimized, complete solutions Built-in resource provisioning Integrated management Single vendor solution lifecycle support Reduced risk from superior infrastructure and HP best practices Twenty years of innovation and leadership Reliable implementation based on proven technology 5

6 ConvergedSystem 700x provides standardized building blocks of server, storage, networking, rack and power, and HP innovation. At its core, ConvergedSystem 700x includes: HP ProLiant BL460c Gen8 servers in an HP BladeSystem c7000 enclosure with HP Virtual Connect FlexFabric interconnects for the simplest, most cost-efficient virtualization platform. HP 3PAR StoreServ 7000 or series, for efficient, flexible and easy-to-manage storage with non-disruptive scaling of capacity and performance, supporting a high number of VMs. HP FlexNetwork high-performance, low-latency architecture ideal for virtualized data centers, enabling faster virtual migration than alternative multi-tiered approaches. HP options for flexibility and optimization reside at every level. HP and partner services for comprehensive solution support and service offerings provide for every situation, from consulting to delivery to lifecycle support. This document demonstrates how to integrate HP CSA with Red Hat Enterprise Linux OpenStack Platform private cloud, and describes this as implemented on an HP ConvergedSystem 700x. Figure 3 below depicts a lab implementation of an HP ConvergedSystem 700x running HP CSA, HP OO and Red Hat Enterprise Linux OpenStack Platform. Note Although this paper is focused on Red Hat Enterprise Linux OpenStack Platform 4, the HP Cloud Service Automation and Operations Orchestration designs are compatible with both Red Hat Enterprise Linux OpenStack Platform 4 and 5. 6

7 Figure 3. HP ConvergedSystem 700x diagram Solution components This solution includes three important components: HP ConvergedSystem 700x Red Hat Enterprise Linux OpenStack Platform 4.0 HP Cloud Service Automation with HP Operations Orchestration 7

8 Hardware requirements The table below shows the set of ConvergedSystem 700x components used for this reference architecture in the lab. Table 1. ConvergedSystem 700x hardware requirements Component One HP BladeSystem c7000 enclosure Two Virtual Connect FlexFabric 10 Gb/24-Port Modules Eight ProLiant BL460c Gen8 E5-v2 server blades Three ProLiant DL360p Gen8 E5-v2 management servers One HP 3PAR StoreServ 7400 with 2-nodes Two HP StoreFabric SN6000B 48-port SAN switches Two HP 5920AF-24XG switches Two HP G El switches Purpose Enclosure to host blades and Virtual Connect modules Virtual Connect module for Ethernet and SAN connectivity Blade Servers to host OpenStack services Rack Servers One to act as a Client for OpenStack and the other two to run HP CSA and HP OO Storage back-end for Glance Image service and Cinder Block Storage service Fibre Channel Switches for SAN connectivity between servers and 3PAR 10 GbE Top-of-Rack switches Ethernet switches Note For this reference architecture an additional HP ProLiant DL360e server installed with Microsoft Windows Server 2008 R2 operating system was used as a jumpstation. This server was used to download or install any necessary software components, and connect to ilos, Virtual Connect Manager and Onboard Administrator. HP 3PAR Management Console was installed on this server to manage the HP 3PAR used for this reference architecture. Software requirements A successful deployment includes: Red Hat Enterprise Linux 6 Red Hat Enterprise Linux OpenStack Platform 4.0 or 5.0 Servers registered to Red Hat Network (RHN) HP 3PAR OS version or higher HP Cloud Service Automation version 4.0 or 4.1 HP Operations Orchestration version or Note HP Cloud Service Automation version 4.0 must be used in combination with HP Operations Orchestration 10.02; and, HP Cloud Service Automation version 4.1 must be used in combination with HP Operations Orchestration

9 Configuration guidance Configuration requirements The following configuration must be completed and tested before implementing this paper. Additional links to important documentation and downloads are available in the For more information section at the end of this document. Red Hat Enterprise Linux OpenStack Platform 4.0 must be configured and operational on HP ConvergedSystem 700x. For details on setup, refer HP CSA and HP OO must be installed and configured. For details, refer to the Installation Guide and Configuration Guide for Windows available at HP customers and partners must have an active HP support agreement ID (SAID) and an HP Passport sign-in to access this documentation. The HP CSA administrator and Marketplace Portal (MPP) must be configured. Steps to complete the configuration are available in the HP CSA configuration guide, chapter 4, Marketplace Portal. Key point Ensure HP OO certificates are imported to the HP CSA server when installed on separate server nodes. Refer to procedures in the HP CSA Configuration Guide in the chapter Create an HP CSA Encryption Keystore. Installation and configuration of the Content Pack Download HP CSA Content Pack The distribution file for HP Content Pack (CP) and documentation can be found on HP Live Network. HP customers and partners must have an active HP support agreement ID (SAID) for HP CSA and an HP Passport sign-in to access this Content Pack. The following need to be downloaded to duplicate this implementation. Red Hat Enterprise Linux OpenStack Platform integration documentation documentation contains CSA/OO detailed procedure for integrating with Red Hat Enterprise Linux OpenStack Platform. Content Pack installation guide guide contains the CP deployment procedure using CP Installer for both Windows/Linux. CP Installer installer package with a filename of CapsuleInstaller_1.zip is used for both Windows and Linux. Refer to the guide listed above for more detail. CP Content this will download HP CSA/OO content with a filename of CumulativeCapsule_OO10.zip to be deployed by CP Installer. See Figure 4 for details. 9

10 Figure 4. HP Content Pack download page The CP installer deploys all these files automatically to their install locations on the HP CSA server. The CP Content file CumulativeCapsule_OO10.zip contains the RedHat OpenStack Integration toolkit whose contents are as shown in Table 2. Table 2. Contents of RedHat OpenStack Integration.zip under CP CumulativeCapsule_OO10.zip Folder File name Description Provider Service designs SERVICE_DESIGN_CSL_RedHat_OpenStack_- _Compute_with_Storage_v1.0_90cd da480147cdf98b3a4e75 HP CSA service design RedHat OpenStack Tools 1.rh-flavors.jsp 2. rh-images.jsp 3. rh-tenants.jsp 4. rh-common.jsp 5. rh-networks.jsp 6. rh-keypairs.jsp 7. rh-securitygroups.jsp 8. provider.properties Tenant JSP files used for this implementation Resource provider properties file RedHat OpenStack 10

11 Important step The following CSA property files must be modified as below. Unzip the CumulativeCapsule_OO10.zip file to C:\Temp. Change directory to C:\Temp. Unzip the file: RedHat OpenStack Integration.zip From the Tools folder, copy the provider.properties file to the location: <CSA_HOME>\jboss-as Final\modules\sun\jdk\main\service-loader-resources Modify the following parameters in the file: <CSA_HOME>\jboss-as Final\standalone\deployments\csa.war\WEB-INF\classes\csa.war properties file: DynamicPropertyFetch.READ_TIMEOUT= DynamicPropertyFetch.RESPONSE_SIZE= Key point In this implementation the location of CSA Home is CSA_HOME= C:\Program Files\Hewlett Packard\CSA Verify HP CSA CP installer environment requirements The CP installer must be run on the server where HP CSA is installed. Java SE Runtime Environment (JRE) version 7u45 or later must be installed on the server where the content pack installer is executed. Verify JRE version JRE version 1.7 or higher is needed. Check the version by entering the following command at a command prompt: java -fullversion If the JRE is not installed or the required minimum version is not available, then download it from oracle.com/technetwork/java/javase/downloads/java-se-jre-7-download html. Installation instructions for the JRE are available at oracle.com/technetwork/java/javase/documentation/index.html. Check certificate for remote HP OO server If HP OO is installed on a remote server, ensure that the certificate for the HP OO server has been imported to the certstore on the HP CSA server. Next, test the connection. This is required for the installer to perform process definition with a remote HP OO server. See HP CSA documentation for instructions on how to set up the certificate. Run HP CSA and OO Content Pack installer The content installer provides a unified, graphical interface for installing and updating content for HP Cloud Service Automation (HP CSA) and HP OO. It will lead the user through a series of steps to prepare for installation, perform the installation, configure new content, and enable content in HP CSA and HP Operations Orchestration. The installer was tested to work with HP CSA and HP Operations Orchestration REST functionality. See supported versions in the content pack Release Notes document. To access this document, log in with HP Passport credentials. Check for prerequisite before CP installation The following HP Operations Orchestration 10 Standard content packs are dependencies to be installed (resolved) before deploying the Content Pack. Base dependencies are available at oo10-base-cp oo10-cloud-cp oo10-hp-solutions-cp oo10-virtualization-cp oo10-sa-cp oo10-sm-cp oo10-csa-cp or oo10-csa-cp

12 Launch the installer 1. Log in to the server as root or a user with administrator privileges. 2. Navigate to CapsuleInstaller_1.zip (CP Installer). 3. Extract the downloaded file to a folder of choice on the server where HP CSA is installed. Included in the bundle is an XML file silent_install.xml for managing silent/headless installs. 4. Open a command prompt. 5. Navigate to the location where the installer was extracted. 6. Double-click CapsuleInstaller.jar or enter the following command to launch the installer. java jar CapsuleInstaller.jar Install procedure At the introduction panel, browse and select the downloaded CumulativeCapsule_OO10.zip content pack to install. If no capsule zip file is selected or is improperly designated, a validation failed pop-up will display, giving the details regarding the problem. Ensure the default setting is set to importing content to HP Operations Orchestration and to import service designs into HP CSA as shown in Figure 5. Figure 5. HP Content Pack Installer launch page Once a viable CumulativeCapsule_OO10.zip file is found, a pop-up will display detailing the necessary out-of-thebox (OOTB) content required within HP OO prior to installation of CP If the dependencies are not met, the screen shown in Figure 6 will display. Ensure that all the dependencies listed in the Check prerequisite before CP installation section in this paper are resolved. 12

13 Figure 6. Content support matrix pop-up If all dependencies are met, the message shown in Figure 7 will display. This screen lists the supported content versions for HP CSA and HP OO (this information can also be found in the Release Notes). Figure 7. Supported HP CSA and HP OO versions pop-up 13

14 Licensing The next step will be agreeing to the HP Licensing Terms for software usage. Upon accepting the License agreement shown in Figure 8, progress to the Next screen. Figure 8. License agreement Check and add resources At this point, if importing both HP OO flow content and HP CSA service designs is selected, the panel shown in Figure 9 will appear to provide credentials and modify information for connecting to the HP CSA server. Figure 9. Connecting to the HP CSA server To automatically scan for attached HP OO machines to this HP CSA instance, ensure that the box, Automatically detect linked instance(s) of HP OO is checked. Selecting Authenticate HP CSA will begin the process of auto-discovery. 14

15 After connecting to the HP CSA and HP Operations Orchestration instances, the screen shown in Figure 10 will present where HP CSA and HP Operations Orchestration instances can be added as necessary. When finished adding additional instances, if any, click Next to continue with the installation. Figure 10. Add necessary HP CSA and HP OO instances 15

16 Select Red Hat OpenStack content The screen shown in Figure 11 presents the option to select the components of interest. To install all the available components, check the top-level checkbox, Capsule Pack, and all sub-contained items will automatically select. For this implementation, Usecase_Capsule-RedHat_OpenStack_Content is selected as shown in Figure 11. Figure 11. Select Red Hat Enterprise Linux OpenStack Platform contents Click on any open item marker (+) to view details about the various service designs listed under the Capsule Pack. Here, selectively request which service designs to install for a particular use case. In this case, select Usecase_Capsule- RedHat_OpenStack_Content. Associated use-case flow components for HP Operations Orchestration will automatically be selected for installation to match the requested service designs. A short description related to the currently highlighted component will be displayed towards the bottom of this panel. Install content Clicking Next will bring up the pre-installation summary page detailing the service-design items selected along with the basic information supporting the HP OO and HP CSA machines for installation. On selecting to install, the content pack gets deployed with details displayed as shown in Figure 12 Figure 12. Install and configure content pack 16

17 Verification of content pack installation After the installer completes, log on to HP OO Central as an administrator at as shown in Figure 13. Figure 13. HP OO Central 17

18 Click on Content Management to browse the Flow Library. Expand the library to verify that the content has been installed in Library/CSA Content Pack/CSA3.2 as shown in Figure 14. Figure 14. Flows and actions in HP OO Tables 3 through 18 show the imported operations and describe each flow, including its input and output parameters. OpenStack Compute: Deploy Description: Creates a new server instance. Table 3. Parameters for OpenStack Deploy Type Parameter name Description Input imagename Image which has to be deployed Input flavorname Flavor name using which instance has to be created Input servername Specifies the name for the VM Input tenantname Name for the tenant/project that is unique within OpenStack Input ostype Specifies the type of OS 18

19 OpenStack Compute: Undeploy Description: Deletes a server instance. Table 4. Parameters for OpenStack Undeploy Type Parameter name Description Input serverid Specifies the server ID for the VM Input tenantid Tenant ID OpenStack Compute: Hard reboot Description: Performs a hard reboot of a server. A hard reboot (HARD) is equivalent to power cycling the server. Table 5. Parameters for OpenStack Hard reboot Type Parameter name Description Input serverid Specifies the server ID for the VM Input tenantid Tenant ID OpenStack Compute: Soft reboot Description: Performs a soft reboot of a server. In a soft reboot (SOFT), the operating system is signaled to restart, which allows for a graceful shutdown of all processes. Table 6. Parameters for OpenStack Soft reboot Type Parameter name Description Input serverid Specifies the server ID for the VM Input tenantid Tenant ID OpenStack Compute: Start server Description: Returns a STOPPED server to ACTIVE status. Table 7. Parameters for OpenStack Start server Type Parameter name Description Input serverid Specifies the server ID for the VM Input tenantid Tenant ID OpenStack Compute: Stop server Description: Halts a running server and changes status to STOPPED. Table 8. Parameters for OpenStack Stop server Type Parameter name Description Input serverid Specifies the server ID for the VM Input tenantid Tenant ID 19

20 OpenStack Compute: Suspend Description: Suspends a server and changes its status to SUSPENDED. Table 9. Parameters for OpenStack Suspend server Type Parameter name Description Input serverid Specifies the server ID for the VM Input tenantid Tenant ID OpenStack Compute: Resume server Description: Resumes a SUSPENDED server and changes its status to ACTIVE. Table 10. Parameters for OpenStack Resume server Type Parameter name Description Input serverid Specifies the server ID for the VM Input tenantid Tenant ID OpenStack Compute: Associate floating IP Description: Associates floating IP to a server. Table 11. Parameters for OpenStack Associate floating IP Type Parameter name Description Input serverid Specifies the server ID for the VM Input tenantid Tenant ID OpenStack Compute: Disassociate floating IP Description: Disassociates floating IP from the server. Table 12. Parameters for OpenStack Disassociate floating IP Type Parameter name Description Input serverid Specifies the server ID for the VM Input tenantid Tenant ID OpenStack Compute: Refresh Description: Refreshes the state of the server. Table 13. Parameters for OpenStack Refresh server Type Parameter name Description Input serverid Specifies the server ID for the VM Input tenantid Tenant ID 20

21 OpenStack: Add storage volume Description: Creates a new volume. Table 14. Parameters for OpenStack Add storage volume Type Parameter name Description Input volumesize Size, in gigabytes, for new volume Input volumedisplayname Display name for new volume Input volumedisplaydescription Description for new volume OpenStack Storage: Remove storage volume Description: Deletes the specified volume. Table 15. Parameters for OpenStack Remove storage volume Type Parameter name Description Input volumeid ID of the volume to delete OpenStack Storage: Create snapshot Description: Creates a new snapshot. Table 16. Parameters for OpenStack Create snapshot Type Parameter name Description Input displayname Name of snapshot to be created Input displaydescription Description of snapshot to be created Input volumeid ID of volume from which to create snapshot OpenStack Storage: Delete snapshot Description: Deletes the specified snapshot. Table 17. Parameters for OpenStack Delete snapshot Type Parameter name Description Input snapshotid ID of snapshot to delete 21

22 OpenStack: Add storage volume from snapshot Description: Creates a new volume from a snapshot. Table 18. Parameters for OpenStack Add storage volume from snapshot Type Parameter name Description Input volumesize Size in gigabytes for new volume Input volumedisplayname Display name for new volume Input volumedisplaydescription Description for the volume Input snapshotid ID of the snapshot from which to create the new volume Configuration of offerings in HP CSA Adding providers This implementation requires the resource providers shown in Table 19. Table 19. Resource providers Provider name RedHat OpenStack Service access point Provide OpenStack identity service API access endpoint: or host>:<port>/version For example: User name and password: RedHat OpenStack user and password that can be part of multiple tenant or single tenant. Configure provider property file This is an important configuration step. To configure the property file, perform the following step. Deploy the provider.properties file from: <CSA-Installation-Path>\jboss-as Final\standalone\deployments\csa.war\propertysources to the HP CSA server under the path: <CSA-Installation-Path>\jboss-as Final\modules\sun\jdk\main\serviceloaderresources Key Point The display name as entered while configuring the provider using the CSA portal should be the same as in the provider.properties file. If the provider display name RedHat OpenStack was entered, the provider.properties file should have the following: bind.os.provider.name = RedHat OpenStack 22

23 Configure RedHat OpenStack provider Complete the following steps to configure the RedHat OpenStack provider. 1. Log in to the Cloud Service Management Console as an administrator, as shown in Figure Click Providers. Figure 15. CSA Management console 3. Select a provider type in the panel on the left. In this case, select RedHat OpenStack, as shown in Figure 16. Figure 16. Select provider 23

24 4. Click Create. Enter the values for the required parameters as shown in Figure 17 and click Save. Figure 17. Create Resource Provider 5. Finish the procedure to create a new provider. Associate resource offerings with providers New resource offerings that were imported with the design archive must be associated with providers. It is required to associate the resource offerings and providers listed in Table 20. Table 20. Required resource offering and provider associations Resource offering RESOURCE_OFFERING_CSL_OpenStack_Compute_Actions_v1.0_90cd93c446a a917d4f90217 RESOURCE_OFFERING_CSL_OpenStack_Compute_v1.0_90cd93c446a a917c RESOURCE_OFFERING_CSL_OpenStack_Flex_Server_Count_v1.0_90cd93c446a a917de6302b0 RESOURCE_OFFERING_CSL_OpenStack_Flex_Volume_Count_v1.0_90cd93c446a a917bdd700d6 RESOURCE_OFFERING_CSL_OpenStack_Storage_v1.0_90cd93c446a a917af Provider RedHat OpenStack RedHat OpenStack RedHat OpenStack RedHat OpenStack RedHat OpenStack Complete the following steps for each resource offering listed in the table above: 1. Log in to the Cloud Service Management Console as an administrator. 2. Select the Resource Management tab. 3. Click Provider in the panel on the left under Offerings. 4. Click Select Resource Offerings as shown in Figure

25 Figure 18. Select resource offerings 5. Select all the resource offerings from the left box and click the Add button, then click the Save button as shown in Figure 19. Figure 19. Save resource offerings Create a service offering A service offering must be created in HP CSA before subscribers can request services based on the RedHat OpenStack service design. Follow the steps below to import the design. 1. Log in to the Cloud Service Management Console as an administrator. 2. Click Offerings. Figure 20. Offerings in CSA Management Console 25

26 3. Click Create Offering. The Create New Service Offering dialog will open as shown in Figure 21. Figure 21. Create new service offering 4. Enter a name for the new service offering. This is the name of the offering that will be visible to the subscribers of this service. 5. Select the appropriate service design and click the Select button as shown in Figure 22. Figure 22. Select service design 26

27 6. Click the Create button as shown in Figure 23. Figure 23. Create offering Publish a service offering HP CSA is installed with a default global catalog. When a service offering is published in this global catalog, that service offering will be visible in the Cloud Subscriber Portal for every organization. Complete the following steps: 1. Log in to the Cloud Service Management Console using an account with administrator privileges. 2. Click Catalogs as shown in Figure 24. Figure 24. Catalogs Link on CSA console 27

28 3. Double-click Global Shared Catalog in the panel on the right, shown in Figure 25. Figure 25. Global Shared Catalog screen 4. Navigate to the Offerings tab in the central panel and click the Add Offering button, as shown in Figure 26. Figure 26. Add offering screen 28

29 5. Select the service offering created in the previous steps and select an In Category, as shown in Figure 27 to define the category under which this service offering should appear in the Marketplace Portal. Click Publish to add a new service offering. Figure 27. Select category screen Service management Subscribe to a service This section provides examples of how a subscriber can order the service created in previous sections. Follow these steps to import the design and order a service: 1. Log in to Cloud Service Management Console as an administrator. 2. Click Marketplace. Figure 28. HP CSA Marketplace Portal Link 29

30 3. Log in to the Marketplace Portal with user credentials as shown in Figure 29. Figure 29. HP CSA Marketplace Portal Log in screen 4. Click All Services, as shown in Figure 30. The offerings available in this catalog will be displayed. Figure 30. Catalog dashboard 30

31 5. Click the service offering published earlier to order as shown in Figure 31. Figure 31. Order screen 6. Enter the number of servers to deploy as shown in Figure 32. Figure 32. Servers order screen 31

32 7. Complete the form with all required values for the subscription options as shown in Figure 33. Refer to Table 21 below for details on available options. Table 21. Required subscriber input Subscriber options Tenant name Image OS type Flavor Keypair Name Private Network Public Network Security Group Server name prefix Value Tenant/project name as in OpenStack. This Tenant/project name should be available in OpenStack. Image reference for the desired image for the server instance Type of OS (Windows/Linux) Flavor reference for the desired flavor for the server instance Name of the security key used with the new server. This keypair name should be available in OpenStack. The name of the Private network. The name of the Public network. The name of the security group used with the new server. Prefix name for the new server Figure 33. Subscription options screen 32

33 8. If OpenStack Block Storage Options is selected, Table 22 below lists the required Subscriber options. Check this box to enable attaching an additional volume to the compute instance and enter the options as shown in Figure 34. Table 22. Required OpenStack Block Storage Subscriber options Storage subscriber options Volume Name Volume Description Volume Size in GB Value Display name for the new volume Description for the new volume Size in gigabytes for the new volume Figure 34. OpenStack Block Storage Subscriber options 9. Click Checkout. 10. Enter values such as the subscription name, end date. 11. Click Submit Request. 12. Open the Subscriptions tab to monitor the status of the subscription. Once Published Catalog is selected, then a Loading Content wait screen presents, as shown in Figure 35, for approximately two to five minutes, depending on the compute/network speed. Figure 35. Wait screen Cancel a subscription A subscription may be canceled only if the service instance falls in one of the following status categories: Online Reserved Modification Failed Failed 33

34 To cancel a subscription 1. Select the Subscriptions tab from the HP Marketplace Portal Dashboard. 2. Locate the subscription to cancel. 3. Click View Details to display the details page for the subscription. Figure 36. Subscription details page 4. In the Summary box, click Cancel Subscription. 5. Click Yes to confirm cancellation of the subscription. The subscription is canceled, and a confirmation message is displayed. Figure 37. Subscription cancellation screen 6. Click OK to close the confirmation message. The Subscriptions tab opens with all subscriptions displayed. 7. Confirm the status for the canceled subscription. Note A request to cancel a subscription is approved automatically, so the request has the status of Approved on the Requests tab. 34

35 Summary After understanding and working through the steps described here, the result is a working small cloud that is scalable through the addition of compute and network nodes. HP CSA and Red Hat Enterprise Linux OpenStack Platform are a complex suite of software and may be configured in many different ways. This reference architecture should provide a baseline for implementation and can serve as a functional environment for many workloads. We recommend the excellent documentation on the Red Hat as well as OpenStack websites to learn more about the individual components and architectural choices available when setting up and running Red Hat Enterprise Linux OpenStack Platform. The HP ConvergedSystem 700x is an excellent platform for implementation of OpenStack. It provides powerful, dense compute and storage capabilities for this reference architecture; and the ilo management capability is indispensable in managing a small cluster of this kind. Implementing a proof-of-concept As a matter of best practice for all deployments, HP recommends implementing a proof-of-concept using a test environment that matches as closely as possible the planned production environment. In this way, appropriate performance and scalability characterizations can be obtained. For help with a proof-of-concept, contact an HP partner or HP Services representative at hp.com/large/contact/enterprise/index.html. Appendix Support matrix Table A-1. Support matrix Product Version HP Cloud Service Automation 4.01, or 4.10 HP Operations Orchestration or with CP or or later with Cloud CP Note: Obtain the latest content pack for HP Operations Orchestration from HP Live Network (HPLN). Red Hat Enterprise Linux OpenStack Platform Versions Red Hat Enterprise Linux OpenStack Platform 4 (Havana) Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse) Known issues This implementation does not support instance customization like hostname, DNS, etc. 35

36 For more information HP & Red Hat, hp.com/go/redhat HP CloudSystem, hp.com/go/cloudsystem Red Hat, redhat.com Red Hat Enterprise Linux OpenStack Platform, redhat.com/openstack HP Cloud Service Automation, hp.com/go/csa HP Operations Orchestration, hp.com/go/oo HP ConvergedSystems, hp.com/go/convergedsystem HP Live Network Portal, Red Hat product manuals and documentation, To access other toolkits to design and extend cloud services running on HP CloudSystem, go to hp.com/go/csdevelopers HP software product manuals and documentation for the following products can be found at HP customers and partners must have an active HP support agreement ID (SAID) and an HP Passport sign-in to access this documentation. HP Cloud Service Automation Module Specification, HP Server Automation, HP Operations Orchestration, To help us improve our documents, please provide feedback at hp.com/solutions/feedback. Sign up for updates hp.com/go/getupdated Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Microsoft and Windows are trademarks of the Microsoft Group of companies.. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Red Hat and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. The OpenStack Word Mark and OpenStack Logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation s permission. We are not affiliated with, endorsed, or sponsored by the OpenStack Foundation, or the OpenStack community. 4AA5-6085ENW, November 2014