|
Post by paligill on May 16, 2024 21:52:21 GMT
Hi In case multiple Target URIs are passed as an array for TargetURI option, whats the way to track the status? Is update service suppose to return an array of Tasks, where the each tasks pertains to an entry in TargetURI array? I don't see any such use case in the Redfish White Paper www.dmtf.org/sites/default/files/standards/documents/DSP2062_1.0.1.pdf. Regards Jagpal S Gill
|
|
|
Post by mraineri on May 17, 2024 12:23:52 GMT
You'd still get a single task; there's no way in Redfish to spawn multiple tasks from a single operation.
If you really do need to break down the management to have a different task per target, then you could use "SubTasks" to express this (or "Steps" in the Job resource if you transitioned to a Job as part of the flow). However, the client's handling will always stem from the the root task or job, so it's important to surface all relevant messages from the sub tasks or steps.
|
|
|
Post by paligill on May 21, 2024 21:31:57 GMT
Mike, what should be a valid TargetURI, for example in case of BMC Manager -
1. /redfish/v1/Managers/bmc 2. /redfish/v1/UpdateService/FirmwareInventory/xxx
I couldn't find any examples in the Update Service white paper, but update service schema has this description "These targets should correspond to software inventory instances or their related items". So, i am wondering if both the options are valid?
|
|
|
Post by shawnw on May 22, 2024 2:42:06 GMT
paligill, You could try to see the Task URI in the TaskService. There's also a task monitor uri from the response header to help you to track the task.
|
|
|
Post by mraineri on May 22, 2024 12:07:29 GMT
Mike, what should be a valid TargetURI, for example in case of BMC Manager - 1. /redfish/v1/Managers/bmc 2. /redfish/v1/UpdateService/FirmwareInventory/xxx I couldn't find any examples in the Update Service white paper, but update service schema has this description "These targets should correspond to software inventory instances or their related items". So, i am wondering if both the options are valid?
Both options are valid. Some users may opt to specifying a "device resource" (like /redfish/v1/Managers/bmc) or something in the inventory (/redfish/v1/UpdateService/FirmwareInventory/xxx). We have the following statements in the long description for "Targets" to cover all possible usage.
> 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.
|
|