commit | 12c7f4388b58a974265827ab62d3981ba98ed8f2 | [log] [tgz] |
---|---|---|
author | jayaprakash Mutyala <mutyalax.jayaprakash@intel.com> | Fri Mar 20 17:31:36 2020 +0000 |
committer | jayaprakash Mutyala <mutyalax.jayaprakash@intel.com> | Fri Mar 20 17:31:36 2020 +0000 |
tree | a546bb0ace6bac40d5d52279770ba31aa221526e | |
parent | 5db4be2178fdeb09f95b58471cbdee7f76f8254b [diff] |
Fix for message_registry entries count mismatch BMCWEB repo build is failing due to mismatch in number of message registry entries. So updated with correct message entry count. Tested: Redfish validator - passed Signed-off-by: jayaprakash Mutyala <mutyalax.jayaprakash@intel.com> Change-Id: I69ad2850c862a1173987554da06163014a222b84
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/CMakeLists.txt
and then compiling. For example, cmake -DBMCWEB_ENABLE_KVM=NO ...
followed by make
. The option names become C++ preprocessor symbols that control which code is compiled into the program.
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.