commit | c8ccb7745d1f4993176f2689a7811e09fad9b840 | [log] [tgz] |
---|---|---|
author | Asmitha Karunanithi <asmitk01@in.ibm.com> | Tue Sep 22 10:56:46 2020 -0500 |
committer | Asmitha Karunanithi <asmitk01@in.ibm.com> | Thu Sep 24 12:25:26 2020 -0500 |
tree | 5b739cdf3e5be8fe8572b0d776f72521ed32d28d | |
parent | 4841191fed358da53d4c00c9866151dce54bd6a2 [diff] |
Move to 2020.3 Run the script update_schemas.py by pointing it to 2020.3 An overview of 2020.3 release can be found at: https://www.dmtf.org/sites/default/files/Redfish_Release_2020.3_Overview.pdf Tested: Loaded on a Witherspoon and Validator passed with the latest schemas Signed-off-by: Asmitha Karunanithi <asmitk01@in.ibm.com> Change-Id: I6c7a2e0cbdbe599930ba453a1d8c134c22136306
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.