Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and HP Cloud Services or Amazon EC2

3
 A server type (flavor or instance type) can be explicitly chosen in the template or can be selected automatically
by IO based on the server memory and CPU configuration.
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 share a firewall (security group), which controls inbound network access.
Account access
 HPCS or EC2 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 HPCS or EC2 accounts.
 Access to server pools containing Cloud Resources is assignable to CloudSystem user groups in the same way as
other server pools.
Prerequisites
 Install HP Insight Management using the 7.1 DVD and select to install HP Matrix infrastructure orchestration.
 Install (or verify installation of) a supported browser. See the HP Insight Management Support Matrix for
supported browsers.
 Obtain a Matrix OE Public Cloud Managed Instance license. 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.
Overview of CloudSystem configuration
The following sections describe the configuration steps that must be performed in CloudSystem before you can
provision to a public cloud provider. These steps are similar for HP Cloud Services and Amazon EC2, but are
detailed in separate sections. See Configuring CloudSystem for bursting to HP Cloud Services and Configuring
CloudSystem for bursting to Amazon EC2 for detailed instructions.
The configuration steps in CloudSystem are:
1. Edit the infrastructure orchestration properties file
2. Copy sample configuration files
3. Define capacity pools
4. Configure capacity pools
5. Create the server types configuration file
6. Create image filters for each capacity pool
7. Create mxpassword entries
8. Configure the SSL certificate
9. Restart the infrastructure orchestration service
The purpose and relationship among the CloudSystem configuration and properties files is shown below.