Hp cloudsystem matrix by Fabian Hachur

Understanding the HP CloudSystem Matrix Technology

Technical white paper Table of contents Introduction......................................................................................................................................... 2 Overview: HP CloudSystem Matrix ........................................................................................................ 3 How CloudSystem Matrix is used........................................................................................................... 5 Provisioning workloads in a cloud infrastructure................................................................................... 6 Continuously optimizing the infrastructure with capacity and power management.................................. 13 Protecting continuity of services using high availability and disaster recovery capabilities ....................... 15 Enabling technology .......................................................................................................................... 16 BladeSystem c-Class ....................................................................................................................... 16 Virtual Connect .............................................................................................................................. 18 Matrix Operating Environment......................................................................................................... 19 Cloud Service Automation for Matrix................................................................................................ 20 Storage technologies ...................................................................................................................... 21 Security......................................................................................................................................... 21 Integrating HP CloudSystem Matrix into customer environments ........................................................... 23 HP CloudSystem extensions ............................................................................................................. 24 Expanding beyond private cloud ..................................................................................................... 25 Purchase and delivery ........................................................................................................................ 26 HP services to make the most of CloudSystem .................................................................................... 29 Ready capacity when business demands........................................................................................... 30 Summary and conclusion .................................................................................................................... 31 Appendix A: Implementing a private cloud ........................................................................................... 32 Appendix B: HP CloudSystem Matrix use cases ..................................................................................... 32 Increasing availability of infrastructure services during planned downtime ............................................ 32 Dynamic infrastructure provisioning and reprovisioning for an agile test and development environment.... 33 Ongoing optimization and consolidation with energy awareness......................................................... 33 Flexible management of secure mission-critical workloads in hybrid cloud environments ......................... 34 Appendix C: HP Cloud Mapsâ&#x20AC;&#x201D;an example.......................................................................................... 34 Glossary of terms............................................................................................................................... 37 For more information.......................................................................................................................... 40

Introduction Businesses are moving to the cloud in accelerating numbers. Business users recognize cloud advantages that help speed innovation, accelerate business processes, and reduce time to revenue. Frequently, these users turn to public cloud services for the solutions they need. In fact, a Forrester study found that business is adopting cloud five times faster than is IT operations. 1 IT directors are concerned about the challenges associated with the rush to cloud-based services: how can IT maintain adequate security, ensure service levels, and integrate cloud-based services with existing traditional IT systems? At the same time, IT departments are under tremendous pressure to keep pace with business demand. While IT infrastructure has made significant advances in performance and availability, the effort to meet increasing business demands has frequently led to “IT sprawl.” Computing resources proliferate throughout the business, but remain underutilized and too hardwired to redeploy easily when business needs change. Operating and maintaining those resources ties up IT dollars—personnel costs for server management and administration can be as much as 70-80% of an IT budget. 2 IT increasingly employs virtualization and automation to improve the flexibility and increase utilization of computing resources. However, this course has not yet eliminated the issues of over-provisioning and complexity. Too frequently, IT resources are dedicated to a particular application or business unit and any excess capacity remains unavailable for other uses. IT continues to be thwarted in its ability to focus its resources on strategic objectives and driving innovation, resulting in slow time to revenue and lost opportunity. HP offers you a solution to trapped IT resources and a path to providing secure, predictable cloudbased services through Converged Infrastructure. Your IT staff can consolidate physical and virtual server, storage, and network assets into pools of virtualized resources. These resource pools can host sets of infrastructure services, which typically map to application services, including complex multi-tier, multi-node applications. IT personnel can flexibly provision and reprovision services, and can confidently optimize the underlying resources for performance, resiliency, and efficiency. HP Converged Infrastructure technologies are at the core of the HP CloudSystem portfolio: a comprehensive, integrated, and open solution that provides IT with a unified way to provision and manage services across private clouds, public cloud providers, and traditional IT. HP CloudSystem equips you to respond to customers or business units faster, more predictably, more efficiently, and with lowered costs. HP CloudSystem offerings provide a range of services as well as an avenue for growth and expansion. As shown in Figure 1, HP CloudSystem has three integrated offerings. • HP CloudSystem Matrix: Enables you to deliver infrastructure as a service (IaaS) and achieve quickly the self-service, on-demand delivery model that you need to establish a private cloud. Moreover, you can attain the flexibility and efficiency of a private cloud infrastructure without giving up needed controls that reside in centers of data center expertise, such as server, network, storage, and facilities administration. • HP CloudSystem Enterprise: For those looking to deploy private and hybrid cloud environments and the full range of service models (IaaS, platform as a service (PaaS), and software as a service (SaaS)). This offering provides a single service view of your environments, from private cloud to public clouds to traditional IT, with advanced application-to-infrastructure lifecycle management. • HP CloudSystem Service Provider: Public or hosted private cloud designed for service providers to provide a public cloud IaaS and SaaS, including aggregation and management of those services.

Forrester Research, Inc., You're Not Ready For Internal Cloud, July 2010

IDC White Paper Sponsored by HP, Realizing TCO Savings with HP BladeSystem Virtual Connect Flex-10 Technology, Doc #218222, May 2009

Figure 1. Three integrated HP CloudSystem offerings for a full range of cloud capabilities

This whitepaper describes the HP CloudSystem Matrix solution (previously known as BladeSystem Matrix), with a focus on how it delivers shared IT infrastructure services. The document is intended for IT directors, IT architects, solution architects, and other readers who are familiar with current HP BladeSystem offerings and existing server virtualization technology. The content should assist you in understanding how HP CloudSystem Matrix can benefit your IT environments with more flexible, efficient use of physical and virtual IT resources. The paper begins with a discussion of key architectural and operational concepts and then highlights the key enabling technologies; it concludes with a brief overview of the purchase and implementation process, including available services.

Overview: HP CloudSystem Matrix HP CloudSystem Matrix is the ideal platform for private cloud and IaaS. It enables you to provision infrastructure and applications in minutes rather than months, resulting in greater agility and speed, as well as TCO savings. CloudSystem Matrix offers a self-service infrastructure portal for autoprovisioning and built-in lifecycle management to optimize infrastructure, monitor applications, and ensure uptime for cloud and traditional IT. HP CloudSystem Matrix makes use of industry-standard, modular components, but it is far more than simply a collection of components. In a single Converged Infrastructure platform, CloudSystem Matrix integrates technologies and services from across the HP enterprise portfolio that have been proven in the marketplace to provide value in demanding data center environments. CloudSystem Matrix also incorporates the offerings of leading application, management, network, and storage partners, so that the solution fits seamlessly into diverse customer environments and works with all traditional application workloads. The core elements of a CloudSystem Matrix solution are one or more BladeSystem c7000 enclosures with Virtual Connect, the Matrix Operating Environment, and Cloud Service Automation for Matrix. The Matrix Operating Environment includes an integrated service designer, self-service infrastructure portal, and auto-provisioning capabilities; the tools to manage and optimize the resource pools; and

a recovery management solution for ProLiant. Recovery management for HP-UX is available with HP Serviceguard. Using included Cloud APIs, you can easily customize the operating environment to your specific requirements, enabling chargeback and billing integration, integration into approval processes, as well as other process automation tasks. Cloud Service Automation for Matrix integrates application provisioning, monitoring, and lifecycle management. CloudSystem Matrix supports the full range of HP ProLiant and Integrity server blades. Storage options for Matrix include cloud-optimized HP 3PAR Utility Storage, Enterprise Virtual Arrays (EVA), and XP Disk Arrays, or you can connect Matrix to newly purchased or existing HP or supported third-party Fibre Channel (FC) SANs. Physical machine instances achieve maximum flexibility by using boot from SAN. Virtual machine instances are backed by files in the hypervisor file system, which could be on a variety of storage types (local disk, FC SAN, NAS, and iSCSI). You can easily incorporate CloudSystem Matrix into your existing data center environment. Virtual Connect modules in the BladeSystem enclosure enable Matrix to connect to any standard Ethernet network or Fibre Channel fabric. The platform is also compatible with a range of operating systems and hypervisors. Figure 2 provides a diagram of the HP CloudSystem Matrix solution with Virtual Connect FlexFabric.

Figure 2. Solution diagram of HP CloudSystem Matrix with Virtual Connect FlexFabric module*

* Optionally, Virtual Connect Flex-10 modules can be used for LAN connection and Virtual Connect Fibre Channel Modules for SAN connection. ** Cloud Service Automation for Matrix is an optional component of the CloudSystem Matrix solution.

CloudSystem Matrix arrives at your site as a factory-integrated solution. Each CloudSystem solution also includes HP on-site implementation services and demonstrations, enabling you to begin realizing

the value of CloudSystem and the IaaS model immediately. HP offers an integrated service and support portfolio, with extensive worldwide geographic coverage, to help you get the most from your CloudSystem solution. The Matrix Operating Environment capabilities provided in CloudSystem Matrix (illustrated conceptually in Figure 3) enable provisioning and re-provisioning of the shared pools of servers, storage, power, and network connectivity as needed, based on pre-defined templates. An IT architect or designer uses a graphical designer tool to build and publish infrastructure service templates incorporating physical and virtual servers, storage, networks, and the connections between them. Typically, each template represents the complete infrastructure needed to host a specific application service, such as Microsoft® Exchange, Oracle Real Application Clusters (RAC), an enterprise resource planning solution, or even a custom application, and may include the application itself. A service catalog of published service templates is then available; using a self-service infrastructure portal, users can request an instance of a service from the catalog to be automatically provisioned. Through its infrastructure orchestration capabilities, Matrix provides standardization and efficient control of provisioning of a private cloud infrastructure. Compared to a manual process that requires coordination among different teams across a data center or IT organization, CloudSystem Matrix enables administrators to provision an entire infrastructure service, including the application, in just minutes or hours instead of weeks or months. Administrators can also continuously monitor and optimize the cloud infrastructure—for example, by managing capacity, moving workloads or adjusting infrastructure service lease periods—as well as protect service continuity with disaster recovery and automated server failover.

Figure 3. CloudSystem Matrix automates the entire lifecycle to build and manage a private cloud

How CloudSystem Matrix is used Perhaps the best way to understand the unique value of HP CloudSystem Matrix is to examine how you can deliver and operate infrastructure services using CloudSystem Matrix and the capabilities of the Matrix Operating Environment and CSA for Matrix. This section describes how IT staff can

provision infrastructure services, optimize the infrastructure resources, and protect continuity of services. (For definitions of many of the terms used in this section, see the Glossary of terms.)

