HP CloudSystem Matrix How-To Guide: ESXi Cluster Provisioning

34
50_HostRegisterOnVMM_group_end
Registers each VM host in the cluster with Matrix Operating
Environment, and in case of error, attempts to discover the
server again.
60_MoveHostToCluster_group_end
Connects to the vCenter/Auto Deploy server and moves each VM host
into the vCenter cluster.
70_ConfigureVSwitchesAndPortGroups_gr
oup_end
Connects to the vCenter/Auto Deploy server and configures the first host
with the defined networks.
80_CreateHostProfile_group_end
Connects to the vCenter/Auto Deploy server, creates a VMware host
profile from the first VM host, and applies the host profile to all VM
hosts in the cluster.
90_AssignVMhostsToPool_group_end
In Matrix OE, assigns each VM host to the HP IO pool named for
the cluster.
95_Delete_Datastore
Connects to the vCenter/Auto Deploy server, removes each VM host
from vCenter, and deletes the associated data stores.
Util_Delay
A utility flow that delays hpscriptdelayminutes minutes.
Customizing the OO flows
You can modify the behavior of the OO flows by accessing the Windows PowerShell code in Operations
Orchestration Studio as follows:
 Log in to your fully installed CMS.
 Open OO Studio by clicking Start -> Programs -> Hewlett-Packard -> Operations Orchestration ->
HP Operations Orchestration Studio.
 Enter the credentials. The user name is admin, and the password is what was entered at installation time.
Expand the tree on the left section of the page, down to Library -> Hewlett-Packard -> Infrastructure
Orchestration -> Service Actions -> HP -> ESXHOST.
 The flows are listed alphabetically. Double-click the required workflow.
 In the flow diagram that appears, double-click the PowerShell Script step. Click the right arrow on the input
variable named script.
Customizing the VMware host profile
VMware host profiles define a standard configuration for the blades in a cluster. The host profile created by the
80_CreateHostProfile_group_end workflow is uniquely named for each instance of service request and is generated
from the first VM host in the service request. The VMware host profile is then applied to subsequent VM hosts added
to the cluster either at creation or server add time.
With the distributed set of OO workflows, the initial host profiles must be created by IO first through the IO process.
Customizations made to the primary VM host in the cluster, such as networking configuration or Common Information
Model (CIM) indication subscriptions, require that the VMware host profile be regenerated, with the same name,
through vCenter and reapplied to the cluster. Any new VM hosts added to the cluster will get the updated VMware
host profile applied to them to match the other hosts in the cluster.