commit | 49e429ca172365bd4ba16c924501321c73527cbe | [log] [tgz] |
---|---|---|
author | Jonathan Doman <jonathan.doman@intel.com> | Wed Mar 03 13:11:44 2021 -0800 |
committer | Gunnar Mills <gmills@us.ibm.com> | Wed Jun 23 18:02:37 2021 +0000 |
tree | e443f82b251e78b5c56590dd3d0738fbc4a29822 | |
parent | 2205bbf681bfac508a9e985b9581ce9d662db4df [diff] |
Expose Processor PPIN property Some Processors may support exposing a globally unique identifier in addition to a serial number. Redfish supports this via ProcessorId.ProtectedIdentificationNumber property. ("Protected" indicates it may be a sensitive value due to tracking/privacy concerns - Intel CPUs allow the customer to mask the PPIN so it can't be exposed.) cpuinfoapp in smbios-mdr repo is currently implementing this interface. Tested: - New property is shown (only for cpus with valid PPIN) - Passed Redfish Service Validator with no errors. Signed-off-by: Jonathan Doman <jonathan.doman@intel.com> Change-Id: I233931ac640338e8f50f37ba4cc7298c7a0db9bf
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.