Provisioning workloads in a cloud infrastructure The most powerful attribute of HP CloudSystem Matrix is the speed and simplicity with which pools of infrastructure resources can be “carved up,” and flexibly configured and reconfigured to match the infrastructure requirements of nearly any application. You can deploy a single CloudSystem Matrix environment in place of multiple different server configurations to satisfy varied application requirements for CPU, memory, network, and storage and quickly build your private cloud. Matrix resources are then available on demand as infrastructure services for IT users to request using a service catalog. In a traditional IT environment, the deployment of a new application requires the involvement of many people and a high degree of coordination among them. An IT architect might draw up a design specifying the servers, virtual machines, storage, and networks needed to support the application. The design would specify the connections between those resources and adhere to established policies and standards. Based on this design, the different IT staff responsible for servers, storage, virtualization, networking, and facilities would assemble and/or activate the needed resources. This process could take multiple weeks, if not months, and involve repeated communication between the different IT groups. Making use of role-based infrastructure orchestration software, Matrix enables: • Administrators to create pools of resources and oversee and control their use. • IT architects to design the infrastructure to support business applications and publish service templates to drive implementation. • Users of IT services to select from a service catalog and request infrastructure services. The CloudSystem Matrix software simplifies, streamlines, and coordinates these processes and automates the provisioning of the infrastructure resources to satisfy approved requests. Creating resource pools An administrator can use the management console to define pools of server, network, and storage resources, register user accounts, and assign resource pools to users (Figure 4). Through the console, the administrator can also define virtual machine images and software deployment jobs.

Figure 4. Creating server pools

Populating storage pools The CloudSystem Matrix capabilities enable the Matrix administrator (typically a server administrator) to define the storage needs of a physical or virtual server (for example, a boot disk of a specific size, a shared data disk, and a private transaction log disk). A storage administrator can create and publish to a storage catalog. The storage administrator populates a set of storage volumes in the storage catalog to meet the provisioning needs of service templates in CloudSystem Matrix. The storage administrator controls the visibility of the storage volumes and the operations that can be performed. For example, this administrator could allow changes in OS mode or adjustments in LUN (logical unit number) masking for some volumes. The storage administrator can also define tiers of storage, based on performance and availability characteristics, and tag specific storage volumes according to the defined tiers. Matrix also allows the use of tags to identify storage volumes according to intended application—such as “production” or “database”—as well as other userdefined criteria. When specifying server storage needs in CloudSystem Matrix, the Matrix administrator can request candidate matches from the storage catalog and browse volumes chosen based on size, OS support, specified tags, and other values. The storage catalog also serves as a formal, automated communication mechanism between Matrix administrators and storage administrators. Rather than having to manually communicate storage needs to the storage administrator and later manually enter the information, the server administrator can request candidates through Matrix. If there are no matches, the storage administrator can see the unfulfilled request and provision appropriate storage (in other words, create the volume, present the volume, and adjust the SAN zoning, if necessary). The storage administrator can then fulfill the request with the provisioned storage, and the Matrix storage definition automatically updates to reflect that storage. When CloudSystem Matrix is paired with the HP 3PAR Storage System or the HP EVA solution, the storage catalog in Matrix can automatically discover existing volumes and enable the storage administrator to import them into the storage catalog and assign authorizations, thus avoiding manual entry. The storage administrator can also load volumes created in other arrays (HP or third-party) into

the storage catalog, automatically using workflows or manually. In addition, the storage catalog can represent volumes from multiple arrays in the same catalog. For customers wanting to integrate with their own storage provisioning processes, whether automated or manual, there is command line access to the storage definitions (requests) and the ability to import results back into the Matrix storage definitions. Designing the infrastructure and creating service templates The architect uses a graphical designer (shown in Figure 5) to plan and design infrastructures to fit the needs of business applications. For example, a design can be a three-tier architecture, with the database tier running in physical mode and the application and web tiers configured to run in virtual mode, or it can be a simple virtual machine. By dragging and dropping and connecting icons representing the required resources, the architect creates a template, saved as an XML file, for an infrastructure service. The architect can also import and export template files. The architect specifies attributes for the logical resources, such as minimum memory required, IP address allocation, requirements for physical or virtual servers, the amount of storage and storage tier (or other tagged criteria) required, and the software required on the boot disk. The architect saves each service template to a catalog for access only by specified, approved users. The infrastructure orchestration software validates the design and presents information about any issues so that they can be resolved before the template is published.

Figure 5. Creating a template using the graphical designer

The CloudSystem Matrix designer interface enables the architect to: • Design infrastructure service templates for a range of application needs—from a simple virtual machine cluster for a web front end, to a configuration for a test and development organization, to complex, multi-tier designs for e-shopping, enterprise resource planning (ERP), or customer relationship management (CRM) applications. • Incorporate established IT policies and standards with assurance that they will be followed in the provisioning process. • Specify costs to support budget tracking and reporting. • Attach custom workflows that automate key pre- and post-provisioning tasks. • Use workflows and processes to enable smooth transitions between roles or teams (Figure 6). Example workflows: – Open Request For Change (RFC) tickets for requests in ticketing/ change management systems – Pass customer, cost, and lease duration into a chargeback system – Apply patching and compliance policies in configuration management tools – Maintain status in change management systems when new services are created or changed

Figure 6. Adding workflows

The architect can design service templates from scratch, modify previously created templates, or leverage best practice templates. HP Cloud Maps, developed with key independent software vendors (ISVs), include standard templates and other resources to aid in designing and customizing service templates for applications such as Microsoft Exchange, Oracle RAC, and SAP NetWeaver, and others (visit www.hp.com/go/cloudmaps).

Included HP Cloud APIs enable the architect to integrate Matrix with business processes or other IT operations. For example, the architect can link Matrix provisioning to a company chargeback system. In designing a template, the architect can associate a cost with each of the elements of a service; the service template then displays the overall cost of the service. Using the interfaces provided, the architect (or administrator) can easily build the links to enable the chargeback system to capture usage and cost summaries from CloudSystem Matrix at the desired intervals. For details, see HP Cloud Advisor Nigel Cookâ&#x20AC;&#x2122;s blog posting on how to integrate Matrix into a chargeback or billing system at http://h30507.www3.hp.com/t5/Eye-on-Blades-Blog-Trends-in/Integrating-BladeSystemMatrix-into-a-Chargeback-or-Billing/ba-p/80389. For more information on Cloud APIs, see the white paper on Matrix integration interfaces at http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA09219ENW.pdf. Extending provisioning to applications Through integration with optional HP Cloud Service Automation (CSA) for Matrix software, CloudSystem Matrix offers automated application provisioning, monitoring, and compliance management. CSA for Matrix, the integration of HP Server Automation (SA) and HP SiteScope, enables the Matrix architect to select both the OS and application software needed for a service (Figure 7), create a single service template that comprehends both infrastructure and application, and thus include applications in the service catalog. Then, when a user requests the service, Matrix provisions the infrastructure including OS (virtual or physical or both) and application software as a single process.

Figure 7. Selecting software using SA of CSA for Matrix as a provisioning engine

Requesting infrastructure and application services An approved user can initiate the creation of a new service from the published templates, which may include infrastructure services or infrastructure and application services. Through the Matrix selfservice infrastructure portal, the user can: • Select a service template from the catalog (example in Figure 8). • Select one or more assigned resource pools. • View associated costs for the service and specify a lease period. Since provisioning infrastructure resources is generally the domain of IT, the Matrix portal is designed for IT staff as the typical users. However, line of business users can also use the portal to request infrastructure services. Users are able to browse only the service templates that they are authorized to use based on their functions in the organization. For example, members of a test and development team might see a variety of infrastructure services, while members of the finance department would see only services needed to support finance, and human resources (HR) personnel would see only services needed for HR functions. The self-service portal displays all of the user’s service requests, with their status, and provides email notification when a status changes.

Figure 8. Template catalog in self-service portal

Approval and provisioning The Matrix software sends an email notification of pending service requests to the administrator. Through the management console, the administrator can review each request, and approve or deny the request. Approval of a request initiates the provisioning process.

To the infrastructure orchestration software, the components of each service template are logical objects. A key capability of the software is allocation—the process of finding the resources that match the logical objects. After a user submits a service request through the self-service portal, the Matrix software validates the needed infrastructure for the service request and performs an allocation. If the software can locate the resources that match the template, the allocation is successful; the software reserves the selected resources and provisioning proceeds. CloudSystem Matrix performs automated provisioning for both virtual and physical servers by including physical server and virtual machine configurations, allocating appropriate SAN volumes, deploying and customizing the OS—and, with CSA for Matrix, installing the applications. CloudSystem Matrix supports a variety of mechanisms for deploying OS software. The software source can be virtual machine templates or HP server deployment software. When provisioning several virtual machines from the same virtual machine template, Matrix can utilize linked clones, which speeds up the provisioning process and reduces the amount of storage required. During provisioning, the Matrix infrastructure orchestration software invokes any associated workflows at their respective execution points. Because the service template automates and controls the provisioning, administrators can enforce established standards and avoid variances due to human error. Managing provisioned services Matrix notifies both the administrator and the user who requested the service when provisioning is complete. The administrator can view status, progress, and details of all completed and in-progress requests and take action to resolve failed requests. The administrator can also modify service infrastructures as required, for example, migrating workloads between server blades to support proactive maintenance activities in the physical environment. The provisioned service is available to the user for the duration of the specified lease period. A user can manage provisioned services through the infrastructure self-service portal—setting the servers to standby to reduce power consumption if a service is not needed temporarily, resuming the service and reactivating the servers when needed again. The user can also easily request a modified service lease period or request additional servers or storage. When a service is no longer needed, the user can delete it to make resources available for other purposes. Administrators can choose one of three options for a service at the end of its lease period: ignore the service lease end and notify the user, suspend the service, or delete the service. Ongoing monitoring and compliance management using CSA for Matrix Upon provisioning of a new service, Matrix communicates the IP addresses of the associated physical and virtual servers to CSA for Matrix. CSA for Matrix, through the SiteScope component, then automatically deploys infrastructure monitors for CPU, memory, and disk utilization of those servers. Easily configurable application, database, and OS monitors are also available for deployment— without installing any agents—to help ensure the availability and performance of application as well as infrastructure components. The SA component of CSA for Matrix not only enables automated application provisioning, it also enables ongoing compliance management of physical and virtual servers and applications. IT staff can establish a baseline of servers, local storage, and software and define compliance policies that govern patch levels and other configuration variables. Administrators can then run compliance checks and quickly correct configurations that do not comply with defined standards. CSA for Matrix greatly improves the speed and consistency of deploying patches and other software across hundreds of servers simultaneously using best practices and proven configurations.

