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
34 lines
1.3 KiB
ReStructuredText
34 lines
1.3 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.ManagedEntity: ../../../vim/ManagedEntity.rst
|
|
|
|
.. _vim.dvs.DistributedVirtualPort.Setting: ../../../vim/dvs/DistributedVirtualPort/Setting.rst
|
|
|
|
|
|
vim.dvs.DistributedVirtualPort.ConfigInfo
|
|
=========================================
|
|
Management related configuration of a DistributedVirtualPort.
|
|
:extends: vmodl.DynamicData_
|
|
:since: `vSphere API 4.0`_
|
|
|
|
Attributes:
|
|
name (`str`_, optional):
|
|
|
|
The name of the port.
|
|
scope (`vim.ManagedEntity`_, optional):
|
|
|
|
The eligible entities that can connect to the port. If unset, there is no restriction on which entity can connect to the port. If set, only the entities in the specified list or their child entities are allowed to connect to the port. If scopes are defined at both port and portgroup level, they are taken as an "AND" relationship. If such a relationship doesn't make sense, the reconfigure operation will raise an exception.
|
|
description (`str`_, optional):
|
|
|
|
A description string of the port.
|
|
setting (`vim.dvs.DistributedVirtualPort.Setting`_, optional):
|
|
|
|
The network configuration of the port.
|
|
configVersion (`str`_):
|
|
|
|
The version string of the configuration.
|