|
|
Post by jyundt on Jun 14, 2023 14:47:09 GMT
Is there any part of the spec that dictates the URI that should be used for the Target parameter when using SimpleUpdate? We have vendors inconsistently using a FirmwareInventory URI of the component to update (e.g. /redfish/v1/UpdateService/FirmwareInventory/BMC) and others that are using some random URI (e.g. /redfish/v1/Managers/1)
I was reading DSP2062 and it lists Target as "An array of strings that are URIs to resources that indicate where to apply the image." but wasn't sure if this was more clearly defined elsewhere.
|
|
|
|
Post by mraineri on Jun 14, 2023 15:44:19 GMT
We did add this text recently to the long description for Targets:
These targets should correspond to software inventory instances or their related items. If this parameter is not present or contains no targets, the service shall apply the software image to all applicable targets, as determined by the service. If the target specifies a device resource, the software image file shall be applied to the specified device. If the target specifies a resource collection, the software image shall be applied to each applicable member of the specified collection. If the target resource specifies an Aggregate resource, the software image file shall be applied to each applicable element of the specified aggregate. If the target resource specifies a ComputerSystem resource, the software image file shall be applied to the applicable components within the specified computer system.
It's not as strong as you'd like at the moment since you're looking for a stronger expectation about the types of resources that can be referenced. This has been a fairly open ended subject to date. I can certainly see both styles as valid since you are pointing to an exact instance to update, and I would think supporting both SoftwareInventory resources as well as specific device resources (like Manager) would be beneficial.
|
|
|
|
Post by jyundt on Jun 14, 2023 15:49:12 GMT
Ah that's helpful, I didn't see that in DSP0268
Agreed, that it's not as strong as I'd like, but it gives me something I can point the vendors to at least (even if it is a "should" vs "shall").
Thank you!
|
|
