commit | dba0c291b5bbd8d256387ba43bb48bda82a191dc | [log] [tgz] |
---|---|---|
author | Jonathan Doman <jonathan.doman@intel.com> | Wed Dec 02 15:34:13 2020 -0800 |
committer | Ed Tanous <ed@tanous.net> | Fri Dec 04 00:07:40 2020 +0000 |
tree | 019aed1f6933cc66c162e6ddb2f2381d5c8ae20a | |
parent | 2bab9831767c180bedd005dfcbeb65af8798f088 [diff] |
Add support for Redfish OperatingConfig resources - Update Processor GET handler to look for a matching CurrentOperatingConfig interface on D-Bus. - Add OperatingConfig node and implement GET handler to look for matching OperatingConfig interface on D-Bus. - Add OperatingConfigCollection node and implement GET handler to look for all OperatingConfig interfaces on D-Bus under the given cpu. Tested: - Ran Redfish Service Validator and verified no errors or warnings on Processor, OperatingConfig, and OperatingConfigCollection. - Browsed OperatingConfig links and resources in browser, confirmed nonexistent configs returned 404 and didn't crash bmcweb. - Killed D-Bus provider service and verified bmcweb didn't crash and still served Processor as before, and passed service validator. Change-Id: Iab94b7fd49a9462cb0eca6f8ea0754f5fb241053 Signed-off-by: Jonathan Doman <jonathan.doman@intel.com>
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 -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.