HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

ManualsBrandsHP ManualsSoftwareHP-UX Matrix Operating Environment

230

231

232

233

234

235

236

237

238

239

Example 3 Received XML (PropertyXML)

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<Name>LogicalServer:0577a0cc-8122-4802-8173-6161b2f8dcc4</Name>

</Property>

<Name>LogicalServer:15d20b1d-abee-45bb-88d8-d951dc1495d9</Name>

</Property>

</PropertyList>

The RELEASE operation may be triggered by a create service or add server request. If the workflow

is invoked to generate host names, and the request fails for any reason, the workflow is invoked

again to release the previously generated host names.

If the RELEASE operation fails, the current request completes with warnings indicating that the host

names may have not been released successfully and that manual cleanup might be required.

HostnameOperationTypeEnum UPDATE option

The HostnameOperationTypeEnum UPDATE is used when out-of-band host name changes are

detected. Configure the workflow parameters as follows:

• PropertyXML contains the name/value pairs representing the server IDs of the servers which

have their host name changed. The value field of each pair contains the new host name.

• The workflow must find the appropriate logical servers in the InfrastructureServiceXML based

on the specified server IDs.

• The workflow must take the appropriate actions for each specified logical server depending

on its internal behavior. For example, the provided sample using a pool of host names updates

the host name of the corresponding server ID in the database.

• No return value is expected.

Example 4 Received XML (PropertyXML)

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<Name>LogicalServer:0577a0cc-8122-4802-8173-6161b2f8dcc4</Name>

<Value>new-hostname-01</Value>

</Property>

<Name>LogicalServer:15d20b1d-abee-45bb-88d8-d951dc1495d9</Name>

<Value>new-hostname-02</Value>

</Property>

</PropertyList>

The Value elements are updated with host names.

If the UPDATE operation fails, no visible feedback is provided to the user since that is an

asynchronous event. An error message is logged in the hpio-controller.log file with detailed

information.

Sample custom host names workflows

To help transition to a new host name generation strategy, two sample custom host name

implementations are available:

• A powershell based implementation which generates host names with an incremental digit

number (similar to the existing host name strategy)

Find this sample workflow in the following directory:

232 Creating custom host name workflows