commit | d61e5194f59793356d812c418aaf3d9ba5137884 | [log] [tgz] |
---|---|---|
author | Tejas Patil <tejaspp@ami.com> | Fri Jun 04 15:49:35 2021 +0530 |
committer | Ed Tanous <ed@tanous.net> | Wed Jun 09 19:51:04 2021 +0000 |
tree | ccd0f59c81c10811b4ab4a186a916dc478e235e4 | |
parent | b282a4380670e5232e7b6f9a08234d3bdbadb5ff [diff] |
Add support for MaxImageSizeBytes in UpdateService This commit adds the support for "MaxImageSizeBytes" property in the "/redfish/v1/UpdateService/" Redfish URI. This property indicates that, the maximum size of the software update image, that clients can send to this Update Service. Tested: - Redfish Validator Test passed. curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/json" -X GET https://${bmc}/redfish/v1/UpdateService { "@odata.id": "/redfish/v1/UpdateService", "@odata.type": "#UpdateService.v1_4_0.UpdateService", "Description": "Service for Software Update", "FirmwareInventory": { "@odata.id": "/redfish/v1/UpdateService/FirmwareInventory" }, "HttpPushUri": "/redfish/v1/UpdateService", "HttpPushUriOptions": { "HttpPushUriApplyTime": { "ApplyTime": "OnReset" } }, "Id": "UpdateService", "MaxImageSizeBytes": 31457280, "Name": "Update Service", "ServiceEnabled": true } Signed-off-by: Tejas Patil <tejaspp@ami.com> Change-Id: Ibc0f3094a50ea7eb274436e4359e05c95d9cec36
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.