commit | 6e3b67ecec7c66d674a6707b6211786fc0704d8a | [log] [tgz] |
---|---|---|
author | AppaRao Puli <apparao.puli@intel.com> | Thu Jan 06 01:37:08 2022 +0000 |
committer | Ed Tanous <ed@tanous.net> | Mon Jan 10 17:21:57 2022 +0000 |
tree | ace830319808a23109a3e1f0496eec9473f10c1c | |
parent | 12778e61c281b8f8c0f976dec225fb0c30edcb47 [diff] |
Convert VariantType to DbusVariantType All bmcweb code is now converted to use DbusVariantType to reduce the image size. Its missed in one place where the code is under compiler flag BMCWEB_ENABLE_REDFISH_PROVISIONING_FEATURE. This commit convert missed types to DbusVariantType. Tested: After conversion, image builds fine with compiler flag enabled. Also tested the PFR provisioned dbus calls and it works fine. Change-Id: Idcef956a18a6f822c44399ef867e26551dd8124f Signed-off-by: AppaRao Puli <apparao.puli@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 -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.