A VM host represents a VM host technology or hypervisor (for example, Xen, Hyper-V, and so on) either installed on a physical resource or accessed by it (in the case of VMware). VM host objects can be used when making provisioning decisions for a resource.
PlateSpin Orchestrate also supports the discovery of VMware vSphere clusters used for high availability (HA) in a VMware environment or managed by the VMware Distributed Resource Scheduler (DRS) (after an Orchestrate Agent has been deployed into such an environment). In this scenario, Orchestrate also allows you to determine when actions have taken place outside of Orchestrate, such as when DRS moves a VM to an alternate host in the cluster or when an administrator moves a VM into a different resource pool (see Setting Up Orchestrate to Accommodate VMware DRS Clustering and Updates
in the PlateSpin Orchestrate 2.5 Virtual Machine Management Guide).
Although the VM host and the VM host Cluster are regarded as two different types of VM host object, and have differing icons, the discovered clusters are represented in the Explorer tree of the Development Client as VM host objects.
NOTE:The Development Client interface (that is, the fields in the admin view) for a VM host and a VM host Cluster are nearly identical. Facts unique to the VM host Cluster are listed in Section 6.7, Unique VM Host Cluster Facts.
This section includes the following information: