|
|
Post by AMI_shirleyh on May 25, 2022 19:18:50 GMT
Hi,
I'm looking for support for updating multiple components with multiple images provided in the single request for FirmwarUpdate (eg. PLDMBundle).
But we have the following description for HttpPushURI:- " "This property shall contain a URI at which the update service supports an HTTP or HTTPS POST of a software image for the purpose of installing software contained within the image."
Also we do not have provision to specify which Bundle or image needs a StartUpdate Action. [ Eg: In case we provide multiple images in a single request or multiple bundles ]
Also target property under StartUpdate is a String and not an array.
So for now as it seems, StartUpdate is designed for updating a specific component image at the given target.
Q1. Can we achieve multiple target updations with multiple components specified in a single request action with OEM Actions as of now or can you suggest any possible way with existing implementation ?
Q2. Are you planning to enhance the standard UpdateService Schema to support this scenario in the upcoming schemas?
|
|
|
|
Post by mraineri on May 26, 2022 11:30:04 GMT
The image provided by the client when using the HTTP push URI can internally contain many software packages. The format of the image is not dictated by Redfish. The "target" property in an action is not a parameter provided by the client; "target" is the way the service tells the client the URI that is used to invoke the action. The "StartUpdate" action is not used to provide an image or specify what devices are updated. "StartUpdate" is used in conjunction with either "SimpleUpdate" or a push update request where the client requested the update to be deferred until the "StartUpdate" action is invoked (using "@redfish.OperationApplyTime" with the value "OnStartUpdateRequest"). It's expected that when the client goes this path that they provide all of the necessary parameters for the update when invoking "SimpleUpdate" or the push update (along with "@redfish.OperationApplyTime" with the value "OnStartUpdateRequest"), and when the client is ready to begin the requested update, they invoke "StartUpdate". For question 1, yes, you can perform multiple updates in a single request. OEM actions are not needed. For question 2, there are no updates planned. It seems like everything is covered today. It may be worth reviewing the Redfish Firmware Update White Paper that goes into the client flows in more detail: www.dmtf.org/sites/default/files/standards/documents/DSP2062_1.0.0.pdf |
|
|
|
Post by AMI_shirleyh on May 30, 2022 13:14:42 GMT
Thank will look into it and get back to you if I've any more queries.
|
|
