commit | 67f0b9c02138d97b9a3be9676c476e4bd5cd571d | [log] [tgz] |
---|---|---|
author | Myung Bae <myungbae@us.ibm.com> | Mon Jun 23 09:52:37 2025 -0400 |
committer | Ed Tanous <ed@tanous.net> | Tue Jun 24 15:35:04 2025 +0000 |
tree | 3e260ffe8081f481d706206301dd40d5e2e45b24 | |
parent | 5571acd2359e4420d749e14069e3eefe1f5b125b [diff] |
Enhance log traces related to PCIe association errors When Redfish PCIeDevice GET fails due to the association error, sometimes it may be difficult to debug the root cause as bmcweb log entries do not show the related dbus object paths. This commit is to enhance ffdc log traces to show dbus object paths if the association is in error. The areas of the changes are: - the association error between pcie device to pcieSlot Tested: - Redfish Service Validator runs and passes Change-Id: I507260c38d7b7ba735832b470122b86967c22343 Signed-off-by: Myung Bae <myungbae@us.ibm.com>
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 setup 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.