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

ManualsBrandsHP ManualsSoftwareHP Matrix Operating Environment w/Insight Control 24x7 Supp 1 Server Lic

Edit the capacity pool definition, which appears as a Cloud Resource in the Matrix infrastructure orchestration designer, self service

portal, and console.

The following is a sample <Resources> element, with associated child elements, for a HP Matrix KVM Private Cloud pool.

<Resources xsi:type="CloudCapacityPool" xmlns:xsi="http://www.w3.org/2001/XMLSchema-

instance">

<Id>sample-MatrixKVM-pool</Id>

<Name>Sample HP Matrix KVM Controller</Name>

<Provider>HP Matrix KVM Controller</Provider>

<PublicCloudLicenseRequired>false</PublicCloudLicenseRequired>

</Resources>

• The <Id> value is used to locate the corresponding capacity pool properties file.

• The <Name> value is the Cloud Resource name.

• The <Provider> value is the capacity pool's source provider.

• The <ProviderConsoleUrl> element, if specified, provides a convenience link from the cloud resource in the Matrix

infrastructure orchestration console to the cloud provider console.

• The <PublicCloudLicenseRequired> value is used to distinguish between on-premise and public cloud resources, for

the verification of usage of each resource type for license management purposes. It is set to true by default.

Sample capacity pool definition files for each cloud resource type are available in "Appendix B: Sample files".

Create mxpassword entries for provider account access

Select an mxpassword key to hold the provider account credentials, and set this key name in the

provider.secretkey.mxpassword.key property (provider.account.mxpassword.key for Amazon EC2) in the <pool-

id>.properties file.

Enter the secret access key or password for each provider account using the following command:

mxpassword -a -x <provider.secretkey.mxpassword.key value>=<access key

for this provider account>

where <provider.secretkey.mxpassword.key value> is the property value in the <pool-id>.properties file, and

<access key for this provider account> is the secret access key for the provider account used for this capacity pool.

Configure capacity pools

For each pool defined in <adapter>-cloud-pools.xml, a properties file must be defined to specify the properties of the pool.

That file must have a name of the form <pool-id>.properties, where <pool-id> is the value of the corresponding <Id> element in the

<adapter>-cloud-pools.xml file.

To create the pool properties file, copy the sample properties file named sample-<provider>-pool.properties to

conf/cloud/<pool-id>.properties. The <pool-id> in the filename must match the <Id> value in <provider>-cloud-

pools.xml. Set appropriate values for each property, following the instructions in the sample file.

The following is a sample capacity pool properties file. Provider-specific information appears at the end of the sample. Endpoint value

examples and sample files for each provider are available in "Appendix B: Sample files".

# This file specifies the properties for an HP Cloud Services capacity pool

# defined in nova-cloud-pools.xml.

# The API endpoint of the Identity service for the cloud provider, with the

# version ID omitted.

# Note: The use of an HTTPS endpoint may require a cloud provider certificate

# to be added to the trust store. Retrieve the root certificate from the

# provider and place it in a file. Add it to the trust store using the

# command "mxcert -t -f <certificate-file>".

provider.api.endpoint=https://region-a.geo-1.identity.hpcloudsvc.com:35357

# The region (availability zone) ID

provider.region.id=az-2.region-a.geo-1

# Specify proxy settings if required to access the provider API endpoint

proxy.host=

proxy.port=