Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and HP Cloud Services or Amazon EC2
12
# An optional value used to pre-populate the DNS domain value in EC2 subnets
subnet.dns.domain=us-east-1.amazonaws.com
# Name of the EC2 key pair to use to access the provisioned servers
default.keypair.name=
# A filter file that controls which AMIs appear in the software inventory
provider.image.filters.file=ec2-image-filters.xml
# A file that defines the instance types to use and their characteristics
provider.instancetype.file=ec2-instance-types.xml
# A prioritized list of instance types to select based on logical server
# attributes (processor count and memory size) when the logical server
# definition does not indicate a specific instance type
instancetype.auto.selection.order=m1.small,m1.large,m1.xlarge
where:
The provider.account.mxpassword.key is a user-defined value that is used in the Create mxpassword
entries step.
The default.keypair.name value is the name of the RSA key pair initially configured to access the servers
created from this capacity pool. The key pair name is defined when the key pair is registered with the cloud
provider. To prevent access by other users who may have access to this key pair, the key pair may be changed
directly on the server after it is provisioned. Alternatively, if isolation is required or desired, it can be achieved by
creating a separate EC2 cloud capacity pool with its own key pair for each organization or user.
The instancetype.auto.selection.order value is a comma-delimited list of names of the instance types
to consider during auto-selection. The first instance type that matches the requirements of a logical server
definition is used to provision the server. Names in this list must match the values of the <name> tags of the
instance types listed in ec2-instance-types.xml, described in Create an EC2 instance types configuration
file.
To create EC2 instances within an Amazon Virtual Private Cloud (VPC) instead of in EC2, the
provider.vpc.id property must be defined and uncommented in the properties file. For more information,
see Appendix: Provisioning to an Amazon VPC and the Amazon Virtual Private Cloud FAQs.
Create an EC2 instance types configuration file
An instance types configuration file contains definitions of instance types available from a cloud provider.
Edit (or use unchanged) the sample instance types configuration file named ec2-instance-types.xml (or specify
a different filename). If you add or change the name of an instance type, ensure that the name matches an instance
type used by EC2. See http://aws.amazon.com/ec2/instance-types for the latest EC2 instance type definitions.
The instance types configuration file can be used to prevent the use of particular instance types by a particular capacity
pool, by excluding them from the server types file used for that pool. The provider.instancetype.file property
in the capacity pool configuration file indicates the instance type definitions to use for that pool. You can use separate
instance types files for different capacity pools. The <name> values are used in the
instancetype.auto.selection.order property in the <pool-id>.properties file.
The following is the sample EC2 instance types configuration file.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<server-types>
<!-- Refer to http://aws.amazon.com/ec2/instance-types for definitions
of EC2 instance types.
Processor counts are set based on Amazon ECU values. An ECU is
equivalent to one early-2006 1.7 GHz Xeon processor.
32-bit x86 processors are represented as "IA-32".
64-bit x86 processors are represented as "x86_64".
A t1.micro instance cannot be launched from an S3-backed AMI.
Some instance types may not be available in all regions. Please
refer to AWS documentation.