Server workflows for HP Matrix Operating Environment

28
The details of the server-related IAction classes are listed below.
Iaction Class
Inputs
Description
IActionGetServerInventoryCallback
esaMessageID
esaMessageID (reused from workflow input)
inventory
List of servers in the inventory as XML.
opStatus
Status of OO Workflow (SUCCESS or FAILED).
faultInfoList
Error string from one or more workflow operations. If
opStatus is set to SUCCESS, the default value for
faultInfoList should be set to “No fault”.
replytoURI
replyToURI (reused from workflow input).
IActionGetServerInfoCallback
esaMessageID
esaMessageID (reused from workflow input)
serverInfo
List of one or more server parameters as XML.
opStatus
Status of OO Workflow (SUCCESS or FAILED).
faultInfoList
Error string from one or more workflow operations. If
opStatus is set to SUCCESS, the default value for
faultInfoList should be set to “No fault”.
replytoURI
replyToURI (reused from workflow input).
IActionPowerOnCallback
esaMessageID
esaMessageID (reused from Workflow input)
opStatus
Status of OO Workflow (SUCCESS or FAILED).
faultInfoList
Error string from one or more workflow operations. If
opStatus is set to SUCCESS, the default value for
faultInfoList should be set to “No fault”.
replytoURI
replyToURI (reused from Workflow input).
IActionPowerOffCallback
esaMessageID
esaMessageID (reused from Workflow input)
opStatus
Status of OO Workflow (SUCCESS or FAILED).
faultInfoList
Error string from one or more workflow operations. If
opStatus is set to SUCCESS, the default value for
faultInfoList should be set to “No fault”.
replytoURI
replyToURI (reused from workflow input).
Adding a new server type
A new server type can be supported via the reference implementation by adding and/or modifying the flows into the
current implementation. This section details how to add a new subflow and modify the existing flows to support new
server types.
In this section, the term “new server” is used to indicate that a server of a new type (not the existing ProLiant iLO2 or
later servers). NOTE: HP only supports the Matrix OE product server OO workflows with HP
servers.
It is essential to identify and collect relevant data before adding support for a new server into the reference
implementation.
The following information is required:
1. Server Data, in the format as defined in the serverInfo.xml file. The UUID and server model are essential to
execute the flows successfully, and information such as network and SAN connectivity are essential to
successfully utilize the servers from Matrix OE with infrastructure orchestration.
2. Remote management interface to perform power operations on the new server.
3. Credentials required to login into remote management interface:
o IP Address
o User Login ID
o Password
4. Commands to execute following power operations:
o Power ON
o Power OFF
o Power Status (optional)