5.5 The VM Host Object
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.
This section includes the following information:
5.5.1 The VM Host Info Tab
The page that opens under the tab includes several collapsible sections on the page where you can configure the general information and attributes of the repository.
NOTE:Whenever you make changes to any Grid object, that object’s icon is overlaid with the write icon 
, signifying that the object has been altered. If you want to save the changes you have made, you need to click the Save icon 
on the Development Client toolbar.
Show Inherited Fact Values Check Box
Select this check box to show facts with overridden values supplied through attached and/or inherited polices. Such fact values are read only (non-editable).
VM Host Information
The VM Host Information panel on the Info page includes the following fields:
NOTE:Tool tip text is available when you mouse over any of these fields.
Physical Resource: (Read Only) this field displays the name of the resource that houses this VM host container.
In the Fact Editor, this fact is listed as vmhost.resource:
<fact name="vmhost.resource" value="vmh7sles" type="String" />
Enabled: This check box is selected by default. When it is selected (that is, its value is “true”), the VM host is enabled, which means that VM instances can be provisioned on it.
In the Fact Editor, this fact is listed as vmhost.enabled:
<fact name="vmhost.enabled" value="true" type="Boolean" />
Online: When this check box is selected (that is, its value is “true”), the agent on the physical resource is online.
In the Fact Editor, this fact is listed as vmhost.online:
<fact name="vmhost.online" value="true" type="Boolean" />
Healthy: This check box is selected by default. When it is selected (that is, its value is “true”), the VM host is designated as being in good health. You can set the health of the object by selecting or deselecting the health check box. Changing the value in this way has an immediate effect unless the value is overriden by an attached policy (this follows the normal rules of policy inheritance). For more information, see Section A.0, Grid Object Health Monitoring
In the Fact Editor, this is fact is listed as vmhost.health:
<fact name="vmhost.health" value="false" type="Boolean" />
Shutting Down: When this check box is selected (that is, its value is “true”), the VM host is attempting to shut down and does not accept provisioning requests.
In the Fact Editor, this fact is listed as vmhost.shuttingdown:
<fact name="vmhost.shuttingdown" value="false" type="Boolean" />
Location: Optional description of the physical location of the VM host.
In the Fact Editor, this fact is listed as vmhost.location:
<fact name="vmhost.location" value="" type="String" />
Supports VM Migration: When this check box is selected (that is, its value is “true”), the VM host can support VM migration. The state of this fact can also depend on the migration capabilities of the provisioning adapter used to provision the VM.
In the Fact Editor, this fact is listed as vmhost.migration:
<fact name="vmhost.migration" value="true" type="Boolean" />
Supports H/W HVM: When this check box is selected (that is, its value is “true”), the hypervisor on the VM host can support hardware virtualization.
In the Fact Editor, this fact is listed as vmhost.hvm:
<fact name="vmhost.hvm" value="false" type="Boolean" />
Accounting Group: From the drop-down list, you can select the default VM host group that you want to be adjusted for VM tracking statistics.
In the Fact Editor, this fact is listed as vmhost.accountinggroup:
<fact name="vmhost.accountinggroup" value="all" type="String" />
Max Hosted VMs: This value specifies the maximum number of VM instances allowed on this VM host.
In the Fact Editor, this fact is listed as vmhost.maxvmslots:
<fact name="vmhost.maxvmslots" value="8" type="Integer" />
Max Virtual Memory: This field displays the amount of memory (measured in MB) available to hosted VMs.
In the Fact Editor, this fact is listed as vmhost.memory.max:
<fact name="vmhost.memory.max" value="1000" type="Integer" />
Repositories: This field that displays the list of repositories (that is, VM disk stores) that are visible to this VM host.
In the Fact Editor, this fact is listed as an array:
<fact name="vmhost.repositories"> <array type="String"> </array> </fact>
You can edit this array by clicking the 
button to open the Choose Grid Objects dialog box. In this dialog box you can add, remove, or edit repositories in an array of repository choices.
Available VM Resource Groups: This field displays a list of resource groups containing VMs that are allowed to run on this VM host.
In the Fact Editor, this fact is listed as an array:
<fact name="vmhost.vm.available.groups"> <array type="String"> </array> </fact>
You can edit this array by clicking the button to open the Choose Grid Objects dialog box. In this dialog box you can add, remove, or edit the resource groups (element values) in an array of choices.
Managing Job: In this field, you can specify the ID of a running job that manages VM operations on this VM host. When this field is completed, the VM Manager prevents other jobs from initiating provisioning actions. The fact is cleared when the managing job ends.
In the Fact Editor, this fact is listed as vmhost.controllingjob:
<fact name="vmhost.controllingjob" value="" type="String" />
Needs Resync: When this check box is selected (that is, its value is “true”), you specify that, at the next opportunity, this VM host is to be probed to resynchronize all the VMs that are managed here.
In the Fact Editor, this fact is listed as vmhost.resync:
<fact name="vmhost.resync" value="false" type="Boolean" />
Provisioning Adapter Config
Adapter Job Name: From the drop-down list, you can select the name of the provisioning adapter job that manages VM discovery on this host. Do not change this value unless you have implemented your own discovery job.
In the Fact Editor, this fact is listed as vmhost.provisioner.job:
<fact name="vmhost.provisioner.job" value="esx" type="String" />
Username: In this field, specify the username required for provisioning on the VM host.
In the Fact Editor, this fact is listed as vmhost.provisioner.username:
<fact name="vmhost.provisioner.username" value="" type="String" />
Password: In this field, specify the password required for provisioning on the VM host.
In the Fact Editor, this fact is listed as vmhost.provisioner.password:
<fact name="vmhost.provisioner.password" value="" type="String" />
Guest VM Monitor Information
Current VM Count: (Read Only) This field displays the current number of active VM instances.
In the Fact Editor, this fact is listed as vmhost.vm.count:
<fact name="vmhost.vm.count" value="0" type="Integer" />
Available Virtual Memory: This field displays the amount of memory (measured in MB) available to new VMs.
In the Fact Editor, this fact is listed as vmhost.memory.available:
<fact name="vmhost.memory.available" value="1000" type="Integer" />
VM Image Counts: This field displays the dictionary of running instance counts for each running VM template.
In the Fact Editor, this fact is listed as a dictionary:
<fact name="vmhost.vm.templatecounts">
<dictionary>
<dictelement key="ads">
<time>12:00 AM</time>
</dictelement>
</dictionary>
</fact>
You can edit the dictionary elements by clicking the button to open the VM Image Counts dialog box and then by adding or removing the names in the dictionary.
Running VM Instances: (Read Only) This field displays a list of active VM instances.
Load Index (Slots): (Read Only) This field displays the current loading index of resource slots, which is a ratio of the active hosted VMs to the specified maximum number of VMs allowed on this host. Each provision VM takes up one slot. For more information, see Max Hosted VMs.
In the Fact Editor, this fact is listed as vmhost.loadindex.slots:
<fact name="vmhost.loadindex.slots" value="0.1250" type="Real" />
Load Index (Memory): (Read Only) This field displays the current loading index for memory, which is a ratio of the virtual memory consumed on this VM host to the specified maximum amount of memory allocated to this host.
In the Fact Editor, this fact is listed as vmhost.loadindex.virtualmemory:
<fact name="vmhost.loadindex.virtualmemory" value="0.0000" type="Real" />
5.5.2 The VM Host Policies Tab
The Polices tab opens a page that contains a policy viewer for each of the policies associated with a Grid object.
NOTE:You can edit a policy by right-clicking a policy icon, selecting and clicking the Save icon.
5.5.3 The VM Host Health Debugger Tab
The Health Debugger is a common Admin view in the Development Client for most Grid objects. For information about this tool, see Section 6.0, The Health Debugger.
5.5.4 The VM Host Constraints/Facts Tab
The Constraints/Facts tab opens a page that shows all of the effective constraints and facts for a Grid object. Each Grid object has an associated set of facts and constraints that define its properties. In essence, by building, deploying, and running jobs on the PlateSpin Orchestrate Server, you can individually change the functionality of any and all system resources by managing an object’s facts and constraints. The Orchestrate Server assigns default values to each of the component facts, although they can be changed at any time by the administrator, unless they are read-only. Facts with mode r/o have read-only values, which can be viewed (that is, using the edit “pencil” icon) but changes cannot be made.
5.5.5 The VM Host Action History Tab
The Action History tab is displayed in the administrative view of the Repository object. When you select the Action History tab, a table displays a list of the history for all VM provisioning actions performed on this Grid object.
The Orchestrate Server must be connected to an audit database for the check box to be available. If the check box is selected in this view, the action status is not polled. Click the refresh icon in the toolbar to fetch and display fresh data.
For more details about the information listed on the Action History page, see Section D.2.2, Action History in Admin Views of the Development Client.