commit | b7790deeba910ccf956ca1cfe91049fce547dae6 | [log] [tgz] |
---|---|---|
author | Lakshmi Yadlapati <lakshmiy@us.ibm.com> | Fri May 12 14:49:20 2023 -0500 |
committer | Lakshmi Yadlapati <lakshmiy@us.ibm.com> | Tue May 16 03:23:09 2023 +0000 |
tree | 56158302da510c908c5677d228c1d56756752dfb | |
parent | adfc6dd863d2bd791257eb858dceb3b307af607b [diff] |
Fix documentation for PCIeDevice properties This commit addresses the incorrect placement and missing documentation of PCIeDevice properties. The properties have been moved to the correct location and all missing details have been added. 913e7732 added the asset properties in the wrong spot. 62cd45af added the pcietype property. f5c9f8bd added the deviceType. No testing has been performed for this change. Tested: None Change-Id: I3574a67c4d1cdb22d6f3dc748b80b6266ed2164c Signed-off-by: Lakshmi Yadlapati <lakshmiy@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.