HP Matrix Operating Environment 7.3 and 7.3 Update 1 Infrastructure Orchestration User Guide

The OO workflow is invoked whenever a host name needs to be assigned or updated, and is
triggered by the following events:
• Create service/add server: Host names are allocated to newly created servers.
• Delete service/remove server: Host names from removed servers are released.
• Out-of-band host name update: If VM guest tools are installed in the target operating system,
host name changes are detected and the OO workflow is notified. Otherwise, the workflow
is not aware of the host name update. For example, if VMWare tools are installed in an ESX
hypervisor and a user changes the host name, the OO workflow is notified.
By default, the custom host names feature is not enabled. Until it is enabled, the existing host name
generation strategy is used. The following properties (set in the hpio.properties file) control the
behavior of the new functionality:
DefaultDescriptionProperty
falseWhen set to true, the custom host
names feature is enabled
oo.enable.custom.hostnames
/Library/Hewlett-Packard/Infrastructure
orchestration/Custom Hostnames/samples/hostname
powershell
Specifies the path to the OO
workflow. This property is
evaluated only when
oo.custom.hostnames.flow
oo.enable.custom.hostnames is
true
Important notes when enabling or disabling the feature:
• When the feature is enabled, the workflow defined in the hpio.properties file becomes the
host name strategy for all services from all organizations.
• Any services created while this feature is enabled cannot be modified later by adding more
servers with the feature disabled. Either recreate the service or enable the custom host name
feature.
• When the feature is disabled, the default host name strategy based on incremental digit
numbers becomes active.
The OO workflow can utilize any logic to generate host names. The implementation may or may
not use the host name pattern defined in the logical server in designer.
WARNING! If the host name pattern is not used, some validations are disabled. This could result
in host names being assigned that previously would have been invalid. For example, the architect
could specify:
• Empty host names
• The same host name in different server groups (the workflow internally uses the duplicate name
only as a hint, since duplicate host names are not allowed)
• Host names without #
NOTE: Although the host name generation strategy is completely defined in the OO workflow,
Matrix infrastructure orchestration ensures the generated host names are valid and unique within
all servers provisioned by Matrix infrastructure orchestration.
See Appendix B: “Creating custom host name workflows” (page 254) for the operations executed
by a custom host name OO workflow.
142 Matrix infrastructure orchestration provisioning and allocation