|
|
Post by vincent0607 on Oct 21, 2022 9:16:44 GMT
Hi, from the DMTF firmware update white paper, www.dmtf.org/sites/default/files/standards/documents/DSP2062_1.0.0.pdfin 7.1 chapter : "Transfer the firmware image to the manager" in this stage, seems like user can not know if manager (BMC) is downloading a FW image from remote server when using 'Pull' FW update method. not sure if you will consider add some message to DMTF 'Update' message registry, for example below * Update.TransferringToManager * Update.TransferToManagerFailed and then apply its to FW Update white paper guide (having another new version) |
|
|
|
Post by jautor on Oct 21, 2022 14:38:24 GMT
I'll bring that to the group to discuss, but that seems to be a reasonable addition, as we have "progress" and "failure" messages defined for the other steps in the process - and a "failure to upload" is certainly not an uncommon fault condition.
Jeff
|
|
|
|
Post by vincent0607 on Oct 24, 2022 2:19:00 GMT
thanks your reply,
besides, in 7.2 chapter, "Verification of the firmware image on the manager"
in this stage, seems like user can not know if manager (BMC) is verifying a FW image status or verification failed.
not sure if you will also consider add the others message to DMTF 'Update' message registry, for example below
* VerifyingAtManager
* VerificationAtManagerFailed
|
|
|
|
Post by mraineri on Oct 24, 2022 16:50:22 GMT
What's the advantage of making a distinction between the manager and other components? A manager is a type of component, and the end result for what a client might do in response to these conditions is the same.
|
|
|
|
Post by vincent0607 on Oct 25, 2022 0:16:08 GMT
What's the advantage of making a distinction between the manager and other components? A manager is a type of component, and the end result for what a client might do in response to these conditions is the same. Thanks your explanation, and agree with you. So, can we use directly following message in stage of "Transfer the firmware image to the manager" (7.1 chapter) ? * TransferringToComponent * TransferFailed and "Verification of the firmware image on the manager" (7.2 chapter) ? * VerifyingAtComponent * VerificationFailed |
|
|
|
Post by mraineri on Oct 25, 2022 14:20:30 GMT
Keep in mind the context of "Transfer the firmware image to the manager" is really tied to the usage of the SimpleUpdate action and the multipart HTTP push URI. For SimpleUpdate, the usage is to direct the manager to download an image remotely, which has stronger mappings to the existing message in the Base registry (they're designed for conveying inaccessible URIs and other external service conditions). For multipart, a failed transfer of the image to the manager would equate to the entire HTTP operation from the client failing, and the client would likely see HTTP timeouts in this case rather than any error message.
For "Verification of the firmware image on the manager", your follow-up comment is correct.
|
|
|
|
Post by vincent0607 on Oct 27, 2022 1:46:15 GMT
Thanks for your reply, as you mention, the context of "Transfer the firmware image to the manager", for SimpleUpdate, it already included many 'Base' error message for usage, but user might also want to know if manager is downloading from remote network. So would like to confirm with you if following message can be used in this stage to notify a user of status to being downloaded.
* "Update.TransferringToComponent" (param component name : "Manager")
|
|
|
|
Post by mraineri on Oct 27, 2022 12:45:10 GMT
Yes, thinking about your case more, I can see a task being produced immediately after the SimpleUpdate request, meaning it would be useful to show "download in progress". Given that usage, I agree; that type of message is useful.
|
|
|
|
Post by vincent0607 on Oct 28, 2022 7:21:59 GMT
Let us have a summary according above discussion.
In some 'update' stage from DMTF firmware update white paper, can have message registry extra supplement and usage as below
1. in 7.1 chapter : "Transfer the firmware image to the manager"
* Update.TransferringToComponent
2. in 7.2 chapter : "Verification of the firmware image on the manager"
* Update.VerifyingAtComponent
* Update.VerificationFailed
Also, could you have a minor revision version in this white paper ?
|
|
|
|
Post by mraineri on Oct 31, 2022 14:19:43 GMT
Sure, I'll raise this to others to discuss to see if they also agree and want it in the white paper.
|
|
