Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and Savvis

CloudSystem Matrix bursting to Savvis
Initially, HP CloudSystem Matrix 7.0 can burst to Savvis, an HP CloudAgile Service Provider partner and approved
HP CloudSystem bursting destination. Savvis is a managed hosting and cloud services provider capable of meeting
dynamic customer demand for outsourced IT and cloud services. Savvis is a global cloud provider, with datacenters
in the US east, US west, EMEA, and Asia. The company offers Savvis Symphony Virtual Private Data Center (VPDC)
solutions that feature multi-tiered security and a set of predefined service levels.
Over the coming months and years, look for an expanding ecosystem of bursting destinations that will include HP
Cloud Services, additional HP CloudAgile bursting partners, and other service providers.
CloudSystem Matrix bursting to Savvis concepts and capabilities
Inventory
 Savvis resources appear to CloudSystem Matrix infrastructure orchestration as pools with unlimited capacity.
Cloud Resource pools do not have an upper capacity (unlike VM Hosts, which can run out of memory and disk
space). Consequently, if a logical server definition is valid for the cloud provider, it can always be provisioned to
the cloud.
 Resources accessible via a Savvis account are represented as a Cloud Resource inside of Matrix. This Cloud
Resource can be added to a resource pool like any other VM Host or ESX Resource Pool.
 A Savvis Cloud Resource comprises its own infrastructure orchestration pool.
– CloudSystem can burst to any number of Savvis accounts
– For a single Savvis account, there can be multiple VPDCs in Savvis and multiple Savvis cloud pools in Matrix
– Savvis Cloud Resources can be inserted into any number of different server pools
– A single server pool cannot include both internal cloud resources and Savvis Cloud Resources, and multiple
Savvis Cloud Resources cannot be included in one server pool
Access
 Access to Savvis server pools is assignable to user groups, in the same way that access to internal server pools is
managed.
 Savvis account credentials are associated with a Cloud Resource. The account used is determined by the Cloud
Resource selected during allocation.
Allocation policy
 The user selects server pools and specifies the pool list order. Servers are provisioned to the first server pool that
can accommodate the needs of all servers in a group. If a Savvis pool can satisfy the needs of a server group
and is the first pool in the list, the server is provisioned to Savvis. If a Savvis pool is not the first pool in the list of
selected pools, Savvis is used only if previous pools are unable to accommodate the server group.
 All servers in a server group are provisioned within the same cluster or the same Cloud Provider. Multiple server
groups can have some groups provisioned in the Matrix environment and others in an external cloud.
VM provisioning
 Operating system image is deployed
 Data disks are added
 Servers are added to the Savvis network
 Progress is monitored, and status reported as for on-premise
Networking
A logical server is limited by Savvis to connect to only one network.
Software mapping
 Matches a CloudSystem software template to an analogous Savvis deployment image
 Accommodates differences in the name, format, and content of images used by CloudSystem and Savvis. For
example, CloudSystem VM templates are mapped to corresponding images in the Open Virtualization Format
(OVF) that Savvis uses; HP servers employing hypervisors not supported by Savvis can be mapped to Savvis
images that rely on Savvis-supported hypervisors. This allows customers to deploy services to Savvis regardless of
whether the template was initially designed for on-premise deployment of ESX virtual machines or Hyper-V virtual
machines. (Note that VMware software is required to create the client provided OVF images that are uploaded
to Savvis.)