Server workflows for HP Matrix Operating Environment

Note: The Extended Attributes provide key-value pairs such as Enclosure and EnclosurePosition. If the attributes are

set, infrastructure orchestration will read the information and report location information of the servers.

Matrix OE will determine the LAN and SAN connectivity for the server based on the networkInterfaceName and

sanFabric values from this file. Thus, it is key these values match what will be used when specifying resource requests

which may be fulfilled by these servers (e.g., the named networks in the HP Matrix infrastructure orchestration

Designer “Networks” tab). The servers will be visible in the HP Matrix infrastructure orchestration Designer “Servers”

interface (with suitable details).

Each UUID specified in inventoryList.xml must have corresponding server details in the serverinfo.xml file (otherwise,

the workflow will fail to return details). Any UUID in the serverinfo.xml file but not in the inventoryList.xml file will not

be seen (as the Get Server Info workflow would not be invoked).

Note: The <serverModel> and <cpuFamily> information must be specified correctly to ensure the appropriate

Matrix OE license is made available for the server being described. The following sub-sections show the licenses and

<serverModel> and <cpuFamily> values for the blade and rack-mount ProLiant and Integrity servers.

After the servers are appropriately described in the file, the following steps must be followed for the servers to be

successfully used by HP Matrix infrastructure orchestration:

1. Edit C:\Program Files\HP\Matrix infrastructure orchestration\conf\blade_models.properties

2. Add the appropriate X86_64_MODELS or IA_64_MODELs entry depending on the server type that is being

added. For example:

X86_64_MODELS=ProLiant DL 580 G6

IA_64_MODELS=HPIntegrity BL 860c

3. Repeat the entries above using the SUPPORTED_MODELS property. For example:

SUPPORTED_MODELS=ProLiant DL 580 G6

SUPPORTED_MODELS=HPIntegrity BL 860c

Restart the “HP Matrix infrastructure orchestration” Windows service after making changes to this file.

HP ProLiant c-Class blades not using Virtual Connect and rack-mount servers

As noted earlier, Matrix OE is able to automatically gather information regarding (and perform power operations on)

blades using Virtual Connect. OO workflows are needed for ProLiant c-Class blades not using Virtual Connect, or

ProLiant rack-mount servers.

The blades/servers should use the standard Matrix OE suite for ProLiant license:

 ProLiant c-Class blades not using Virtual Connect

o <serverModel>ProLiant BLXXXc GX</serverModel>

o <cpuFamily>HPProLiant c-Class</cpuFamily>

 ProLiant rack-mount servers

o <serverModel>ProLiant DL/MLXXX GX</serverModel>

o <cpuFamily>HPProLiant</cpuFamily>