15f7be9a52
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
2.1 KiB
vim.host.UnresolvedVmfsVolume
Information about detected unbound, unresolved VMFS volume. An unresolved VMFS volume is reported when one or more device partitions of volume are detected to have copies of extents of the volume. Such copies can be created via replication or snapshots.UnresolvedVmfsVolume are not mounted on the host where they are detected. User may choose to resignature the volume in which case a new Uuid is assigned to the volume and contents of the VMFS volume is kept intact.User may choose to keep the original Uuid and mount the VMFS volume as it is on the given host. In this case, user has choosen to mount the copy of the VMFS volume on that host with no change to the original Uuid. This may fail with VmfsVolumeAlreadyMounted exception if there is an existing VMFS volume with the same Uuid mounted somewhere in the same datacenter.Simple diagram representing the possible operations on UnresolvedVmfsVolumeresignature forceMount VmfsVolume<--------------- Unresolved ------------> VmfsVolume with forceMountedInfo Vmfs Volume forceMountedInfo not set will be setSee HostStorageSystem
- extends
- since
- Attributes:
-
extent (vim.host.UnresolvedVmfsExtent):
List of detected copies of VMFS extents.
vmfsLabel (str):
The detected VMFS label name
vmfsUuid (str):
The detected VMFS UUID
totalBlocks (int):
Total number of blocks in this volume.
resolveStatus (vim.host.UnresolvedVmfsVolume.ResolveStatus):
Information related to how the volume might be resolved.