commit | 29d2a95ba12f8b5abed040df7fd59790d6ba2517 | [log] [tgz] |
---|---|---|
author | James Feist <james.feist@linux.intel.com> | Wed Jun 10 09:41:44 2020 -0700 |
committer | James Feist <james.feist@linux.intel.com> | Thu Jun 11 17:53:20 2020 +0000 |
tree | 0b6804b6a708213c71facca440d39f7be63c611e | |
parent | 35e257a6938c5b853ff074658ac35823a2eded24 [diff] |
Revert "EventService: Add event log support with inotify" This reverts commit e9a14131650d30389eaf9dc38a3c32f1cb552f52. Reason for revert: if /var/log/redfish does not exist this causes bmcweb to crash on start Fixes #126 Change-Id: If6ba4717a32d4cd72aa92a9bc9c696d5813b5cac Signed-off-by: James Feist <james.feist@linux.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/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.