
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
1.6 KiB
vim.Datastore.Capability
Information about the capabilities of this datastore.
- extends
- Attributes:
-
directoryHierarchySupported (bool):
Indicates whether or not directories can be created on this datastore.
rawDiskMappingsSupported (bool):
Indicates whether or not raw disk mappings can be created on this datastore.
perFileThinProvisioningSupported (bool):
Indicates whether or not the datastore supports thin provisioning on a per file basis. When thin provisioning is used, backing storage is lazily allocated.This is supported by VMFS3. VMFS2 always allocates storage eagerly. Thus, this value is false for VMFS2. Most NAS systems always use thin provisioning. They do not support configuring this on a per file basis, so for NAS systems this value is also false.
storageIORMSupported (bool):
Indicates whether the datastore supports Storage I/O Resource Management.
nativeSnapshotSupported (bool):
Indicates whether the datastore supports native snapshot feature which is based on Copy-On-Write.
topLevelDirectoryCreateSupported (bool, optional):
Indicates whether the datastore supports traditional top-level directory creation.See DatastoreNamespaceManager
seSparseSupported (bool, optional):
Indicates whether the datastore supports the Flex-SE(SeSparse) feature.