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
21 lines
939 B
ReStructuredText
21 lines
939 B
ReStructuredText
.. _policy: ../../../vim/profile/ApplyProfile.rst#policy
|
|
|
|
.. _Network: ../../../vim/Network.rst
|
|
|
|
.. _property: ../../../vim/profile/ApplyProfile.rst#property
|
|
|
|
.. _vSphere API 4.0: ../../../vim/version.rst#vimversionversion5
|
|
|
|
.. _VmPortGroupProfile: ../../../vim/profile/host/VmPortGroupProfile.rst
|
|
|
|
.. _vim.profile.host.PortGroupProfile: ../../../vim/profile/host/PortGroupProfile.rst
|
|
|
|
|
|
vim.profile.host.VmPortGroupProfile
|
|
===================================
|
|
The `VmPortGroupProfile`_ data object represents the subprofile for a port group that will be used by virtual machines. Use the `policy`_ list for access to configuration data for the virtual machine port group profile. Use the `property`_ list for access to subprofiles, if any.vSphere Servers use `Network`_ managed objects to represent virtual machine port groups in the vSphere inventory.
|
|
:extends: vim.profile.host.PortGroupProfile_
|
|
:since: `vSphere API 4.0`_
|
|
|
|
Attributes:
|