|
|
Post by mharishm on Feb 1, 2022 14:43:03 GMT
Does the redfish spec allows to create a task(based on TaskService schema) when user gives a GET call for certain redfish URIs? If it is allowed, is there any way to represent the resource response along with task instance?
|
|
|
|
Post by jautor on Feb 1, 2022 18:00:54 GMT
While a Task could be created on a GET, for complex items like retrieving data from an RDE device, you should avoid that whenever possible.
The Redfish standard resources were designed with the expectation that the service either has the payload contents readily accessible, or can gather and respond within a reasonable timeout. If you're finding that not to be true in some case, please let us know so we can investigate and discuss that case.
But there are certainly times when you want the service to gather information that may take seconds or even minutes to complete. A frequent use case is to perform a memory dump / crash report / full diagnostic report / etc. So we added support for "CollectDiagnosticData" in 2020.3 release of LogService. "CollectDiagnosticData" is an Action (POST) that will result in a LogEntry that includes a link to the resulting data shown in "AdditionalDataURI". That Action could result in a Task being created, with the LogEntry eventually being created - the client can watch the TaskMonitor to follow the progress and obtain the direct link to the new LogEntry resource.
The "CollectDiagnosticData" Action allows for OEM data types, so this may offer a solution to your needs.
Jeff
|
|
|
|
Post by mharishm on Feb 2, 2022 12:57:08 GMT
Thanks Jeff for the quickly reply.
Yeah, our purpose is also similar to getting the dump/diagnostic report where we communicate with external device to get telemetry data and the GET response depends on how fast the external device responds. |
|
