Server workflows for HP Matrix Operating Environment

Figure 1: Matrix OE component interactions

The Extensible Server Adapter uses HP Operations Orchestration (OO) workflows to perform tasks (such as the server

workflows shown in the diagram above and discussed below). Matrix OE includes reference implementations which

can be customized for specific environments.

The ESA server OO workflows support:

 Discovery of HP servers not using Virtual Connect

 Retrieving details of HP servers not using Virtual Connect

 Powering ON the HP servers not using Virtual Connect (via iLO)

 Powering OFF the HP servers not using Virtual Connect (via iLO)

ESA will call OO in an asynchronous fashion (and OO workflows could return quickly or run for longer periods of

time). ESA will invoke a workflow, passing the appropriate input data and an ESA_ID (for correlation). Once the

specific OO workflow is completed, it does a callback to ESA to send back the response (including the ESA_ID).

Figures 2 and 3 show the OO workflow and the interactions with ESA to receive the input and invoke the callback

mechanism.

Matrix OE with

infrastructure

orchestration

Storage Provisioning

Manager

Extensible Server Adapter

Operations

Orchestration

VCEM

HP blades with

Virtual Connect

iLO CLI

Server Workflows

• Get Inventory

• Get Server

Information

• Power ON

• Power OFF