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

# Tenant name for authentication with the cloud provider
provider.tenant.name=
# Access Key ID from the API Keys for the HP Cloud Services account
# (see https://console.hpcloud.com/account/api_keys)
provider.access.key.id=
# Use the command "mxpassword -a -x <mxpassword-key>=<secret-key>" to create
# an mxpassword entry, where <mxpassword-key> is the value specified here and
# <secret-key> is the Secret Key associated with the Access Key ID above.
provider.secretkey.mxpassword.key=hpcs-account-1
# An optional value used to pre-populate the DNS domain value in cloud subnets
subnet.dns.domain=compute.hpcloudsvc.com
# Name of the RSA key pair to use to access the provisioned servers. Create
# the key pair in the HP Cloud Services account for the selected availability
# zone in the Compute service.
default.keypair.name=
# A filter file that controls which images appear in the software inventory
provider.image.filters.file=hpcs-image-filters.xml
# Optional file containing server type definitions. If not specified, server
# type definitions are loaded directly from the provider. Custom server type
# definitions can be used to exclude the use of some server types and to
# normalize processor count and memory size values.
#provider.servertype.file=hpcs-flavors.xml
# A prioritized list of server types to use when the logical server does not
# specify a server type. The first server type that meets the minimum
# processor count and memory size for the logical server is selected.
#
# A keyword shortcut can be used to include all server types (limited by
# provider.servertype.file). The keyword @min-processors prioritizes first by
# minimum processor count and then by minimum memory size. The keyword
# @min-memory prioritizes first by minimum memory size and then by minimum
# processor count. Note: When a keyword shortcut is used, server types added
# later will automatically be eligible for auto-selection.
server.flavor.auto.selection.order=standard.xsmall,standard.small,standard.medium,standard.large
where:
• The provider.secretkey.mxpassword.key value is a user-defined value that is used in the "Create mxpassword
entries for provider account access" 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 cloud capacity pool
with its own key pair for each organization or user.
• The server.flavor.auto.selection.order value is a comma-delimited list of names of the server types to consider
during auto-selection. The first server 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 server types listed in hpcs-flavors.xml,
described in the "Create the server type configuration file" section of this document.
These keyword shortcuts may be used in place of a flavor enumeration.
o server.flavor.auto.selection.order=@min-processors causes the auto-selection order to be set
automatically. When creating a server without a Cloud Server Type defined in the template, the selected server type
is the one with the fewest processors of those that satisfy the logical server requirements. If more than one server
type meets this requirement, the one with the least memory is selected.
o server.flavor.auto.selection.order=@min-memory causes the auto-selection order to be set
automatically. When creating a server without a Cloud Server Type defined in the template, the selected server type
is the one with the least memory of those that satisfy the logical server requirements. If more than one server type
meets this requirement, the one with the fewest processors is selected.
10