commit | 9f03894ecf12e0d0ffb0ba7855c256f33f959e44 | [log] [tgz] |
---|---|---|
author | Rohit PAI <ropai@nvidia.com> | Mon Mar 10 15:29:56 2025 +0530 |
committer | Rohit PAI <ropai@nvidia.com> | Thu Mar 20 11:52:03 2025 +0530 |
tree | bdbd9e0835b02d36b4b5d0e3a6719293b09ba87d | |
parent | c76f964a8f793e295a149064df0fbc263ef97e93 [diff] |
Enhance Task removal when queue is full Bmcweb operates with fixed queue length for tasks. The current code removes the oldest task when queue is full. This makes task status unavailable if the first task was still running and was not yet completed. The MR brings enhancement to remove the oldest completed/aborted task. If all tasks are in running state then it removes the oldest task. Tested - UT passes - Created long running task after boot-up followed by 100 short running tasks which completed fast. Long running task status was still available after task queue become full. Change-Id: Ida5d4a84c2b51a4797c50677ce5c4ef2607f09a3 Signed-off-by: Rohit PAI <ropai@nvidia.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.