architecture/code-update/firmware-update-over-redfish.md

9 OpenBMC is moving to [Redfish][1] as its standard for out of band management.
15 OpenBMC's existing firmware update implementation over to Redfish.
19 The existing firmware update details for OpenBMC can be found [here][2]. It uses
27 Some differences between the Redfish API and OpenBMC's existing API:
29 - Redfish has a single upload and update API. OpenBMC has a concept of uploading
32   same target. OpenBMC does have support for this concept (for example when a
35   - OpenBMC has the concept of a priority that allows a user to chose an image
42   image with the same command. OpenBMC does not support this currently.
45   Existing OpenBMC only has support for TFTP.
47   (Immediate, OnReset, AtMaintenanceWindowStart...). Existing OpenBMC firmware
53 Redfish firmware update within OpenBMC has already started within [bmcweb][7]
59 OpenBMC 2.7 release. The other section is future items that will get done, but
61 with what the existing OpenBMC REST api's provide.
72     implemented by OpenBMC once approved. The existing API will continue to be
73     supported within the Redfish specification so the OpenBMC 2.7 release will
153 On OpenBMC systems that support multiple flash images for one target, there will
161 during the next activation window. Internally OpenBMC has the concept of a
162 priority being assigned to each image associated with a target. OpenBMC firmware
172 TFTP, ...). The existing back end of OpenBMC only supports TFTP so initially
173 that is all that will be supported via Redfish on OpenBMC.
177 interface on OpenBMC requires two parameters, the TFTP server address and the
191 # Request OpenBMC to download from TFTP server and activate the image
197 it and no validation of the input URL. OpenBMC does have signed image support
217 Could simply create Redfish OEM api's that look like OpenBMC's current custom
218 REST api's. The porting would be minimal but then OpenBMC would not conform to
221 required to make an enterprise based firmware update API. OpenBMC should just
230 OpenBMC has two implementations of firmware update. Different systems have
242 …https://github.com/openbmc/docs/blob/master/architecture/code-update/code-update.md#steps-to-update
250   https://github.com/openbmc/bmcweb/blob/master/redfish-core/lib/update_service.hpp
252 …https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Software/…
253 [9]: https://github.com/openbmc/openbmc-test-automation
258 …https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Software/…