openstack/deb-python-pyvmomi
Code Issues Proposed changes
Files
16be2697fc9ec7828b1961bc1217bd33eb148b8c
deb-python-pyvmomi/docs/vim/storageDrs/VmConfigInfo.rst
Shawn Hartsock 15f7be9a52 pyVmomi reStructured Text Documentation 
This external documentation for pyVmomi was generated using Googly Docs
(aka Google Standard Documentation) which renders very cleanly in
GitHub. Internal documentation for a class should be done in Sphinx
format because tools like pyCharm and Eclipse can use that documentation
as a hint for code completion.

Note: External docs as Googly Docs, internal docs as Sphinx.

Closes bug#15
2014-06-17 14:07:42 -04:00

2.2 KiB
Raw Blame History

vim.storageDrs.VmConfigInfo

Storage DRS configuration for a single virtual machine. This makes it possible to override the default behavior for an individual virtual machine.

extends

vmodl.DynamicData

since

vSphere API 5.0

Attributes:

vm (vim.VirtualMachine, optional):

Reference to the virtual machine. Can be NULL during initial placement.

enabled (bool, optional):

Flag to indicate whether or not VirtualCenter is allowed to perform any storage migration or initial placement recommendations for this virtual machine on the pod StoragePod . If this flag is false, the virtual machine is effectively excluded from storage DRS.If no individual DRS specification exists for a virtual machine, this property defaults to true.

behavior (str, optional):

Specifies the particular storage DRS behavior for this virtual machine. For supported values, see StorageDrsPodConfigInfoBehavior .

intraVmAffinity (bool, optional):

Specifies whether or not to have the affinity rule for the virtual disks of this virtual machine. If not set, the default value is derived from the pod-wide default defaultIntraVmAffinity .

intraVmAntiAffinity (vim.storageDrs.VirtualDiskAntiAffinityRuleSpec, optional):

Specifies the disks for this virtual machine that should be placed on different datastores. A VM cannot have both an affinity and an anti-affinity rule at the same time. Virtual machine disks that are not in this rule are unconstrained and can be placed either on the same datastore or on a different datastore as other disks from this virtual machine.