openstack
/
deb-python-pyvmomi
Code Issues Proposed changes

Update VirtualDiskSpec.rst

This commit is contained in:
Nitin Madhok 2016-04-06 14:21:21 -04:00
parent 888bf2c422
commit 27bd6550b3
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/vim/vm/device/VirtualDiskSpec.rst
View File

@ -16,4 +16,4 @@ vim.vm.device.VirtualDiskSpec
Attributes:
migrateCache (`bool`_, optional):
Manner in which to transfer the cache associated with the virtual disk to the target host. If left unset then migrate is used when the backing vFlash module version is compatible with the specific vFalsh module on the target host; otherwise flush is used for write back cache, or a no-op for write through cache. This setting can avoid VM migration failure due to incompatibility. If true then migrate is always used. VM migration may fail if the backing vFlash module version is incompatible with the module on the target host. If false then flush is used for write back cache. It is a no-op for write through cache. This setting can avoid VM migration failure due to incompatibility, but cache files have to be rebuilt on the target host. Default is unset.See `HostVFlashManagerVFlashCacheConfigInfoVFlashModuleConfigOption`_
Manner in which to transfer the cache associated with the virtual disk to the target host. If left unset then migrate is used when the backing vFlash module version is compatible with the specific vFlash module on the target host; otherwise flush is used for write back cache, or a no-op for write through cache. This setting can avoid VM migration failure due to incompatibility. If true then migrate is always used. VM migration may fail if the backing vFlash module version is incompatible with the module on the target host. If false then flush is used for write back cache. It is a no-op for write through cache. This setting can avoid VM migration failure due to incompatibility, but cache files have to be rebuilt on the target host. Default is unset. See `HostVFlashManagerVFlashCacheConfigInfoVFlashModuleConfigOption`_