vSphere ESX Agent Manager API
|
| Local Properties | ||
| Managed Object Types | Data Object Types | All Properties | All Methods |
Data Object - SolutionsAlternativeVmSpec
- Property of
- HooksDynamicUpdateSpec, SolutionsClusterBoundSolutionConfig
- Extends
- vmodl.DynamicData
- See also
- SolutionsVmSelectionSpec, vim.vm.ConfigSpec
- Since
- vEAM API 9.1
Data Object Description
Describes alternative VM configuration to be applied on VMs that matches a given selection criteria defined as VmSelectionSpec.Properties
| Name | Type | Description |
|---|---|---|
| devices* | vim.vm.ConfigSpec |
Devices of the VMs not defined in the OVF descriptor. This field
takes precedence over ClusterSolutionSpec#devices.
If ClusterSolutionSpec#vmDatastores is not set, the devices of the VMs not defined in the OVF descriptor should be provided to devices and not as part of a VM lifecycle hook (VM reconfiguration). Otherwise, the compatibility of the devices with the selected host and datastore where the VM is deployed needs to be ensured by the client. 1. For VM initial placement the devices are added to the VM configuration. 2. For the reconfiguration it is checked what devices need to be added, removed, and edited on the existing VMs. NOTE: No VM relocation is executed before the VM reconfiguration. The supported property of vim.vm.ConfigSpec is vim.vm.ConfigSpec.deviceChange. The supported vim.vm.device.VirtualDeviceSpec.operation is Operation#add. For vim.vm.device.VirtualEthernetCard the unique identifier is vim.vm.device.VirtualDevice#unitNumber. ClusterSolutionSpec#vmNetworks and devices are mutually exclusive.
If omitted - ClusterSolutionSpec#devices is used.
|
| selectionCriteria | SolutionsVmSelectionSpec |
Selection criteria to match System VMs for which to apply this spec.
|
| Properties inherited from vmodl.DynamicData | ||
| None | ||
Show WSDL type definition
| Top of page | Local Properties | ||
| Managed Object Types | Data Object Types | All Properties | All Methods |