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

1 # Firmware update over Redfish
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
22 The Redfish schema for firmware update can be found [here][3]. Note the
29 - Redfish has a single upload and update API. OpenBMC has a concept of uploading
41 - Redfish does support the ability to update multiple targets with the same
46 - Redfish has the ability to schedule when a firmware update is applied
51 commands for their firmware update implementations ([ref a][5], [ref b][6]).
53 Redfish firmware update within OpenBMC has already started within [bmcweb][7]
68 - Support firmware update for all supported targets (BMC, BIOS) using existing
75   - Must provide status to user on their image during an update
83 will be required post 2.7 release. An update to this design document will be
89 - Support new UpdateService firmware update implementation defined in [Issue
91 - Support firmware update for other targets (power supplies, voltage regulators,
93 - Support to update multiple targets with the same firmware image at once
94 - Support scheduling of when update occurs (Maintenance windows)
97   - TODO: Any update mechanism that doesn't have transport security on its own,
98     like FTP, needs a secondary verification mechanism. Update mechanisms that
105 ### Update An Image
107 The pseudo flow for an update is:
130 to all firmware update packages and will be used for all subsequent firmware
131 update packages.
136 update. The Task concept is still being defined within the DMTF and will provide
168 ### Remote Image Download Based Update
180 The pseudo flow for an update is:
198 which is, by default, part of the update process. The user must have
199 administration authority to request this update so it is assumed they know what
221 required to make an enterprise based firmware update API. OpenBMC should just
227 This will be using the existing D-Bus API's for firmware update internally so
230 OpenBMC has two implementations of firmware update. Different systems have
236 End to end [tests][9] are being written for the firmware update of BMC and BIOS
242 …https://github.com/openbmc/docs/blob/master/architecture/code-update/code-update.md#steps-to-update