Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and Savvis
<Id>savvis-cloud-1</Id>
<Name>savvis-cloud-1</Name>
</Resources>
<Resources xsi:type="CloudCapacityPool" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Id>savvis-cloud-2</Id>
<Name>savvis-cloud-2</Name>
</Resources>
</CapacityPool>
Create a pool properties file for each pool
For each pool entered in savvis-cloud-pools.xml, create a properties file using the information from the example below
and save it in C:\Program Files\HP\Matrix infrastructure orchestration\conf\. Name the file
<pool-ID>.properties, where <pool-ID> is the pool ID entered in savvis-cloud-pools.xml.
provider.url=https://api.savvis.net/vpdc/v1.0
provider.profile=<SAVVIS_ACCOUNT_PROFILE>
provider.username=<SAVVIS_ACCOUNT_USERNAME>
proxy.host=<PROXY_FROM_BROWSER>
proxy.port=<PROXY_PORT_FROM_BROWSER>
proxy.username=<NOT_REQUIRED>
proxy.password=<NOT_REQUIRED>
For example, savvis-cloud-1.properties contains the following information:
provider.url=https://api.savvis.net/vpdc/v1.0
provider.profile=balanced
provider.username=firstname.lastname
proxy.host=
proxy.port=8088
proxy.username=
proxy.password=
Create an mxpassword entry for each pool
For each pool entered in savvis-cloud-pools.xml, create an entry in mxpassword. Open a command prompt
on the Central Management Server (CMS) and enter the following information, replacing savvis-cloud-1 with the
name of each pool ID in savvis-cloud-pools.xml.
mxpassword -a -x savvis-cloud-1=<SAVVIS-ACCOUNT-PASSWORD>
Create a software mapping file for each pool
As part of the bursting process, IO matches the software specified in the template, and matches it against software
defined in Savvis as mapped in the properties file. This provides a mapping from software X in CloudSystem Matrix
to software Y in Savvis.
The Matrix software that is selected is not important; it only matters that the software has a specific mapping to a
specific software item in Savvis that will be used to create the new VM. Generally, the software in Matrix and Savvis
are equivalent (for example, small_win2k8, large_win2k8, using the desired naming convention). The mapping
directs Matrix so that when a request for software X is targeted at the cloud, it creates a VM from software Y in the
cloud.
For each pool entered in savvis-cloud-pools.xml, create a properties file containing the mapping values for
your software. This file is used to identify the software that should be installed in the virtual machine in the Savvis
portal. Save the file in C:\Program Files\HP\Matrix infrastructure orchestration\conf\. Name
the file <pool-ID>-software.properties, where <pool-ID> is the pool ID entered in savvis-cloud-
pools.xml.
The first part of the mapping file (to the left of the equals sign) is the infrastructure orchestration software
location. This location is shown in the bottom details pane of the infrastructure orchestration console Software
tab. (If an ellipsis is displayed at the end of the location, hover your mouse to see the full location in yellow.
Special characters in the software location must be preceded by a “\”.)
In the following example, the infrastructure orchestration software location is:
vm\://192.168.200.11/vmfs/volumes/datastore1/WinTemplate/WinTemplate.vmtx