commit | 5b9e95a17fae7aaf9f8716b65345bb64ade5f403 | [log] [tgz] |
---|---|---|
author | Nan Zhou <nanzhoumails@gmail.com> | Wed Jun 01 17:12:23 2022 +0000 |
committer | Ed Tanous <ed@tanous.net> | Wed Jun 08 02:26:49 2022 +0000 |
tree | a066a849ad7b564e52cea7df3a12a34f73e2c154 | |
parent | 2c5cb5120349490aff5a0d5240528f6803003e26 [diff] |
Chassis: fix ResetActionInfo There is a regression that "Parameters" in ActionInfo now become an object rather than an array, as defined in the Schema, https://redfish.dmtf.org/schemas/ActionInfo.v1_2_0.json Tested: 1. On my mock environment, { "@odata.id": "/redfish/v1/Chassis/fake_chassis/ResetActionInfo", "@odata.type": "#ActionInfo.v1_1_2.ActionInfo", "Id": "ResetActionInfo", "Name": "Reset Action Info", "Parameters": [ { "AllowableValues": [ "PowerCycle" ], "DataType": "String", "Name": "ResetType", "Required": true } ] } 2. Redfish Service Validator passes ``` *** /redfish/v1/Chassis/fake_chassis/ResetActionInfo Attempt 1 of /redfish/v1/Chassis/fake_chassis/ResetActionInfo Response Time for GET to /redfish/v1/Chassis/fake_chassis/ResetActionInfo: 0.0017544100992381573 seconds. Type (ActionInfo.v1_1_2.ActionInfo), GET SUCCESS (time: 0:00:00.001957) PASS ``` Signed-off-by: Nan Zhou <nanzhoumails@gmail.com> Change-Id: I85d1c14d6a37b6f360732ee107d0163c2d3ff15f Signed-off-by: Ed Tanous <edtanous@google.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/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 -C builddir test ninja -C builddir coverage
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.