
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
28 lines
760 B
ReStructuredText
28 lines
760 B
ReStructuredText
.. _vim.host.HardwareStatusInfo: ../../../vim/host/HardwareStatusInfo.rst
|
|
|
|
.. _vim.host.HardwareStatusInfo.Status: ../../../vim/host/HardwareStatusInfo/Status.rst
|
|
|
|
vim.host.HardwareStatusInfo.Status
|
|
==================================
|
|
The current status of the hardware
|
|
:contained by: `vim.host.HardwareStatusInfo`_
|
|
|
|
:type: `vim.host.HardwareStatusInfo.Status`_
|
|
|
|
:name: Red
|
|
|
|
values:
|
|
--------
|
|
|
|
Unknown
|
|
The implementation cannot report on the current status of the physical element
|
|
|
|
Green
|
|
The physical element is functioning as expected
|
|
|
|
Red
|
|
The physical element is failing. It is possible that some or all functionalities of this physical element is degraded or not working.
|
|
|
|
Yellow
|
|
All functionality is available but some might be degraded.
|