commit | 938f25685f4b93d632fe5169cf5e258164538114 | [log] [tgz] |
---|---|---|
author | Ed Tanous <edtanous@google.com> | Fri Jun 11 09:34:52 2021 -0700 |
committer | Ed Tanous <ed@tanous.net> | Fri Jun 11 20:17:22 2021 +0000 |
tree | ff9399d7912a2255857757b2ed5bfe5373c3d33e | |
parent | 9552547ce8a48583a7f33fbbdc6748ff02d7661b [diff] |
Fix base registry validator failure The latest version of the registries causes a validator failure: "ERROR - Messages.UndeterminedFault.ParamTypes: Value of Collection property is null but Collections cannot be null, only their entries" This appears to be because of a base registry bug where UndeterminedFault has "NumberOfArgs": 1, but then is missing the ParamTypes key. This causes bmcweb to produce ParamTypes: null in the json, which is definitely incorrect. This commit throws some duct tape over the problem for the moment, and forces the key to at least be the correct type. This changes the response to: ParamTypes: [] While this is still incorrect, bmcweb now passes the service validator, which I think is ok for the moment. I will follow up with a DMTF bug against the base registry shortly, but because it will likely take them several months to release a new revision, this temporary fix will be required in the meantime. Tested: Ran service validator before and after this patch, and observed the aformentioned behavior, and the validator now passes on the base Registry schema. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: I7d007a0614e833b0a254c78cad068d3eb5fe88e3
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.