Server workflows for HP Matrix Operating Environment

Figure 13: Server power OFF workflow: subflow SSH commands

The OO workflow subflow for PowerOff invokes the appropriate iLO command via SSH. Figure 13 shows HP ProLiant

servers using the iLO2 “power off” command for a standard power off, and “stop –force /system1” for a forced

power off. Integrity servers use the “pc –graceful” and “pc –off” commands.

Extensibility:

1. Understand the Power OFF OO workflow

2. Add a new check in the subflow shown above for the corresponding server type (typically included in the server

model string); the Adding a new server type section summarizes the changes for a new server type across the

workflows.

3. The reference implementation uses SSH to invoke the command.

4. Alternatively, create a new IAction class (the OO documentation provides details on developing IAction

extensions).

As noted earlier, the power on and off operations for HP servers are done through iLO (or Virtual Connect, if present).

The following power off sequence is used for those servers:

 Invoke a graceful power off command

 Wait for 30 seconds

 Check the powerOff status

 If the server power is still on, invoke a forced power off command

These steps are performed on HP servers using iLO2 or later.

IActions

To facilitate development of OO workflows, the Matrix OE implementation includes IAction classes for server

operations. The dependent jars for the server workflows are esa-server-model-x.jar and esa-oo-server-rservice-x.jar.