Continuously optimizing the infrastructure with capacity and power management Integrated capacity and power management capabilities keep infrastructure services provisioned in HP CloudSystem Matrix running optimally. CloudSystem Matrix enables administrators to quickly rebalance and repurpose physical and virtual servers to address changing business priorities. As energy costs continue to rise, power consumption is an increasingly important consideration when planning for server consolidations or growth. Capacity planning tools and what-if scenarios help identify optimal workload placement based on projected resource utilization, power consumption, and other pertinent criteria. On an ongoing basis, built-in technologies throttle resources when not needed, keeping power consumption in line with actual server utilization. Dynamic power saver features can place power supplies in standby to keep power supply efficiencies above 90% for all normal operating conditions. Ongoing capacity management Using the integrated real-time capacity planning and workload balancing capabilities of CloudSystem Matrix, administrators can easily accommodate the varying resource requirements of an application workload. For example, varying the resources based on time of the month can address dramatic increases in peak use during end-of-month processing or a sales promotion. The capacity planning capability of CloudSystem Matrix measures the traditional resource metrics of CPU, memory, networking, and disk I/O. Matrix also measures power consumption, based on data collected every five minutes for the Matrix server blades. In the management console, administrators can view both current utilization and historical data by the type of resource. When resource utilization is low for a set of physical or virtual servers, administrators can evaluate consolidation alternatives using consolidation planning scenarios. It is helpful to understand the CloudSystem Matrix approach to analyzing capacity requirements, which is more sophisticated than simply determining the maximum memory or CPU utilization. A common practice in capacity planning is to take simply the peak of the various loads and use that to determine the maximum required peak capacity; this method is the “sum of peaks”. Although it will provide a robust solution, this method does not take into account the timing of the peaks of the loads and may end up planning for much more capacity than is actually used. A more efficient planning solution, referred to as the “peak of sums” and easily accomplished with Matrix, takes into account the timing of the maximum utilization peaks in the individual loads. By adding together utilization at each measured interval and then taking the maximum of the resulting time sequence, the “peak of sums” method used by CloudSystem Matrix results in a more accurate measure of the required maximum resource, thus reducing costs. Consolidation planning using what-if scenarios When planning for consolidation, an IT administrator can simulate the placement of server workloads prior to implementation and compare resources used under multiple scenarios, taking into account future trends. By analyzing these planning scenarios, the administrator can determine optimal workload placement. With the Matrix scenario editor, the administrator can create a baseline scenario based on an existing solution and then generate the desired number of alternative scenarios for comparison. For each of the alternatives, the administrator can apply what-if actions, for example, automated system consolidation to virtual machines. The administrator can also specify configuration parameters and include growth projections for CPU, memory, disk I/O, and networking I/O, as well as utilization limits for each of these resources. The capacity planner compares the alternatives and provides a recommended solution, including a 5-star headroom rating and projected utilization. The administrator can then run a comparison report to determine possible outcomes. For example, administrators can compare relative improvement in power consumption from various alternative

scenarios, as illustrated in Figure 9. Details of the consolidation scenarios give the administrator additional relevant data on which to base a decision regarding the best consolidation solution. The administrator can then move the workloads to the selected host and free up the server blade for other applications or power it down to save energy.

Figure 9. Consolidation planning scenario comparison report

Additionally, administrators now have the capability to easily spot the peaks of individual servers and monitor the average utilization across all servers through a peak summary report. The administrator can then view a consolidation candidate report and determine the best candidates for consolidation based on real, historical data. Finally, a cost allocation report presents utilization in percentage format, ready for further cost allocation reporting if desired. Advanced power management: dynamic power capping The dynamic power capping feature of Matrix safely limits peak power consumption without impacting system performance and without risk of over-subscribing data center branch circuits. This capability is enabled for every ProLiant server blade and blade enclosure. Administrators can set power caps for individual server blades, for groups of blades or for an entire enclosure. Embedded management and power microprocessors on each blade work together both to measure and control power usage. When enforcing the user-defined power cap, the power microprocessor first will lower the CPU P-state. If this action does not achieve the required reduction in power, it will continue to reduce CPU clock speed to prevent peak power consumption from exceeding the cap. (HP does not recommend setting a cap that would throttle performance at a single server level, blade group or enclosure level.)

When applied at the enclosure level, dynamic power capping spreads the administrator-defined cap across multiple servers, dynamically adjusting the power caps for individual server blades, based on workload intensity. The feature reduces power caps for server blades running lighter workloads and increases power caps for server blades running more intense workloads. Because workload intensity will peak and subside at different times in most environments, the ability to adjust power caps dynamically lets IT administrators set the enclosure-level dynamic power cap below the sum of peak power consumption for each blade without affecting blade performance.

Protecting continuity of services using high availability and disaster recovery capabilities With BladeSystem at its core, CloudSystem Matrix has redundant components, so the failure of a single component such as a power supply or fan does not affect operations. In addition, you can optionally configure the Central Management Server (CMS) for Matrix into a high availability clustered environment. Even if the CMS is unavailable for some reason, the CloudSystem Matrix environment (and workloads) will continue to operate in its current configuration. CloudSystem Matrix protects continuity of services by providing, enabling, or enhancing a range of availability and recovery solutions. For ProLiant and Integrity platforms, these solutions range from server-aware and application-aware availability to disaster recovery solutions for distances from campus to continental and supporting both physical and virtual server environments. A simple but powerful feature of CloudSystem Matrix is server failover: if a server fails, the application can restart on a spare server and thus be running again in about the time it takes to power on another server blade, boot the OS (which resides on shared storage), and start the application service. Failover can take place within an enclosure, within a data center, or between data centers. Failover requires no special software to be run on the servers. It can draw from a pool of spare servers, so the total number of spare servers can be less than the number of protected operational servers. Disaster recovery CloudSystem Matrix recovery management provides disaster protection for ProLiant servers and is licensed for every ProLiant server blade in CloudSystem Matrix. Matrix recovery management integrates with replicated storage environments to ensure proper transition of application data to the recovery location, restoration of storage access, and execution of the overall transition in minutes, not days. The recovery function provides push-button disaster recovery to a recovery site, and subsequent failback, enabling transfer of workloads that run on physical servers or in virtual machines. The location of the recovery site can range from a metropolitan (up to 200 km) to a continental (beyond 200 km) distance from the data center. Matrix recovery management combined with Continuous Access capabilities of HP EVA or HP XP disk arrays provides automated and seamless storage availability. Matrix also coordinates with recovery actions of other SAN storage systems, including HP 3PAR Storage Systems, through storage decoupling. HP CloudSystem Matrix allows physical to virtual and dynamic recovery models, which enables recovery to either a physical or a VMware virtual resource. The physical to virtual recovery scenario can provide cost savings by enabling consolidation of multiple physical workloads to a single virtual machine host with multiple guests. By using the dynamic recovery capability, the administrator does not have to lock in a recovery target in advance. In this scenario, the administrator can set up a workload to fail over from a physical server to either a physical server or a VMware virtual server, depending on the failover preference specified and resource availability. If the preferred (physical or virtual) server type is not available at the time of recovery, the workload can recover to an available alternative (virtual or physical) server. The automated recovery of a given workload to either a virtual or a physical environment greatly improves the cost-effectiveness of a disaster recovery implementation by enabling more flexible use of the target recovery site.

