HP released this great technical white paper that provides in-depth information on how to use a CSA environment to federate multiple Matrix OE managed data centres across multiple regions of the globe.
The paper explains how to expose CSA services in a consumer catalogue, in which the deployment is an option.
A custom CSA provider selection mechanism is then used to dispatch the service provisioning on the selected Matrix OE platform.
The paper also describes how the CISS demo, HP CloudSystem Enterprise: Federating Multiple Matrix OE’s with CSA, was created and is good background reading to fully understand what happens behind the scenes.f
You can find the whitepaper here: URL
Some more information on MOE and CSA:
The HP Cloud strategy – HP Converged Cloud – was designed to provide solutions in 3 key areas:
– Public Cloud with HP Cloud Services (www.hpcloud.com)
– Managed Cloud
– Private Clouds
– Managed Cloud
– Private Clouds
This strategy allows HP to be uniquely positioned today, as the sole provider of Hybrid Cloud solutions.
The key product in the Private Cloud space, is called HP Cloud System, and is available in 3 flavors:
– HP CloudSystem Matrix, a turnkey solution including software and hardware to build a Private Cloud in a short amount of time using components of the HP Converged Infrastructure such as HP BladeSystem, HP VirtualConnect, HP 3PAR storage and the Matrix Operating Environment (MOE) software stack to control the entire package
– HP CloudSystem Enterprise which includes several software packages to what HP CloudSystem Matrix already offers, such as HP Cloud Service Automation (CSA), HP Server Automation (SA), HP SiteScope, HP uCMDB
– HP CloudSystem Service Provider which adds to these two packages a Telco oriented aggregation layer
HP CloudSystem Matrix includes a set of hardware components and a software stack often referenced as MOE for Matrix Operating Environment.
On its own MOE handle enough functionality to build an IT centric private Cloud. MOE is particularly well suited for what is often referred as IaaS (Infrastructure as a Service). The most important components of the solutions are:
– A Service Template designer (a.k.a. HPIO Designer) which allows a solution architect to build an infrastructure service template, by assembling compute resources (virtual, physical, both) from different virtualization vendors (Microsoft, VMware, HP, RedHat), storage resources and network resources.
– An administrative console (which plugs in HP Systems Insight Manager) to control the pools of compute, storage, and network resources, and the private Cloud roles and responsibility, in a multi-tenant way. This is also the place where Service Templates are assigned to organization (or tenants), and made available in their service catalog.
– One or more tenant administrative console, in the case where multi-tenant is configured, then MOE handle some level of delegation to organization administrator using a dedicated portal.
– One or more tenant user portal, where end users of the cloud (line of business managers, IT managers) can login and order, automatically provisioned services from their catalog.
– A workflow engine called HP Operations Orchestration (HP OO), which allows a solution architect to extend the behavior of MOE by graphical programs (workflows), added to a service template and automatically (headless) executed by MOE during a provisioning.