HP Matrix Operating Environment Software - Manual (Page 51)

Changing the ESXi Software Depot
Perform the following procedure to change the ESXi Software Depot if a service was previously
created for the target VM Host.
1.
In infrastructure orchestration console, delete the VM Cluster service. (This step is not required
if you are creating a new service.)
2. In Operations Orchestration Studio, update the DepotURL property to point to the new ESXi
depot.
3. In vCenter, manually remove the deploy rule created by the first service.
Following is an example of the deploy rule created by the VM cluster and attached to the
target blade MAC address. The deploy rule points to the depot
HP=ESXi-5.0.0-469512-standard-be2net.
To update the service in this example, remove the deploy rule by entering the command
remove-deployrule -deployrule "00:21:5A:9B:00:04" –delete
.
4. In infrastructure orchestration console, recreate the VM Cluster service.
VMware cluster considerations
VMware ESXi hosts can PXE boot (using vSphere Auto Deploy) from an infrastructure orchestration
designer template definition. If the software deployment server is “custom,” a boot disk is not
required. For servers that boot in a stateless manner (without a boot disk), a service template is
valid when a boot disk is not defined.
Before provisioning a stateless ESXi server, optionally set up Dynamic DNS (DDNS) in the
environment so the infrastructure orchestration FQDN is sent to the DDNS server. Without DDNS,
the network hostname is not set automatically to match the hostname in IO, and the name of the
VM Host in vCenter will be the IP address of the VM Host.
IP addresses are assigned by DHCP and the hostnames must be updated in DNS for proper naming.
The preferredHostName property is set in vCenter, which is designed to be passed to an available
DDNS server to automatically configure DNS resolution.
NOTE: To make the vCenter preferredHostName setting active, restart the ESX server network
management service on the VM Host, or request vCenter to reboot it.
•
DNS must be configured on the CMS so the CMS can resolve the hostname of the VM Hosts,
or
•
VM Hosts must be statically defined so that IP information is available to contact and configure
the VM Hosts.
When adding a physical server to a VM cluster server group, the resulting service may not reflect
the values in the IO template or may fail even though there are available resources that appear to
fit the request. This can occur if the created logical server was updated with information from the
physical server since the first service creation. If a new service is created from the outdated IO
template, the service uses information from the updated logical server instead of the template.
Configuring an environment for ESXi cluster provisioning 51