For those environments where business-critical and mission-critical availability and recovery are required, CloudSystem Matrix integrates with “application-aware” solutions to provide a faster and more granular level of solution recovery. For Integrity servers, the HP Serviceguard family of products (available through an upgrade) provides the level of mission-critical availability that customers require in these environments. Integrated with key CloudSystem Matrix technologies, Serviceguard defines “packages” that define how to start, stop, and monitor a database or any customer application along with all of the required resources. The software monitors for faults in hardware (servers, storage, and networking), in the OS, and in the application package environment. In the event of a fault, it automatically initiates a failover sequence to a new node (physical or virtual) and restores services in seconds, often completely transparently to application users. Serviceguard manages failovers within a data center and between one, two, or three data centers by using HP Metrocluster and Continental cluster technologies. Application-specific extensions and tools ease deployment and manageability through the standard configuration of popular applications in Serviceguard packages. For example, Serviceguard Extensions for SAP and for Oracle provide tight integration with SAP and Oracle RAC, delivering superior availability for these mission-critical environments. (For more information see the white paper, Wielding HP’s Serviceguard Solutions Availability Portfolio to Maintain Mission-Critical Service-Level Objectives, at http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA2-3913ENW.pdf, and listen to the podcast, HP-IT Uses Serviceguard Solutions, at http://www.hp.com/go/ServiceguardSolutions.)

Enabling technology HP Converged Infrastructure technologies at the core of CloudSystem Matrix—BladeSystem with Virtual Connect, the Matrix Operating Environment, and Cloud Service Automation for Matrix— enable the powerful capabilities just described that enable you to auto-provision, continuously optimize, and protect the continuity of an IaaS environment. This section provides more information on these and other, complementary technologies available as extensions to CloudSystem.

BladeSystem c-Class In designing the HP BladeSystem architecture, HP worked very closely with our customers to understand their requirements and challenges in managing their data centers. The resulting BladeSystem c-Class design incorporates modular and flexible compute, embedded management, network, and storage resources to provide a common, modular infrastructure that is cloud-ready and can accommodate continually changing business needs. As such, BladeSystem c-Class provides the ideal foundation for CloudSystem. Key components of this architecture include the following: • Embedded management: The Onboard Administrator management controller at the enclosure level and the HP Integrated Lights-Out (iLO) intelligent management processors in every server blade. – HP Integrated Lights-Out enables you to save time and conserve valuable IT resources by simplifying remote management. The iLO for BladeSystem processor provides graphical remote console, virtual media, and other features that yield complete remote server virtual presence. – The Onboard Administrator controller communicates with the iLO management processors on each server blade and collects and manages system parameters related to thermal and power status, system configuration, and managed network configuration. – Together, the Onboard Administrator and iLO provide intelligence throughout the infrastructure to monitor power and thermal conditions, ensure correct hardware configurations, enable health monitoring and recovery, and simplify enclosure setup and network configuration. • Shared cooling and power: HP consolidated power and cooling resources to conserve power and provide efficient cooling, while efficiently sharing and managing the resources within the enclosure.

HP uses the term “Thermal Logic” to refer to the mechanical features and control capabilities throughout the BladeSystem c-Class that enable IT administrators to optimize their power and thermal environments. HP has taken a systems approach to energy efficiency with HP BladeSystem resulting in a very efficient computing system. – High-performance, high-efficiency Active Cool fans provide redundant cooling across each enclosure. The Onboard Administrator controls these hot-pluggable fans so that cooling capacity can be ramped up or down based on the needs of the entire system. – A Sea of Sensors across every blade and within the enclosure itself ensures cooling of the entire system to meet the demand. By responding to dozens of embedded sensors within the blades and the enclosure (which are read constantly), HP BladeSystem optimizes cooling and saves energy. – 94% (Platinum level) efficiency power supplies offer the highest efficiency power supply in the market. – HP Power Regulator constantly monitors the utilization of the processors, and automatically throttles the processor input power and frequency to match the application load. You benefit from increased energy efficiency without sacrificing any performance, because the processors automatically return to full capacity whenever necessary. – HP Dynamic Power Saver mode enables more efficient use of power in the server blade enclosure. During periods of low server utilization, the HP Dynamic Power Saver places power supplies in standby mode, incrementally activating them to deliver the required power when demand increases. – Onboard Administrator allocates power to the device bays based on the specific configuration of each blade in the enclosure. The Onboard Administrator discovers each blade when it is inserted into the enclosure and allocates power accordingly, based on actual measured power requirements. • Virtualized connectivity: HP Virtual Connect technology provides a way to virtualize the server I/O connections to Ethernet and Fibre Channel networks. (See Virtual Connect.) For additional background on HP BladeSystem technologies, see the BladeSystem technical resources at http://h18004.www1.hp.com/products/blades/components/c-class-tech-function.html. HP Insight Control power management software leverages embedded BladeSystem capabilities to provide: • Power Regulator—Dynamic or static control of CPU performance and power states • Dynamic Power Capping—Reclaiming of trapped power and cooling capacity, as described in Advanced power management: dynamic power capping • Power Metering—Real-time measurements of actual power consumption to enable finding and fixing inefficiencies • Calibrated Maximum Power—A power planning tool based on accurate measurement of peak potential power for each device instead of estimates • Data Center Thermal Mapping—Generation of a thermal map of the room based on aggregating data from thermal sensors in the servers • Data Center Power Control—Protection for critical loads by reducing power to non-critical servers during cooling system failures For details on servers and OS supported by Insight Control power management capabilities, see the HP Insight Software Support Matrix at http://h18004.www1.hp.com/products/servers/management/unified/infolibrary_ic.html. For more information on HP Insight Control software, visit www.hp.com/go/insightcontrol.

Virtual Connect Virtual Connect is an essential foundation element in CloudSystem. Inherent in CloudSystem functionality and the powerful automation capabilities of its operations is the ability to move workloads from one server to another without human intervention or coordination. Virtual Connect technology enables this capability. Most LAN and SAN networks rely on the unique addresses of NICs and host bus adapters (HBAs) within each server. Replacement of a server necessitates changes to the MAC addresses and WWNs associated with network adapters and HBAs on the server and adjustments in the LANs and SANs attached to those servers. As a result, even routine server changes are often subject to delays for coordination among IT operations groups. Virtual Connect brings all of the necessary capabilities into the domain of the system administrator. Virtual Connect is a set of interconnect modules and embedded software that implements server-edge virtualization. It adds an abstraction layer between the servers and the external networks. It assigns and holds all MAC addresses and WWNs at the server bay, instead of on the servers themselves. At the addition of a new server, its NICs inherit their assigned server bay MAC addresses and the HBAs inherit their WWNs. Similarly, upon removal of a server, its replacement inherits the same addresses so that the LANs and SANs do not see server changes and do not require updating for them. Using the local Virtual Connect Manager, or the data-center-wide HP Virtual Connect Enterprise Manager software, the system administrator can preprovision and preassign to the enclosure all of the LANs and SANs that the server pool might ever need (from those predefined by the network and storage administrators)â&#x20AC;&#x201D;even before any servers are installed. SAN and LAN administrators retain sufficient control over their domains but are freed from interruptions for routine server maintenance. Through an extension of the same mechanism, Virtual Connect establishes server connection profiles for each server, and an administrator can move these profiles from one server bay to another in a single enclosure or across the data center with a single mouse click, within seconds. When these capabilities combine with boot from SAN and the Virtual Connect management tools, administrators can move application workloads from one server to another very quickly, securely, and automatically and with their storage and network configurations intact. The change is transparent to application users, because the OS image and data reside on shared storage accessible from a pool of servers. Figure 10 compares HP Virtual Connect to the traditional network model.

Figure 10. Comparison of HP Virtual Connect to traditional model Traditional Model Server changes impact LAN & SAN resources

HP Virtual Connect LAN & SAN resources remain constant as the server environment changes

NIC HBA NIC HBA NIC HBA Connect HP Virtual Modules

HBA NIC HBA NIC

HBA NIC

ENET Switch

SAN

HBA NIC

LAN

FC Switch

Server System HBA NIC

Server System

LAN

SAN

HP FlexFabric, built on Virtual Connect Flex-10 technology and HP Networking innovation, enables fully virtualized network connections and capacity from the edge to the core. This enables IT to deliver “network-as-a service,” wire connections once, and move applications freely across or between servers or even across or between data centers. HP Virtual Connect FlexFabric modules enable Matrix to connect to any Fibre Channel, Ethernet, and iSCSI network with a single device. By eliminating the need for multiple interconnects, Virtual Connect FlexFabric modules reduce network equipment needs up to 95% and the power needed to drive them by 40%. 3 Virtual Connect FlexFabric modules allocate the bandwidth of a single 10 Gb network port into up to three independent FlexNIC and one FlexHBA or four independent FlexNIC server connections. Administrators can dynamically adjust the bandwidth for each FlexNIC and FlexHBA connection in increments of 100 Mb between 100 Mb and 10 Gb. The result is network capacity applied where applications need it rather than oversubscribed everywhere. HP Virtual Connect architecture uses industry standard Ethernet and Fibre Channel for simple integration with familiar brands, such as Brocade, Cisco, and HP Networking. The Virtual Connect architecture is built into every HP BladeSystem enclosure, taking advantage of the high performance interconnect channels, integrated I/O connections, Onboard Administrator communication and control channels, and modular interconnect bays delivered as standard with HP BladeSystem. (More information on HP Virtual Connect technology is available at www.hp.com/go/virtualconnect.) HP is committed to serving the diverse needs of modern data centers without imposing a specific operating model, proprietary architecture, or network fabric. HP is continuing to build out the Converged Infrastructure vision with the addition of storage network protocols to its Virtual Connect Flex-10 technology. This combines the capabilities of Virtual Connect and Flex-10 with Data Center Bridging (DCB), Fibre Channel over Ethernet (FCoE), and accelerated iSCSI technologies to enable BladeSystem customers to use a single pair of Virtual Connect interconnect modules to access both storage and server networks. Ultimately, the HP goal is to allow IT to plug new systems into a Converged Infrastructure that will automatically discover capacity, add it to resource pools, and put it to work to support the needs of business applications. For more information on HP FlexFabric, see www.hp.com/go/flexfabric.

Matrix Operating Environment The Matrix Operating Environment provides an integrated toolkit that enables the capabilities described in How CloudSystem Matrix is used: • Visual design and automated provisioning of infrastructure services • Infrastructure optimization through advanced capacity and power management and consolidation planning • Protection of service continuity with integrated recovery management The Matrix Operating Environment (formerly known as Insight Dynamics) gives IT staff a full view and easy access to all functions to manage your Matrix infrastructure. Figure 11 shows the home page.

Based on HP analysis of networking equipment (adapters and enclosure interconnects)

Figure 11. Home page for the Matrix Operating Environment

The Matrix Operating Environment includes and is tightly integrated with HP Insight Control and enables administrators to manage HP BladeSystem c-Class blades, standalone physical servers, virtual machine hosts and guests on ProLiant and Integrity servers as well as physical hardware partitions on Integrity servers, all from a single management console. In particular, HP Insight Control delivers capabilities that enable the proactive management of ProLiant server health - whether physical or virtual, the quick deployment of ProLiant servers, optimized power consumption, and control of ProLiant servers from anywhere. The Matrix Operating Environment enables management of both physical blade servers and virtual machines as logical servers so they can be moved and migrated easily within a CloudSystem Matrix environment. It delivers a full range of deployment, management, capacity planning, migration, and movement capabilities. The Matrix Operating Environment runs on a Central Management Server (CMS). A federated CMS model permits scaling the Matrix infrastructure orchestration capabilities to manage up to four times the number of resources possible when using a single CMS. In a federated CMS environment, multiple CMSs cooperatively share management responsibility. A primary CMS, with the Matrix orchestration software installed, can direct automated provisioning of resources across multiple secondary CMSs. For more information, see the HP Matrix Operating Environment Federated CMS Overview white paper, http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA3-4721ENW.pdf.

Cloud Service Automation for Matrix HP Cloud Service Automation (CSA) for Matrix incorporates a starter edition of HP Server Automation software and HP SiteScope software. Server Automation automates lifecycle management for physical and virtual servers and applicationsâ&#x20AC;&#x201D;from establishing a baseline to provisioning, patching, configuration management, and compliance assurance. SiteScope provides agentless monitoring of infrastructure platforms and key performance indicators for applications such as CPU, disk, and memory usage. As described in How CloudSystem Matrix is used, CSA for Matrix combines with the Matrix Operating Environment to enable seamless deployment, monitoring, and management of applications along with infrastructure services in HP CloudSystem Matrix. CSA for Matrix is available as an optional, integrated solution for CloudSystem Matrix for ProLiant. Comparable functionality is available for CloudSystem Matrix with HP-UX with the addition of HP Server Automation and SiteScope software. For more information, see the HP Cloud Service

Automation for Matrix data sheet, http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA3-1176ENUS&cc=us&lc=en.

Storage technologies Key to the flexibility of the Matrix solution is having the OS image and data reside on shared storage. Logical servers can then migrate from one physical server to another and retain their personality, and continue to provide application support after reboot. For physical servers, Matrix supports preprovisioned Fibre Channel storage. Matrix can connect to your existing SAN or you can order Matrix with an HP 3PAR Storage System or an HP EVA or XP disk array. For virtual servers, Matrix supports VMware, Microsoft Hyper-V, and Integrity Virtual Machines whose boot and data storage are files within the hypervisor file system. For VMware and Hyper-V, that file system could be on local disk, FC SAN, or iSCSI. For iSCSI SAN storage solutions, HP recommends the HP P4300/P4500/P4800 G2 SAN solutions. In VMware environments, Matrix also supports hypervisor file systems on NAS and virtual machines using Raw Device Mapping (RDM) to access a FC LUN directly. RDM is a key enabler to allow a logical server to move from a physical environment to a virtual one yet still access the same boot and data volumes. For Integrity Virtual Machine environments, Matrix supports the use of SLVM (Shared Logical Volume Manager) volumes on physical FC disks. For the most current information on supported and recommended storage solutions, see the HP CloudSystem Matrix Compatibility Chart at www.hp.com/go/matrixcompatibility. HP 3PAR Utility Storage is designed to provide the agility and efficiency specifically required by virtual and cloud data centers. The integration of HP 3PAR F-Class or T-Class Storage Systems with CloudSystem Matrix provides you with a simplified way to provision and scale storage for private cloud environments. The use of thin provisioning technologies reduces overall capacity requirements and keeps utilization rates high over time, enabling you to save 50% or more on the cost of a storage technology refresh 4 . (For general information on the full benefits of HP 3PAR storage, see the HP 3PAR Utility Storage Benefits Summary white paper at http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA3-4024ENW.pdf.) The HP Storage Provisioning Manager, which is included with the Matrix Operating Environment, provides the means for a storage administrator to publish a catalog of storage volumes that can be consumed as needed, as described in Populating storage pools. This capability further streamlines the provisioning process by allowing the storage administrator to create the volumes and do SAN zoning in advance. This action in turn enables the automatic fulfillment of server administrator requests for storage, eliminating the need for the storage administrator to intervene manually each time provisioning requires storage. The storage administrator retains control of the storage catalog, storage-related processes, and permissions.

Security With the powerful capabilities to manipulate IT resources that CloudSystem Matrix provides, appropriate levels of security are imperative. The CloudSystem Matrix solution provides a consistent and integrated security management framework that you can flexibly configure to satisfy local site security policies, utilizing security mechanisms in individual components and security services across the integrated solution. CloudSystem Matrix supports numerous security mechanisms, including identification and authentication, access control, authorization and auditing, as well as use of secure practices such as secure communication protocols.

Based on deploying HP 3PAR Storage Systems and HP 3PAR Thin Provisioning and Thin Conversion Software. See â&#x20AC;&#x153;Thin Technologiesâ&#x20AC;? at http://h18006.www1.hp.com/storage/solutions/3par/technologies.html.

The security provided by the CloudSystem Matrix solution includes mechanisms to: • Ensure the confidentiality and integrity of management communications. • Log all actions that manipulate server instances in HP Systems Insight Manager (HP SIM) and other audit log files. • Provide separation of duties and role-based access control for provisioning and management. Matrix provides a great deal of flexibility for dividing administrative operations. It achieves this division through restricting login access and authorizations. Matrix uses the core authentication services provided by HP SIM, leveraging the underlying Microsoft Windows® infrastructure, including the Active Directory infrastructure if available. The Matrix solution provides authorization mechanisms that simplify the configuration and ongoing management of privileges for the various levels of users. For example, administrators can specify different levels of access to the Matrix infrastructure orchestration capabilities, administrators and users, based on their individual needs. The authorization mechanism provides the specified user with the ability to perform actions for which the individual has privileges and the graphical user interface will only display the tasks authorized for the current user. Similarly, the integrated HP Storage Provisioning Manager solution enables a storage administrator to control the visibility of pre-provisioned Fibre Channel LUNs in the storage catalog, as well as controlling which storage operations a given server administrator (or Active Directory group) can perform. HP SIM also provides an audit facility that logs entries for tasks performed by all users, including executed tasks, authorization modifications, and user login and logout. Among the methods Matrix employs to ensure secure management communications are use of the SSL (Secure Socket Layer) transport protocol and the SSH (Secure Shell) network protocol, and HTTPS (HTTP Secure) for webbased communications. For a detailed discussion of security in Matrix, see the white paper on HP Converged Infrastructure solution security at http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA28444ENW.pdf. Important extensions available for CloudSystem for security are HP TippingPoint technology and ArcSight and Fortify software. TippingPoint technology extends existing security inspection, visibility, and protection to the virtual infrastructure and delivers seamless security for the cloud. The solution enables you to deploy security policies that automatically adapt to changes in virtual environments, such as introducing a new virtual machine. It offers continuous protection of both physical and virtual assets from a single, integrated offering. The solution centers on the TippingPoint Intrusion Prevention System (IPS), an inline security appliance with full inspection of every packet of network traffic that passes through it. The TippingPoint IPS incorporates intrusion protection intelligence from HP’s security research and development organization, Digital Vaccine Labs (DVLabs). DVLabs regularly provides new filters that guard against the latest malicious attacks. For a discussion of the HP TippingPoint architecture and solution components, see the Understanding the HP CloudSystem Reference Architecture white paper at http://h18006.www1.hp.com/storage/pdfs/4AA3-4548ENW.pdf. HP ArcSight software adds cybersecurity and compliance solutions that protect organizations from enterprise threats and risks. The use of ArcSight with HP CloudSystem can help organizations safeguard physical and virtual digital assets, comply with corporate and regulatory policy, and control the internal and external risks associated with cybertheft, cyberfraud, cyberwarfare, and cyberespionage. HP Fortify software is a suite of integrated applications for identifying, prioritizing, and fixing security vulnerabilities in software and managing the business of ensuring application security. By enabling enterprises to quickly identify and fix the security holes within their software applications, Fortify dramatically reduces the risk of catastrophic attacks on applications deployed as cloud applications on the Internet and further helps ensure compliance with government and regulatory mandates.

Integrating HP CloudSystem Matrix into customer environments Because it is an open, standards-based solution, HP CloudSystem Matrix works seamlessly with your existing operating systems, hypervisors, networks, SANs, and applications. In addition, the Matrix Operating Environment integrates with HP and third-party management software and manages thirdparty servers to ensure effective management of your entire IT environment. Support for most common operating systems and hypervisors Matrix supports these native server operating systems: Microsoft Windows Server, HP-UX, Red Hat Enterprise Linux (RHEL), and Novell SUSE Linux Enterprise Server (SLES). Matrix supports VMware ESX and Microsoft Windows Server 2008 Hyper-V hypervisors, as well as Integrity Virtual Machines. For the latest and most complete information on CloudSystem Matrix compatibility, see www.hp.com/go/matrixcompatibility. Compatible with existing networks Matrix connects seamlessly to existing Ethernet networks. Because Virtual Connect is a layer-2 bridge, not a switch, it integrates smoothly with any existing network. HP Virtual Connect Flex-10 and FlexFabric interoperate with any industry standard Ethernet switch while providing 4-to-1 network hardware consolidation of the server NICs and interconnect modules. Compatible with existing SANs The HP Virtual Connect 8 Gb Fibre Channel and FlexFabric interconnects are fully compatible with all standard Fibre Channel switches. The shared storage for logical server boot and data disks can be any pre-presented FC LUN, although there are additional capabilities with HP storage solutions, such as validation of the storage definitions and the ability to import discovered volumes into the storage catalog. HP Cloud Maps for leading applications HP has collaborated with key industry-vertical and infrastructure software partners to deliver Cloud Maps for HP CloudSystem and help you fast track the development of service catalogs tailored to your environment. A Cloud Map is an easy-to-use navigation system that can save days or weeks of solution design time. Cloud Maps contain tested engineering components, such as best practice templates for hardware and software configurations, workflows, sizers, and deployment scripts, along with supporting white papers to guide customization. IT architects can import Cloud Map components into the CloudSystem designer interface to provide a starting point for creating customer-ready infrastructure services. The sizers included in the Cloud Maps for Microsoft Exchange Server and SharePoint Server automatically generate CloudSystem templates based on the solution requirements specified during the sizing process. Generating the template in this manner and importing it into the CloudSystem designer tool saves significant time in the template planning and design process. Once Cloud Map components are imported, architects can customize them to meet your specific infrastructure requirements and then â&#x20AC;&#x153;proofâ&#x20AC;? them in test and development environments before releasing them for production use.

HP Cloud Maps are available (as of the publication of this paper) for leading business applications from the following partners: • Citrix

• QAD

• F5 Networks

• Red Hat

• IBM Software

• SAP

• McAfee

• SAS

• Microsoft

• Siemens PLM

• Novell

• Symantec

• Open Text

• TIBCO

• Oracle

• Trend Micro

• PTC

• VMware

For access to the most up-to-date Cloud Map resources available for download, visit www.hp.com/go/cloudmaps. Integration with IT and business operations An embedded workflow automation engine and HP Cloud APIs enable Matrix integration with IT and business processes, as well as initiation of lifecycle operations on infrastructure services. Examples include linking into billing or chargeback systems as described in Designing the infrastructure and creating templates, and customizing the self-service portal to reflect company branding and standards. For details on available interfaces, see the white paper on Matrix integration interfaces at http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA0-9219ENW&cc=us&lc=en. Management of the extended infrastructure From the CloudSystem Matrix CMS, you can manage not only the Matrix infrastructure, but also select ProLiant, Integrity, and third-party servers that the Matrix Operating Environment manages. Supported capabilities include automated provisioning of virtual machines, capacity planning, and recovery management. For details on server models supported by the Matrix Operating Environment, see the latest HP Insight Software Support Matrix at http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02786379/c02786379.pdf (refer to the Insight Dynamics supported servers); for information on licensing requirements, see the Insight Dynamics for ProLiant QuickSpecs, http://h18000.www1.hp.com/products/quickspecs/13050_div/13050_div.html. Integrated virtualization management The Matrix Operating Environment virtualization management builds on years of experience in virtualization management with HP Integrity systems combined with HP expertise in integrated management with key virtualization partners, VMware and Microsoft. It gives IT administrators a unified method to manage both VMware ESX and Windows Server 2008 Hyper-V virtualization technologies. Matrix API integration works with tools such as VMware vCenter, vSphere, and vMotion, and with Microsoft System Center. The combined HP and partner capabilities provide robust lifecycle management of virtual environments, including automated deployment, migration, capacity and power management, health monitoring, and disaster recovery. For example, when Insight Management receives a ProLiant pre-failure hardware alert, it works with VMware vCenter to initiate the movement of all the virtual machines on that server before the failure occurs.

HP CloudSystem extensions CloudSystem extensions such as HP Tipping Point, ArcSight, and Fortify security and HP Storage build on the core technologies and capabilities to provide an optimized platform for your private cloud.

Additional extensions available for CloudSystem Matrix enable comprehensive management of your private cloud infrastructure and services. • Business Service Management software improves service quality and monitors total customer experience by integrating infrastructure, application, and end-user performance and availability management. • Storage Essentials software increases storage resource efficiency, service performance, and availability through automated discovery, mapping, monitoring, and capacity management of virtual and physical storage environments. • Network Automation software automates change, configuration, and compliance management for multivendor physical and virtual networks. For more information on CloudSystem extensions, see the Understanding the HP CloudSystem Reference Architecture white paper at http://h18006.www1.hp.com/storage/pdfs/4AA34548ENW.pdf.

Expanding beyond private cloud When you are ready to expand your private cloud infrastructure to a hybrid private/public cloud model and the full range of service delivery models (IaaS, PaaS, and SaaS), HP offers CloudSystem Enterprise—and HP Technology Services can assist you in making the transition. Like all CloudSystem offerings, CloudSystem Enterprise is built on the modular HP BladeSystem architecture and the Matrix Operating Environment, with the addition of full-featured Cloud Service Automation software. Cloud Service Automation manages the entire cloud lifecycle, including provisioning the infrastructure either through one or several Matrix Operating Environment systems, or into non-Matrix infrastructure pools; provisioning, patching, and ensuring compliance of business and complex applications; managing and monitoring the cloud; and releasing resources back to the cloud. Cloud Service Automation works with the infrastructure provisioning, optimizing, and high availability and recovery capabilities in the Matrix Operating Environment. In addition to integrated SiteScope and the Enterprise Edition of HP Server Automation with Application Deployment Manager, Cloud Service Automation includes: • CSA Foundation Server—Including an enterprise self-service portal • HP Database and Middleware Automation (DMA)—Providing a content library for database and middleware management • HP Operations Orchestration—For IT process and run book automation • HP Universal Configuration Management Database (UCMDB)—Providing a consolidated repository of physical and virtual infrastructures and services for advanced configuration management An integration module is available to import configuration data discovered by HP Insight Management into the UCMDB. The data includes relationships such as enclosure-to-blade, management-processor-to-server, and VM-host-to-VM-guest. The module also captures detailed inventory information such as serial numbers and driver and firmware versions. The data is then available to other HP Software, for example, for incident management, impact analysis, and asset tracking. Table 1 compares the orchestration capabilities of CloudSystem Matrix and CloudSystem Enterprise.

Table 1. Comparison of orchestration in CloudSystem Matrix and CloudSystem Enterprise CloudSystem Matrix

CloudSystem Enterprise

IaaS

Extend to PaaS, SaaS

Delivery at the IT level

Delivery at the line of business level

Matrix managed devices: HP BladeSystem, HP, & third party servers running VMware or Hyper-V, HP or thirdparty network, storage, & client devices

Extend to integrate services with legacy IT systems, third-party resources

Resource pool management

Matrix managed server (physical & virtual), storage, & network resources within the Matrix private cloud

Extend with management of non Matrix resource pools & aggregation of Matrix systems within & across data centers

Service design

Design and request infrastructure services through Matrix portal

Extend with service design at line of business level

Scope Supported devices

Leverage Cloud Maps for best practices Self-service portal

Primarily for IT user

Primarily for line of business user

Infrastructure: hardware, hypervisor, OS

Pre-defined service

Application (using CSA for Matrix)

Simple services view with guided options

In-depth infrastructure view with configuration options Provisioning Workflow capabilities, integration, and execution

Infrastructure with basic application deployment

Infrastructure & advanced application

Pre-defined workflows & operations

Expanded workflows & operations

Drive the Matrix pre- & post-provisioning process

Automate any type of routine/operational tasks

Example: automatically triggers approval process through integration with relevant management tools*

Examples: repetitive maintenance, change execution & incident resolution, coordinating the hand-offs across teams

lifecycle management

Integrates with existing IT environment, tools, & processes * *Additional HP or third-party licenses and/or services required

Purchase and delivery Purchasing CloudSystem Matrix begins with ordering a Starter Kit (Table 2), which includes the infrastructure needed for a working environment: • A fully-redundant c7000 enclosure • Virtual Connect modules • Software to enable all of the advanced Matrix functionality for an enclosure fully loaded with ProLiant or Integrity server blades • Hardware and software support • Implementation services Customers populate the enclosure with the desired number and type of server blades and add storage, CMS, rack, and other options.

Table 2. HP CloudSystem Matrix Starter Kits Matrix with Virtual Connect Flex-10 & FC Virtual Connect modules Software licenses

Support

Virtual Connect Flex-10 & Virtual Connect 8 Gb FC

Matrix with Virtual Connect FlexFabric Virtual Connect FlexFabric

Matrix with HP-UX & Virtual Connect Flex-10 & FC Virtual Connect Flex-10 & Virtual Connect 8 Gb FC

Matrix with HP-UX & Virtual Connect FlexFabric Virtual Connect FlexFabric

Virtual Connect Enterprise Manager for the enclosure Matrix Operating Environment for up to 16 ProLiant server blades

HP-UX VSE-OE* for up to 4 2-socket Integrity server blades

Cloud Service Automation for Matrix (optional)

Server Automation and SiteScope (optional)

3-year, 24x7 4-hour response hardware support 3-year, 24x7 software support and updates**

Blades supported

ProLiant or Integrity

Integrity or ProLiant

*HP-UX Virtual Server Operating Environment includes the Matrix Operating Environment with Integrity Virtual Machines and the right to use the HP-UX Operating System as a guest **Performing upgrade to Matrix environment requires purchase of a separate service

Customers wanting to minimize their equipment can order one of the Matrix Starter Kits with Virtual Connect FlexFabric modules. Doing so enables you to combine Ethernet and storage networks onto one converged fabric within the BladeSystem enclosure and eliminate the need for FC HBAs and interconnect modules. For traditional server edge implementations having separate networks for Ethernet and storage, the Matrix Starter Kits with Virtual Connect Flex-10 and 8 Gb FC modules are available. In all configurations, Matrix connects directly to any industry standard Ethernet and Fibre Channel networks. The CloudSystem Matrix Starter Kits with HP-UX are optimized for use with Integrity server blades. Each kit includes eight per-socket HP-UX 11i v3 Virtual Server Environment-Operating Environment (VSE-OE) licenses. VSE-OE includes the HP-UX Operating System as well as the Matrix Operating Environment for Integrity featuring the Integrity Virtual Machines. Similarly, the CloudSystem Matrix Starter Kits for ProLiant are optimized for use with ProLiant server blades. These Starter Kits include the Matrix Operating Environment licenses for 16 ProLiant server blades. HP supports mixed ProLiant and Integrity server blade environments; mixed orders require the addition of the appropriate management software licenses not included with the Starter Kit. A Windows-based CMS hosts the Matrix management softwareâ&#x20AC;&#x201D;the Matrix Operating Environment, consisting of Matrix infrastructure orchestration, Matrix capacity planning, and Matrix recovery management for ProLiant, as well as Insight Control (with HP SIM), Virtual Connect Enterprise Manager, and Storage Provisioning Manager. HP offers the ProLiant DL360 G7 as the recommended option for a CMS. Using this rack-mount server rather than one of the server blades allows you to use all available and licensed enclosure blade bays for managing target blades and workloads. Though the ProLiant DL360 G7 is the recommended default CMS option, you can substitute any other server of your choice provided the server matches the Insight Management CMS requirements (see the HP Insight Software Support Matrix at www.hp.com/go/matrixoe/docs). Customers purchasing Matrix Starter and Expansion Kits have the option of including the HP CSA for Matrix software for important IaaS capabilities such as basic application deployment and monitoring and automated patching and compliance. Customers purchasing Matrix Starter and Expansion Kits with HP-UX can add HP Server Automation and SiteScope for these IaaS capabilities. CloudSystem Matrix with HP-UX allows seamless upgrades of the HP-UX VSE-OE to the HP-UX Data Center

Operating Environment (DC-OE). Upgrading to DC-OE adds HP Serviceguard for mission-critical high availability and disaster recovery. Fibre Channel storage options from HP include the HP 3PAR F-Class and T-Class Storage Systems and HP EVA and XP FC arrays 5 . For iSCSI SAN storage, HP recommends the HP P4000 G2 SAN solutions. Matrix also supports third-party FC SANs; for details on the SANs supported, see www.hp.com/go/matrixcompatibility. You can scale the capacity of the Matrix infrastructure by ordering one or more Expansion Kits, either with the initial Matrix purchase or as needs grow. Table 3 shows recommended small, medium, and large configurations for CloudSystem Matrix using ProLiant and Integrity server blades. Table 3. Recommended configurations for CloudSystem Matrix for ProLiant and CloudSystem Matrix with HP-UX SMALL

MEDIUM

LARGE

ProLiant configurations Servers

Matrix Starter Kit

8 ProLiant Server Blades

16 ProLiantServer Blades

3 Expansion Kits

DL360 CMS

64 ProLiant Server Blades DL360 CMS

Storage

EVA Storage 5.4 TB*

3PAR Storage 9.5 TB*

3PAR Storage 48 TB*

Matrix Operating Environment

Software

CSA for Matrix* 3rd Party Extensions: VMware or MS Hyper-V * CloudSystem Matrix Implementation Service

Services

Cloud Consulting & Implementation Services**

Integrity configurations Servers

Matrix Starter Kit with HP-UX

Matrix Starter Kit with HP-UX (fully populated)

4 BL860c i2

4 BL870c i2

Expansion Kit with HP-UX (fully populated) 4 BL890c i2

Storage

EVA Storage 5.4 TB*

3PAR Storage 55 TB*

3PAR Storage 111 TB*

Software

8 VSE-OE licenses with Matrix OE

16 VSE-OE licenses with Matrix OE

32 VSE-OE licenses with Matrix OE

Server Automation Starter Edition*

SiteScope*

Services

CloudSystem Matrix Implementation Service Cloud Consulting & Implementation Services**

*Optional components, may require additional hardware **Optional services

Every Matrix Starter Kit comes with an on-site implementation service that will ensure the integration of the Starter Kit, as well as up to four Expansion Kits purchased with the Starter Kit, into your environment (power, network cabling, for example). Matrix Expansion Kits purchased after the initial CloudSystem Matrix Starter Kit order include the CloudSystem Matrix Expansion Kit Integration

HP EVA and XP disk arrays can be factory integrated with Matrix.

Implementation Service. Each implementation service will integrate up to four Matrix Expansion Kits into an existing Matrix customer environment. For details on ordering a Matrix solution, see the Quick Specs for Matrix at http://h18004.www1.hp.com/products/quickspecs/13297_div/13297_div.html and the Quick Specs for Matrix with HP-UX at http://h18004.www1.hp.com/products/quickspecs/13755_div/13755_div.html.

HP services to make the most of CloudSystem HP CloudSystem implementation services facilitate fast and reliable deployment and startup of your CloudSystem solution. All HP CloudSystem Matrix Starter and Expansion Kit orders include factory services to: • Configure, rack, and cable the infrastructure. • Verify and update firmware for the entire solution being purchased (the CloudSystem Matrix kits and the supported blades and options purchased with those kits) to the latest current CloudSystem Matrix firmware release set. • Coordinate hand-off to Technology Services (TS) or an authorized partner. An assigned TS or partner project manager manages pre-engagement planning, and assigns a team of engineers to perform the implementation service at your site. Implementation services include unpacking and inspection; integrating the hardware to the customer environment, including power and network cabling; installation and configuration of the CMS and other required software; and CloudSystem Matrix solution orientation. In addition to the all-in-one implementation services integrated with CloudSystem Matrix, HP Technology Services offers an extensive portfolio of cloud and virtualization consultant services as well as warranty upgrades and support services for all stages of the lifecycle, including infrastructure design, deploy, test, integrate, migrate, upgrade, and ongoing support. HP Technology Services can tailor an offering to help you achieve your specific goals. Additional services available include: • Proactive Service Solutions: HP Mission Critical Services provide integrated proactive and reactive solutions to help you operate more efficiently and sustain the availability of your environment. These solutions include services such as Critical Advantage to manage your critical IT infrastructure. HP experts mitigate people, process, and technology-associated risks while increasing operational efficiency. • Education Services: Innovative HP training solutions help keep your staff up to date on CloudSystem, virtualization solutions, IT management, and topics related to Microsoft, Linux, VMware, and Citrix. (For more information, visit http://h10076.www1.hp.com/education/.) • Converged Infrastructure Services: These services help you implement a shared services model, whether you plan to make the make the move incrementally or undertake a complete data center transformation. Offerings include visioning workshops, needs assessments, data center design, operations assistance, and implementation assistance. The HP Converged Infrastructure Maturity Model (CI-MM) helps you assess the current and desired future state of your data center. CI-MM uses a set of metrics, based on research and industry best practices, to help align business and IT objectives and output an action-oriented roadmap for meeting those objectives. Cloud Discovery Workshop The HP Cloud Discovery Workshop is a one-day, strategic workshop that helps facilitate faster decision making and cross-team collaboration—so that you can shape your own cloud path. Through an interactive session and informative visual displays, HP experts share their experience, explain the

possibilities, risks, and business implications of the cloud, and make recommendations for using the cloud. Business and IT stakeholders have an opportunity to discuss cloud concepts, service portfolio concepts, governance, security, business case issues, and HP solutions. For details, see the service brief at http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA3-2331ENW.pdf. Matrix TCO Calculator The Matrix TCO Calculator 6 is an online tool designed to generate TCO estimates over a three-year period. The tool enables comparisons of each step in the move toward a CloudSystem Matrix environment including: rack servers to Matrix; server blades to Matrix; server blades to blades with HP Virtual Connect FlexFabric technology; and server blades with Virtual Connect FlexFabric technology to CloudSystem Matrix. The tool allows you to customize inputs to compare the relative costs of specific infrastructure configurations. Access the tool at http://roianalyst.hp.com/bladesystemmatrixtco/launch.html. HP CloudStart Solution Built on HP CloudSystem Matrix, the HP CloudStart Solution (currently available for ProLiant servers only) is a pre-integrated, turnkey solutionâ&#x20AC;&#x201D;consisting of hardware, software, and servicesâ&#x20AC;&#x201D;that simplifies and speeds up the launch of your private cloud. With CloudStart you can be delivering private cloud services within thirty days after hardware and software installation. As part of HP CloudStart, HP consultants will help you plan and define up to four cloud services. They will help you implement security, backup, chargeback and automation policies so your services can be available quickly. HP CloudStart is also extendible and can be customized to the unique needs of your organization. HP CloudSystem Matrix Conversion Services If you have already invested in HP BladeSystem or HP VirtualSystem (highly optimized, turnkey server virtualization) solutions, you can protect and build on this investment with HP CloudSystem Matrix Conversion Services. These services, performed by HP Services experts, let you move from the HP BladeSystem investment you already have, to a complete HP CloudSystem Matrix environment. The resulting converted HP enclosures and server blades will enjoy the full functionality and full support of the HP CloudSystem Matrix environment. For details, see the data sheet at http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA3-2191ENW.pdf. For more information on HP Technology Services, visit http://www8.hp.com/us/en/services/itservices.html.

Ready capacity when business demands To help you ensure that resources are available at all times to meet even unanticipated business demands, HP CloudSystem provides dual bursting capability. The capability allows enterprises to dynamically scale and provision IT resources, either locally through an onsite pay-as-you-use cloud model or externally through a public cloud provider. For local bursting, CloudSystem combines with HP Utility Ready Computing service to enable rapid deployment of pay-per-use infrastructure resources that reside on your site. You pay for the resources only when they are in use through a monthly billing based on metered usage at a fixed price per blade per hour. You can ensure that capacity is configured and available instantly when business needs demand it, yet reduce the risk of investment in underutilized equipment. The Matrix Operating Environment simplifies implementation by automatically powering resources on and off as needed. For external bursting, you can access external resources, either by establishing a virtual private cloud environment through an authorized HP service provider or through a public bursting service we are 6

Developed for HP by Alinean, Inc.

planning to offer through HP certified bursting partners. CloudSystem enables you to activate external resources by simply selecting the virtual private cloud or public cloud services from the infrastructure self-service portal. For details on the HP Utility Ready Computing service, visit www.hp.com/go/utilityreadycomputing. For more information on the HP CloudSystem dual bursting capability, see the news advisory at http://www.hp.com/hpinfo/newsroom/press_kits/2011/HPDiscover2011/DISCOVER_CloudSystem _Adv.pdf.

Summary and conclusion Moving to a model of delivering infrastructure as a service and establishing a private cloud can help IT regain control while responding to ever-increasing business demands. HP Converged Infrastructure helps you realign traditional technology silos of server, storage, and network resources into pools of virtualized and integrated assets. These resource pools can be shared by many applications, optimized, and managed as a service. This accelerates delivery of IT services and simplifies ongoing infrastructure management. HP CloudSystem Matrix, the entry offering of the HP CloudSystem portfolio built on HP Converged Infrastructure technologies, provides the ideal platform for your private cloud and infrastructure as a service. The HP CloudSystem portfolio, including Matrix, together with CloudSystem Enterprise and CloudSystem Service Provider, provides IT with a unified way to build, provision, and manage services across private clouds, public cloud providers, and traditional IT solutions.

Appendix A: Implementing a private cloud As IT departments witness their business units attempting to fulfill their IT requirements by going straight to the public cloud, they are seeking ways to regain control. They want to put in place private cloud solutions that match the perceived speed, flexibility, and affordability of the public cloud yet provide better security and integration into the enterprise. To achieve this objective, the basic requirements that the private cloud must satisfy include the following: • Self service delivery on demand—A business unit should be able to view a selection of standardized services and initiate deployment as needed. • Single governance & security model—Mechanisms must be in place to minimize business risk. • Automated metering & chargeback—A business unit must be able to see the costs for the services. • Instant scalability with mission critical availability—Services must be able to scale as business needs grow. • Optimization for business applications—A private cloud could excel in this area over public cloud offerings. • Openness and extensibility—These attributes are necessary to achieve integration with the enterprise. Implementing a private cloud can be a complex and daunting task. HP has built CloudSystem Matrix to simplify and accelerate just such a task. As discussed in this paper, the capabilities of Matrix—with its tool for designing standardized services, self-service infrastructure portal, automated provisioning, and shared resource pools that can be dynamically scaled—enable you to move quickly to a private cloud model in which users can provision services in minutes. Integration with HP CSA for Matrix allows you to design application services that fit your business. Matrix integrated management tools help you optimize resources and deliver on the requirements for security and service availability. Embedded workflows and included Cloud APIs enable you to connect your private cloud to your chargeback system and incorporate other established business and IT processes. HP Cloud Maps provide a wealth of resources to get you started in implementing your private cloud. For customers wanting additional assistance, HP has introduced Cloud Consulting Services, including the HP CloudStart solution designed to achieve a private cloud solution in less than 30 days after hardware installation and start-up. (See http://h20219.www2.hp.com/services/us/en/consolidated/cloud-overview.html.)

Appendix B: HP CloudSystem Matrix use cases This section contains a selection of use cases that show how CloudSystem Matrix can help address common IT challenges. Your organization may benefit from the solutions described in one or more of these use cases and detailed in the references provided.

Increasing availability of infrastructure services during planned downtime This use case illustrates how an organization can increase availability of infrastructure services during planned or unplanned downtime by freely moving workloads between servers in CloudSystem Matrix. In this case, one of the Matrix servers, a ProLiant BL465c server blade running a mail and messaging application, needs a memory upgrade.

Through the Matrix Operating Environment the server administrator: • Obtains system information for the server blade and observes the current utilization of the server blade. By performing the move while the system load is low, the administrator minimizes impact on users of the application. • Evaluates and selects a suitable target to accept the workload. The Matrix software displays available server blades. In this case, a BL465c and a BL460c are available. The BL460c has more headroom (indicated with a 5-star rating), but the BL465c has a 4-star headroom rating and is the same type of server blade on which the mail application is currently running. • Initiates the move operation. The software deactivates the original server and moves its profile to the selected target blade. Within a few minutes, the mail and messaging workload is activated on the new server. • Monitors the progress of the operation in real time. The administrator has the option to proceed with other work, since no user interaction is required. With the workload moved to the new server, the mail and messaging service remains available to users with virtually no interruption. The administrator can commence the maintenance on the original server blade. Once the hardware maintenance is complete and the administrator identifies an appropriate time, a similar process can be used to move the workload to the upgraded server. For a step-by-step guide and demo video for this use case, see http://h18004.www1.hp.com/products/blades/components/matrix/guides.html#ha.

Dynamic infrastructure provisioning and reprovisioning for an agile test and development environment Using CloudSystem Matrix, administrators can create a multitier test and development infrastructure using physical servers and virtual servers. Matrix can then rapidly activate and deactivate a test and development environment and repurpose infrastructure quickly without reinstallation. Sharing and pooling resources improves utilization and reduces cost. The IT team can create a logical server for each application test environment, provision each logical server once, and then, when priorities change, deactivate logical servers no longer in use. A deactivated logical server does not consume server resources such as CPU, memory, or power, but its profile, including associated SAN storage, is retained so that it can be quickly reactivated in about the same time as it takes to boot the operating system. For a step-by-step guide and recorded demo documenting this scenario, see http://h18004.www1.hp.com/products/blades/components/matrix/guides.html#di.

Ongoing optimization and consolidation with energy awareness The real-time capacity planning capability of Matrix enables rapid rebalancing and repurposing of physical and virtual servers to address changing business priorities. As resource requirements of application workloads lessen, an administrator can dynamically consolidate these workloads onto fewer virtual machine hosts to allow for better utilization of the existing server blade hardware. The administrator can either temporarily power off any physical server blade no longer needed after the consolidation, to save energy costs, or quickly and easily repurpose it. Two use cases illustrating this scenario are documented in step-by-step guides and demo videos, one using VMware ESX virtual machines and another using Microsoft Hyper-V virtual machines. See http://h18004.www1.hp.com/products/blades/components/matrix/guides.html#cc. Matrix real-time capacity planning capabilities also enable consolidation of workloads in an energyefficient manner. The use of capacity planning scenarios and scenario comparison reports makes it

easy to compare energy consumption of different data center configurations, enabling better use of power, cooling, and space resources. For details on this use case, see the step-by-step guide and recorded demo at http://h18004.www1.hp.com/products/blades/components/matrix/guides.html#ea.

Flexible management of secure mission-critical workloads in hybrid cloud environments This use case illustrates how an organization can manage global mission-critical workloads with CloudSystem hybrid cloud capabilities for maximum security and resource flexibility. In this case, a company deploying a global ad campaign uses an HP Integrity BL860c i2 server blade with HP-UX operating environment, Oracle Database for the database tier on physical servers, and a Proliant BL460c running VMware and Windows OS for the web tier. The Matrix Operating Environment with HP-UX provides a single integrated platform to deploy mission-critical applications. CloudSystem Matrix with HP-UX hosts the critical database workload within a private cloud to ensure data security and the robust resiliency required while simultaneously deploying non-mission-critical workloads in a public cloud environment. The result is full hybrid cloud flexibility and TCO enhancement. • CloudSystem allows you to set custom or compliance-oriented policies to specify where you host your mission-critical data, such as HR or customer data, each time a user deploys a service. • HP-UX provides a secure, mission-critical infrastructure tightly integrated with Serviceguard solutions to deliver the highest resiliency to meet requirements of SLAs (service level agreements). A use case illustrating this scenario is highlighted in a video demo at http://h20324.www2.hp.com/SDP/Content/MainPlay.aspx?Id=2854&booth=48.

Appendix C: HP Cloud Maps—an example This example shows how a typical enterprise can make use of HP Cloud Maps with CloudSystem Matrix to create a catalog of templates for provisioning infrastructure services. This example, based on industry best practices, describes the design of a complex multitier service running Microsoft Exchange Server 2010 for 5000 users with 1 GB mailboxes. The design conforms to the gold tier service classification of the HP tiered solution program for Microsoft Exchange Server 2010. For the gold tier, each of the Exchange roles (Mailbox, Client Access, and Hub Transport) resides on a dedicated physical server or virtual machine. For redundancy, a second dedicated server or virtual machine (located on a separate server) is configured for each role. The two mailbox servers are configured in a database availability group (DAG) with two copies of the databases providing mailbox server resiliency if an active mailbox server fails. The resources for this service include: • Virtual machines for Exchange Client Access servers • Virtual machines for Exchange Hub Transport servers • Physical servers for Exchange Mailbox servers • Production networks • Management network • Replication networks • Storage resources The HP Cloud Map for Microsoft Exchange Server 2010 (see http://h71028.www7.hp.com/enterprise/us/en/partners/cloudmaps-microsoft.html) includes a

template, sizer, workflow, and scripts, as well as white papers describing how to use and customize the template and workflow. The import function of the Matrix designer interface enables the architect to accelerate the design process by starting with the provided Cloud Map template for Exchange (Figure A-1) and making modifications needed to complete the design and customize it for the customer environment.

Figure A-1. HP Cloud Map reference architecture infrastructure template for Microsoft Exchange service

The architect can also use the HP Sizer for Microsoft Exchange Server 2010 to derive customized requirements and generate a template based on these requirements. In this example, the architect generates a recommended configuration using the following starting requirements: • Number of Mailboxes: 5000 • Mailbox Size: 1000 MB • Workload Definition: 20 sent and 80 received • Tiered Solution Level: Gold • Total number of database copies: 2 • Additional mailbox servers to add fault resilience: 1 • Number of database copies in secondary site: 0 • Server Platform: Blade

• Processor Vendor: Sizer recommendation • Server: Sizer recommendation • Storage Architecture: SAN—Fibre Channel • Array Type: Sizer recommendation Using these entries, the sizer for produces recommended configurations for each of the Exchange server profiles and associated storage, including server processor and memory requirements, size, type, and RAID level for internal and external storage. The sizer provides the option to generate a template (as an XML file) based on these configurations for import into the Matrix designer interface. The architect can then complete the imported template in the Matrix designer by setting the OS deployment jobs, adding required network resources, and completing any optional customization steps. The template is then ready to be saved and published. By following similar steps, the architect can create a catalog of service templates from which users can provision the infrastructure services needed.

Glossary of terms Allocation—The process of assigning server, storage, and network resources to a service request based on the criteria defined in the service template, the resource pools assigned to the user, and the current reservations or allocations of resources completed as part of infrastructure orchestration by the Matrix Operating Environment. Approval—Action by an administrator for a service request submitted by a self-service user, required before the provisioning of the service can commence. API—Application programming interface. Central management server (CMS)—A system in the management domain that hosts and executes the HP SIM software. All central operations within HP SIM are initiated from this system. Cloud APIs—A set of web service interfaces provided by HP to permit customers, partners, and integrators to integrate Matrix infrastructure orchestration capabilities into their business and IT operations processes or to combine with their own offerings to provide new capabilities. HP has submitted these interfaces to the Distributed Management Task Force (DMTF) Cloud Management Working Group in support of an industry open standard cloud services API. See also API. Cloud computing—A delivery model for technology-enabled services that provides on-demand access to an elastic pool of shared computing assets. These assets include applications, servers, storage, and networks. The entire pool can be rapidly provisioned and scaled up or down as needed on a pay-per-use basis. In other words, these assets can be consumed “as a service.” Cloud computing deployment models include private cloud; public cloud—in which provider-owned assets are shared, and service is provided on a pay-per-use basis to multiple entities; and hybrid cloud— which combines public cloud, private cloud, and traditional IT. See also private cloud, IaaS, PaaS, SaaS. Cloud Map—An HP navigation system for use in creating service catalogs. HP Cloud Maps contain engineering components such as best practice reference architecture templates, workflows, sizers, and deployment scripts, as well as supporting white papers to assist with customization. Cloud Service Automation for Matrix—Integrated software, based on HP Server Automation starter edition and HP SiteScope, that enables seamless infrastructure and application deployment and provides application monitoring and lifecycle management for physical and virtual servers and applications. Continuous Access—Array-based applications that provide synchronous or asynchronous data replication over distance between HP Enterprise Virtual Arrays and between XP Disk Arrays. FlexFabric—HP virtualized, high-performance, low-latency network architecture for Converged Infrastructure. HP FlexFabric consolidates Ethernet and storage network protocols into a single fabric. IaaS---Infrastructure as a service. Cloud model in which the computing infrastructure, including physical and virtualized servers, storage, and networking, is delivered as a service. See also cloud computing. Infrastructure orchestration—The set of processes, enabled by the Matrix Operating Environment, for designing, provisioning, and managing infrastructure services. The software includes an embedded workflow automation engine powered by HP Operations Orchestration software. The Matrix Operating Environment defines and enables three distinct orchestration roles: Architect—Uses the infrastructure orchestration graphical design tool to develop, test, and publish service templates that capture the requirements to provision infrastructure services. The architect specifies attributes for the logical resources, may author and attach workflows, and may make

use of HP Cloud APIs to integrate business processes. See also Cloud APIs, service template, workflow. Administrator—Uses the infrastructure orchestration console to create pools of servers and storage, manage the available networks and software inventory, approve user requests, and modify user service infrastructures. The administrator may also perform manual tasks within a semi-automated operation. See also resource pools. User—Uses the infrastructure orchestration self-service portal to request infrastructure services by selecting a service template, selecting one or more assigned resource pools to use, and specifying a lease period for the start and end of the overall service. During the lease period the user can update the service. See also lease period, service request. Infrastructure service—A running configuration of infrastructure resources that supports a business application such as a multitier web application. Infrastructure resources include server blades, virtual machines, SAN disks, networks, and IP addresses. It is also referred to as a service or service instance. CloudSystem Matrix provides lifecycle management of such a service, including start and end controls, ability to extend service period and accompanying resource allocation, or adding server or storage resources per template definition. Lease period—The duration, or lifetime, of an infrastructure service. The user sets or changes the lease period. Logical server—A management abstraction defined by a server profile that describes the system resources needed for a given OS, application, and workload to operate. For example, a profile includes resource specifications such as processors and memory and unique identifiers such as Media Access Control (MAC) addresses and World-Wide Names (WWNs). A logical server profile can be created for a physical server or a virtual machine and moved across physical or virtual machines. Logical servers allow administrators to manage physical and virtual machines using the same management construct. (For more information on logical servers, see Introducing logical servers: Making data center infrastructures more adaptive, http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01402013/c01402013.pdf.) Matrix Operating Environment—(previously Insight Dynamics) A shared services management platform that automates infrastructure lifecycle management. It enables optimization of server, storage and network resources in compliance with core business, security, and regulatory policies. PaaS—Platform as a service. Cloud model in which an entire computing platform, including infrastructure and a solution stack and development platform, is delivered as a service. See also cloud computing. Primary site—The site where all logical servers being managed by Matrix recovery management are activated. See also recovery management. Private cloud—A cloud computing deployment model in which cloud assets are operated solely for a single entity. The assets may be located on or off premises and may be owned and managed by that entity or by a third party. Provisioning—The process within Matrix of creating an infrastructure service from a template. The Matrix software searches its inventory before allocating the infrastructure resources to all logical resource definitions in the template. Recovery management—Function of CloudSystem Matrix software for ProLiant servers that provides automated disaster recovery of physical and virtual logical server environments, enabling the transfer, or fail over, of workloads to a recovery site. Recovery management integrates the replication capabilities of HP storage environments. Recovery management identifies recovery groups, a pairing of one or more logical servers, and a single Storage Replication Group. During a site failover, recovery groups are failed over from the primary site to the recovery site in a preestablished order. See also primary site, recovery site. Recovery management for HP-UX-based Integrity servers is available through an upgrade to HP Serviceguard disaster recovery solutions.

Recovery site—The site to which all recovery groups are failed over during disaster recovery. See also recovery management. Resource pools—A group of physical and virtual infrastructure resources. An administrator controls resource utilization by allowing users access to one or more resource pools. Server group—Defined in a service template, a set of one or more servers with the same role that can be treated as a tier, enabling the construction of a multitier infrastructure service. Service request—Online submission by a user through the Matrix self-service portal to initiate provisioning and ongoing changes to the infrastructure. Users can monitor and cancel requests. Requests can be approved, rejected, canceled, or continued by administrators. Service template—A design blueprint that specifies the requirements for an infrastructure service in terms of server groups, networks, and storage, and contains customization points that use workflows during the execution of a request. A template may also include the application for the service. See also infrastructure service. SaaS—Software as a service. Cloud model that makes available as a service the infrastructure, the platform, and the software applications running on that platform. See also cloud computing, IaaS, PaaS. Workflow—A set of actions that execute customer-specific IT tasks. Workflows can define integration with IT processes, including approvals, manual OS deployment, manual storage provisioning, and notifications. Making use of the workflow automation engine embedded in CloudSystem Matrix (powered by HP Operations Orchestration software), architects can associate workflows with service templates, to be executed before or after provisioning (or both), based on the associated templates. Examples include workflows to update a configuration management database (CMDB) or open a change request in a ticketing system at precise points within the provisioning or other infrastructure service lifecycle workflow.

For more information For more information on HP CloudSystem Matrix see: www.hp.com/go/cloudsystem www.hp.com/go/matrix www.hp.com/go/insightsoftware www.hp.com/go/convergedinfrastructure

Share with colleagues

ÂŠ Copyright 2010-2011 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 U.S. registered trademarks of Microsoft Corporation. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. 4AA0-5550ENW, Created February 2010; Updated August 2011, Rev. 2