Configuring esa in virtualization manager – HP Matrix Operating Environment Software User Manual

Page 28

Advertising
background image

inventory and for performing basic power control. Several server types and configurations may integrate
into Insight Orchestration using ESA in Insight Dynamics.

Non-HP servers

HP rack mount servers

HP c-Class blades (not managed by Virtual Connect)

For each of the server types referenced above, the following storage configurations are supported:

Boot Disk

A SAN (Fiber Channel) attached disk

A local (direct attached) disk. If using an on-board RAID controller, only a single logical volume is
supported.

Data Disk(s)

One or more SAN (Fiber Channel) attached disks

The included reference workflow for controller server power supports the following server management
processors:

ProLiant iLO2

Integrity iLO2

Dell iDRAC and DRAC5

NOTE:

The Operations Orchestration workflow authoring tool (OO Studio) may be used to extend the

functionality of the reference workflow to support additional management processors are required.

Configuring ESA in Virtualization Manager

Modify <Root Drive>:\Program Files\HP\Virtual Server
Environment\conf\esa.properties

to include the Operations Orchestration 'Admin' password:

esa.oo.admin.password=<your-oo-admin-password>

After making the changes to the esa.properties file, it is necessary to restart the HP Extensible Storage
& Server Adapter Windows service for the changes to take effect.

Using the heterogeneous server reference workflows with Insight Orchestration

The reference workflows are driven by three data files in <Root Drive>:\Program Files\HP\Insight
Orchestration\esa_extensions\server

.

<Root Drive>:\Program Files\HP\Insight Orchestration\esa_extensions\server

\inventoryList.xml

“inventoryList.xml” contains a high level listing of all servers that sufaces as inventory through
ESA. The following example of a single server entry shows the format. In this case, a UUID is used for
both the <handle/> and the <uuid/> elements. This is the recommended form. Typically, the UUID is
directly extracted from the managed server or from a centralized configuration management database
(CMDB) within the data center.

<nodeAttributes>

<handle>38313933-3533-5355-4538-32304E334151</handle>
<uuid>38313933-3533-5355-4538-32304E334151</uuid>

</nodeAttributes>

The following screen shot from OO Studio shows the reference workflow which reads the
“inventoryList.xml” file:

28

Configuration

Advertising