| commit | 28cfceb2980baa76d7f0599dd4a331ceaec52e1f | [log] [tgz] |
|---|---|---|
| author | Gunnar Mills <gmills@us.ibm.com> | Thu Aug 22 15:12:11 2024 -0500 |
| committer | Gunnar Mills <gunnar@gmills.xyz> | Fri Aug 23 15:53:47 2024 +0000 |
| tree | 267cd756e9c21cf6cea2ce2589eb4a4dfde25ff8 | |
| parent | 2ccce1f3a04ab72824820a6795878ce01f37a22c [diff] |
Update to 2024.2 Redfish changed the directory structure again. Don't see that ZipFile has a "cd" so insert the version in the path when checking or building the path. You can see this directory structure change by downloading 2024.2 vs 2024.1. Also by printing the ZipFile Info. <ZipInfo filename='DSP8010_2024.2/info.json' compress_type=deflate filemode='-rw-r--r--' file_size=54 compress_size=42> This is how we used to do it. [1] [1]: https://github.com/openbmc/bmcweb/commit/60c922dfacd5d1aeec8789e03edc91b47f4a6661 Make the changes for the script, bump the version, and run the script. See below for more info on this release: https://www.dmtf.org/content/redfish-release-20242-now-available Tested: Validator is happy. Change-Id: I87674d5b9ff19b39d3cdf2fb046543e21a6ebc5b Signed-off-by: Gunnar Mills <gmills@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.