commit | eb75770c6c4369984cb150ded4f5ace410ed24a9 | [log] [tgz] |
---|---|---|
author | Abhishek Patel <Abhishek.Patel@ibm.com> | Fri May 21 14:17:33 2021 -0500 |
committer | Ed Tanous <ed@tanous.net> | Thu Jun 03 02:27:52 2021 +0000 |
tree | 32c50d37df87ceff11760557af65648e3259c348 | |
parent | 92696982a22d8952b16c399f88898623d9e8b8ab [diff] |
Update Redfish.md with new schemas and properties - Redfish.md has quite old schemas and property. This commit makes it more up-to-date. - added newfound schemas and properties using "RedfishVersion": "1.9.0" API - Arranged all schemas and properties as we get on our redfish server - adding '\' between any URL to Disable Autolinking Ex: Members\@odata.count Note: These schemas and properties are as accurate as the Witherspoon bmcweb server, from where this data retrieved Signed-off-by: Abhishek Patel <Abhishek.Patel@ibm.com> Change-Id: I9def930c8372110d8a70f7d68773ac024cd32dff
This component attempts to be a "do everything" embedded webserver for openbmc.
At this time, the webserver implements a few interfaces:
BMCWeb is configured by setting -D
flags that correspond to options in bmcweb/meson_options.txt
and then compiling. For example, meson <builddir> -Dkvm=disabled ...
followed by ninja
in build directory. The option names become C++ preprocessor symbols that control which code is compiled into the program.
meson builddir ninja -C builddir
meson builddir -Dbuildtype=minsize -Db_lto=true -Dtests=disabled ninja -C buildir
If any of the dependencies are not found on the host system during configuration, meson automatically gets them via its wrap dependencies mentioned in bmcweb/subprojects
.
meson builddir -Dwrap_mode=nofallback ninja -C builddir
meson builddir -Dbuildtype=debug ninja -C builddir
meson builddir -Db_coverage=true -Dtests=enabled ninja coverage -C builddir test
When BMCWeb starts running, it reads persistent configuration data (such as UUID and session data) from a local file. If this is not usable, it generates a new configuration.
When BMCWeb SSL support is enabled and a usable certificate is not found, it will generate a self-sign a certificate before launching the server. The keys are generated by the secp384r1
algorithm. The certificate
C=US, O=OpenBMC, CN=testhost
,SHA-256
algorithm.