
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
31 lines
1.1 KiB
ReStructuredText
31 lines
1.1 KiB
ReStructuredText
.. _str: https://docs.python.org/2/library/stdtypes.html
|
|
|
|
.. _vSphere API 4.0: ../../../vim/version.rst#vimversionversion5
|
|
|
|
.. _vmodl.DynamicData: ../../../vmodl/DynamicData.rst
|
|
|
|
.. _vim.host.PlugStoreTopology.Path: ../../../vim/host/PlugStoreTopology/Path.rst
|
|
|
|
.. _vim.host.PlugStoreTopology.Device: ../../../vim/host/PlugStoreTopology/Device.rst
|
|
|
|
|
|
vim.host.PlugStoreTopology.Plugin
|
|
=================================
|
|
This data object type represents a Plugin in the plug store architecture. A Plugin claims a set of paths and groups them into Devices.
|
|
:extends: vmodl.DynamicData_
|
|
:since: `vSphere API 4.0`_
|
|
|
|
Attributes:
|
|
key (`str`_):
|
|
|
|
The identifier of the plugin.
|
|
name (`str`_):
|
|
|
|
The name of the plugin.
|
|
device (`vim.host.PlugStoreTopology.Device`_, optional):
|
|
|
|
The set of devices formed by this plugin.
|
|
claimedPath (`vim.host.PlugStoreTopology.Path`_, optional):
|
|
|
|
The set of paths claimed by this plugin. Not every claimed path will necessarily appear as part of a Device. Claimed paths will only appear under Devices if the device identifier of the path matches up with the device identifier exposed by the Device.
|