Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and HP Cloud Services or Amazon EC2

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 HPCS 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 Create the server types configuration file.

Create the server types configuration file

A server types configuration file contains definitions of server types available from a cloud provider. (Server types are

also known as server flavors.)

Edit (or use unchanged) the sample server types configuration file named hpcs-flavors.xml (or specify a different

filename). If you add or change the name of a server type, ensure that the name matches a server type used by

HPCS. Server type definitions are displayed in the Flavor menu when creating a server in the HPCS management

console.

The server types configuration file can be used to prevent the use of particular server types by a particular capacity

pool, by excluding them from the server types file used for that pool. The provider.servertype.file property

in the capacity pool configuration file indicates the server type definitions to use for that pool. You can use separate

server types files for different capacity pools. The <name> values are used in the

server.flavor.auto.selection.order property in the <pool-id>.properties file.

The following is the sample HPCS server types configuration file.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<server-types>

<server-type>

<name>standard.xsmall</name>

</server-type>

<server-type>

<name>standard.small</name>

</server-type>

<server-type>

<name>standard.medium</name>

</server-type>

<server-type>

<name>standard.large</name>

</server-type>

<server-type>

<name>standard.xlarge</name>

</server-type>

<server-type>

<name>standard.2xlarge</name>

</server-type>

</server-types>