Redfish Firmware Update: Host server actions required; PSU, BIOS, etc

Redfish Firmware Update: Host server actions required; PSU, BIOS, etc

[Giles, Joshua]

Hello All,

Is there a plan/proposal for Redfish Firmware Updates (UpdateService/SimpleUpdate) that require host server actions?

For example, some vendor(s) may require the host be booted/rebooted in order to complete?

We'd like to merge our efforts around these behaviors with the upstream community.

-Josh Giles

Re: Redfish Firmware Update: Host server actions required; PSU, BIOS, etc

[Gunnar Mills]

On 4/23/2021 8:23 AM, Giles, Joshua wrote:
> Hello All,
> 
> Is there a plan/proposal for Redfish Firmware Updates (UpdateService/SimpleUpdate) that require host server actions?
> 
> For example, some vendor(s) may require the host be booted/rebooted in order to complete?

"ApplyTime" is how we determine when the update will be applied.
https://github.com/openbmc/phosphor-dbus-interfaces/blob/32304979b404c24e32f195d08c667e65b9b34695/xyz/openbmc_project/Software/ApplyTime.interface.yaml#L12

https://github.com/openbmc/docs/blob/f58df4f13cfcc67ef901cd3979ef7dd47da59dab/REDFISH-cheatsheet.md#firmware-applytime

That should all be supported today.
https://github.com/openbmc/bmcweb/blob/8d1b46d7f8d39db2ba048f9e9007106ca3a28c9b/redfish-core/lib/update_service.hpp#L576

RE: Redfish Firmware Update: Host server actions required; PSU, BIOS, etc

[Giles, Joshua]

> -----Original Message-----
> From: Gunnar Mills <gmills@linux.vnet.ibm.com>
> Sent: Friday, April 23, 2021 9:43 AM
> To: Giles, Joshua; Ed Tanous
> Cc: Rao, Balaji B; Brad Bishop; openbmc; Ed Tanous
> Subject: Re: Redfish Firmware Update: Host server actions required; PSU,
> BIOS, etc
> 
> 
> [EXTERNAL EMAIL]
> 
> On 4/23/2021 8:23 AM, Giles, Joshua wrote:
> > Hello All,
> >
> > Is there a plan/proposal for Redfish Firmware Updates
> (UpdateService/SimpleUpdate) that require host server actions?
> >
> > For example, some vendor(s) may require the host be booted/rebooted in
> order to complete?
> 
> "ApplyTime" is how we determine when the update will be applied.
> https://urldefense.com/v3/__https://github.com/openbmc/phosphor-dbus-
> interfaces/blob/32304979b404c24e32f195d08c667e65b9b34695/xyz/openb
> mc_project/Software/ApplyTime.interface.yaml*L12__;Iw!!LpKI!w_4kjGQjkc5
> JWPZLIcE9PchE4fdoX77Oj0IkzS8u2YhZE0ODPS62dHzvt_hq_fi6$ [github[.]com
> ]
>
BMC update using ApplyTime works great.
However for BIOS update, our requirements include rebooting the host (not BMC) in order for the update to take effect.

So, are you saying we would implement other methods w/in the ApplyTime interface?
Are there examples of how ApplyTime is being used _outside_ BMC firmware updates where a host A/C cycle is required for the update to complete?
 
> https://urldefense.com/v3/__https://github.com/openbmc/docs/blob/f58df
> 4f13cfcc67ef901cd3979ef7dd47da59dab/REDFISH-cheatsheet.md*firmware-
> applytime__;Iw!!LpKI!w_4kjGQjkc5JWPZLIcE9PchE4fdoX77Oj0IkzS8u2YhZE0O
> DPS62dHzvt1IAPPt6$ [github[.]com]
> 
> That should all be supported today.
> https://urldefense.com/v3/__https://github.com/openbmc/bmcweb/blob/8
> d1b46d7f8d39db2ba048f9e9007106ca3a28c9b/redfish-
> core/lib/update_service.hpp*L576__;Iw!!LpKI!w_4kjGQjkc5JWPZLIcE9PchE4f
> doX77Oj0IkzS8u2YhZE0ODPS62dHzvt4lRiVdJ$ [github[.]com]