commit | c0bd5e4b37f65ce29a392594d1ef240c64c99734 | [log] [tgz] |
---|---|---|
author | Ed Tanous <edtanous@google.com> | Mon Sep 13 17:00:19 2021 -0700 |
committer | Ed Tanous <ed@tanous.net> | Wed Sep 22 17:31:26 2021 +0000 |
tree | c63ad3326fd6bb871b4031ddf067151ce444fda1 | |
parent | 58e42b189dedd843f721b3a1c943f95ede0b2ca7 [diff] |
Move log service file parsing to use from_chars std::from_chars seems to be what most other bmcweb code has moved to, and allows removal of exceptions usage. Tested: Ran redfishtool -S Always -A Session -u root -p 0penBmc -r 192.168.7.2 raw GET "/redfish/v1/Managers/bmc/LogServices/Journal/Entries/1632252609998258" And observed that the uri component got parsed properly. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: Icd4808196eeae0f8a19a208a065b5f2f4f0b050c
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.