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

The @min-xxx shortcut above is not appropriate for use in these cases:
o An XML flavor file is not used, and one or more server types must be excluded from auto-selection. (For example,
those with special properties such as a cluster type or specialized CPU access like Amazon's t1.micro.)
o An XML flavor file is not used, and server types introduced in the future must not be selected automatically without
an explicit choice to do so.
o The server type selection order must be based on a factor (such as cost) that does not match the automatically
computed order.
Create the server type configuration file
A server type configuration file contains definitions of server flavors or instance types available from a cloud provider. Edit (or use
unchanged) the sample server type configuration files (or specify a different filename):
• HP Cloud Services: hpcs-flavors.xml
• Amazon EC2: ec2-instance-types.xml
Note: This file is required for EC2 and is optional for providers that use the Nova adapter. If no server type file is configured, the
server type definitions are gathered directly from the provider.
If you add or change the name of a server type, ensure that the name matches a server/instance type used by the cloud resource. See
the following for the latest server type definitions:
• Matrix-to-Matrix—Ask the provider for this information.
• HP Matrix KVM Private Cloud—Server type definitions are displayed on the Instance Types screen in the HP Matrix
KVM Admin Console.
• HP Cloud Services—Server type definitions are displayed in the Flavor menu when creating a server in the HPCS
management console.
• Amazon EC2—For the latest EC2 instance type definitions, go to http://aws.amazon.com/ec2/instance-types
.
The server type configuration file can be used to prevent the use of particular server types by a particular capacity pool by excluding
them from the server type file used for that pool. The provider.servertype.file property (provider.instancetpe.file
for EC2) in the capacity pool configuration file indicates the server/instance type definitions to use for that pool. You can use separate
server type files for different capacity pools. The same server type file can be used for multiple pools. The <name> values are used in
the server.flavor.auto.selection.order property or the instancetype.auto.selection.order property in the
<pool-id>.properties file.
Sample server type configuration files for HP Cloud Services and Amazon EC2 can be found in "Appendix B: Sample files". For
Matrix-to-Matrix and HP Matrix KVM Private Cloud, if you want to change or limit the server type definitions retrieved from your
provider, use the HP Cloud Services sample file and modify it to match the definitions for your provider.
Create image filters
HP Cloud Services server images, Amazon Machine Images (AMIs), target Matrix images, and HP Matrix KVM Private Cloud 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 publically available images and optional private images you create in your
account. An image filter configuration determines which images are visible to CloudSystem.
Edit (or use unchanged) the sample image filter file named <provider>-image-filters.xml. An image filter file limits the image
inventory to a manageable size, and can be used to prevent the use of particular images. For example, one might exclude the use of
an AMI with a product code. For more information about image filters for Amazon EC2, see the Amazon Elastic Compute Cloud API
Reference at: http://docs.amazonwebservices.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeImages.html
.
For more information about image filter definitions, see the Filter rules section of the appropriate sample image filter file in "Appendix
B: Sample files".
Set the provider.image.filters.file property in <pool-id>.properties to the name of the filter file. For example:
provider.image.filters.file=hpcs-image-filters.xml
Note: Multiple pools can use the same image filter file. Sample files for each provider are available in "Appendix B: Sample files".
Configure the SSL certificate
To enable HTTPS (secure HTTP) access to the provider API endpoint, the provider SSL root certificate must be imported into the Systems
Insight Manager trust store. A web browser is used to download the certificate.
11