Cloud bursting with HP CloudSystem Matrix infrastructure orchestration: Matrix-to-Matrix, HP Matrix KVM Private Cloud, HP Cloud Services, and Amazon EC2

Inventory
• Resources accessible via provider accounts are represented as Cloud Resources inside CloudSystem Matrix. Cloud Resources
can be added to a server pool in the same way as any other VM Host or ESX Resource Pool.
• Capacity limits are enforced by the provider and limit-related errors can be reported during provisioning. The cloud provider
account holder must apply to raise resource limits, if necessary, to meet the needs of services to be provisioned.
• Each Cloud Resource corresponds to a single cloud provider region and user account.
• A CloudSystem server pool can include either on-premise resources or external Cloud Resources, but not both.
• External cloud provider-hosted software images are displayed in the CloudSystem software inventory. When using HP Cloud
Services server images or Amazon Machine Images (AMIs), you can choose from the collection of pre-existing, publicly
available images and optional private images you create in your account. An image filter configuration determines which
images are visible to CloudSystem.
Server types
• Cloud providers generally limit server configurations to a discrete set of server types. A server type (called “flavor” in HPCS
and “instance type” in EC2) defines the processor and memory characteristics for the server, and other attributes, such as
processor architecture.
• A server type can be explicitly specified in a template, as the Cloud Server Type, or can be selected automatically by Matrix
infrastructure orchestration based on the server memory and CPU configuration in the template.
Allocation
• CloudSystem uses an allocation policy to determine where to provision resources. Moving through the ordered list of server
pools selected by the user, CloudSystem allocates resources from the first server pool that can accommodate the needs of all
servers in a server group. This allocation step is repeated for each server group described in the service template, and the
service can be deployed when all server groups have been through the allocation process.
• All servers in a server group are provisioned to the same Cloud Resource. A template with multiple server groups can have
some groups provisioned in the CloudSystem environment and others in a public cloud.
• Cloud servers in a server group optionally share a firewall (security group. A firewall controls inbound network access. (This
feature might not apply in a Matrix-to-Matrix server group.)
Account access
• Provider account credentials are associated with a Cloud Resource. The account used for the provisioning of a particular
server is determined by the Cloud Resource selected during allocation.
• CloudSystem can burst to multiple provider accounts.
• Access to server pools containing Cloud Resources is assignable to CloudSystem user groups in the same way as other
server pools.
Provisioning
• CloudSystem interfaces to cloud providers to perform provisioning. The cloud provider provisions servers and storage and
deploys images and networks service components together in much the same way that CloudSystem provisioning occurs,
using resources located at the cloud data center.
Prerequisites
• Install HP Insight Management using the 7.2 DVD and install HP Matrix infrastructure orchestration.
• Install (or verify installation of) a supported browser.
• Obtain a Matrix OE Public Cloud Managed Instance license if interfacing to a public cloud provider. For details on
licensing, contact your HP sales representative.
o A public cloud managed instance license allows you to manage one public cloud instance hosted at an HP-
supported public cloud service provider.
o Multiple licenses can be used together under a concurrent use model. For example, if you purchase 10 licenses,
you can manage up to 10 public cloud instances at any one time. The license term is one year from the date of
registration.
o Public cloud managed instance licenses are not tied to a particular service provider. You can use the same license
to manage an instance at one service provider today and at another tomorrow, as long as the license is not used
for both instances at the same time.
4