Enabling StartUpdate D-Bus interface for FirmwareUpdate

[Jagpal Singh Gill]

The Redfish cheatsheet<https://github.com/openbmc/docs/blob/master/REDFISH-cheatsheet.md> has been updated to include the HttpPushUri and MultipartHttpPushUri commands. By default, the HttpPushUri command is used for updating the BMC image only. To update other components such as the BIOS, one needs to use the MultipartHttpPushUri flow with multi-part form data by specifying the appropriate FirmwareInventory TargetURI.

On Nov 18, 2024, at 2:02 PM, Jagpal Singh Gill <jagpalgill at meta.com> wrote:

Hi

This email serves as a formal notification that the StartUpdate D-Bus interface flow will be enabled in BMCWeb and phosphor-bmc-code-mgmt by changing the defaults through patches  #1<https://gerrit.openbmc.org/c/openbmc/openbmc/+/75803> and #2<https://gerrit.openbmc.org/c/openbmc/bmcweb/+/75800>. This change is based on the design<https://github.com/openbmc/docs/blob/master/designs/code-update.md>.

The flow has been tested on romulus Qemu and IBM's p10bmc hardware, thanks to @Adriana for her help. In the meantime, if anyone is interested in testing the flow, they can use the above-mentioned patches (and related dependencies<https://gerrit.openbmc.org/q/topic:EnableUpdateInterface>) to test it locally.

Please let me know if you have any questions.

Regards
Jagpal S Gill


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20241118/6fc14404/attachment.htm>