
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
30 lines
1.3 KiB
ReStructuredText
30 lines
1.3 KiB
ReStructuredText
.. _int: https://docs.python.org/2/library/stdtypes.html
|
|
|
|
.. _str: https://docs.python.org/2/library/stdtypes.html
|
|
|
|
.. _type: ../../../vim/host/DiskPartitionInfo/Partition.rst#type
|
|
|
|
.. _vmodl.DynamicData: ../../../vmodl/DynamicData.rst
|
|
|
|
.. _vim.host.DiskDimensions.Lba: ../../../vim/host/DiskDimensions/Lba.rst
|
|
|
|
|
|
vim.host.DiskPartitionInfo.BlockRange
|
|
=====================================
|
|
A BlockRange data object type describes a contiguous set of blocks on a disk. A BlockRange may describe either a partition or unpartitioned (primordial) blocks on the disk.
|
|
:extends: vmodl.DynamicData_
|
|
|
|
Attributes:
|
|
partition (`int`_, optional):
|
|
|
|
Partition number. This number is a hint from the server indicating what the partition number for this block range is if the range corresponds to a partition. The partition number should correlate to the one in the partition specification. If sent back to the server, this property is ignored.
|
|
type (`str`_):
|
|
|
|
The type of data in the partition.See `type`_
|
|
start (`vim.host.DiskDimensions.Lba`_):
|
|
|
|
The starting block address of the disk range. The block numbers start from zero. The range is inclusive of the end address.
|
|
end (`vim.host.DiskDimensions.Lba`_):
|
|
|
|
The end block address of the disk range. The block numbers start from zero. The range is inclusive of the end address.
|