Do not trigger thermal loop for disabled thermal controllers When a thermal controller is disabled, it will not contribute to the final setpoint of its owner zones. Therefore, it is unnecessary to even start the thermal loop, unless under tuning, which makes this CL a significant optimization to the prod environment, if there exists any disabled controller. Even for tuning, keep running the disabled thermal loop would be needless, as parameters are to be tuned with causative plots, instead of logs, which can be achieved in advance through thermal simulations. Additionally, with more supportive thermal controllers (e.g., DFF, and EAT) to be added, it becomes more and more redundant to add the code everywhere for different functions to add setpoints (e.g., `AddSetpoint()`, `AddAdditiveSetpoint()`). #pid-tlbmc-migration PiperOrigin-RevId: 862410432 Change-Id: Ic14f061a104634cd4a30abda554d28307fc7dc64
This project is Google's version of BMCWeb.
See Readme Google for Google added features. The following is the original README of OpenBMC/BMCWeb.
==============================================================================
This component attempts to be a “do everything” embedded webserver for OpenBMC.
The webserver implements a few distinct interfaces:
bmcweb at a protocol level supports http and https. TLS is supported through OpenSSL.
Bmcweb supports multiple authentication protocols:
Each of these types of authentication is able to be enabled or disabled both via runtime policy changes (through the relevant Redfish APIs) or via configure time options. All authentication mechanisms supporting username/password are routed to libpam, to allow for customization in authentication implementations.
All authorization in bmcweb is determined at routing time, and per route, and conform to the Redfish PrivilegeRegistry.
*Note: Non-Redfish functions are mapped to the closest equivalent Redfish privilege level.
bmcweb is configured per the meson build files. Available options are documented in meson_options.txt
meson builddir ninja -C builddir
If any of the dependencies are not found on the host system during configuration, meson will automatically download them via its wrap dependencies mentioned in bmcweb/subprojects.
bmcweb relies on some on-system data for storage of persistent data that is internal to the process. Details on the exact data stored and when it is read/written can seen from the persistent_data namespace.
When SSL support is enabled and a usable certificate is not found, bmcweb will generate a self-signed a certificate before launching the server. Please see the bmcweb source code for details on the parameters this certificate is built with.
bmcweb is capable of aggregating resources from satellite BMCs. Refer to AGGREGATION.md for more information on how to enable and use this feature.