|
|
Post by ratagupt on May 18, 2023 11:40:01 GMT
>From a payload perspective, "task monitor" and "task" follow the same schema definition and contain the same contents, but have different URIs. "Task monitor" has the added semantic where the response to the GET operation on the task monitor when the operation is complete is the response to the initial request.
@mike Ranier: What about if we are streaming a large binary data(GB) out, It can not fit in the Response of the task monitor URI once the task is completed
|
|
|
|
Post by mraineri on May 18, 2023 13:50:58 GMT
How would it fit in any response if that's the case? Normally we use supplemental URIs to direct the client to a non-Redfish payload (like the BinaryDataUri property in Assembly), especially if the payload is large. However, even for non-Redfish URIs, you'll likely have the same hurdle of supplying a large payload in the response. Ultimately this is going to dependent on the limitations of your web server.
|
|
|
|
Post by ratagupt on May 24, 2023 8:11:06 GMT
@mike in that case when the task completes, Location header would be updated with the URI which will be used to fetch the data but the task monitor output would not give the response to the intitial request. Is that true?
eg:
- Collect the BMC dump data which is binary data
- Start the task
- Task complete
- Task monitor output is 204(NO Content) and location header would be updated with the supplemental URI
|
|
|
|
Post by mraineri on May 24, 2023 12:45:15 GMT
In the case you're describing, that's what would happen; that looks like the correct flow to me.
Think about it this way; let's assume that no task is ever produced and the data is available immediately. The client requests the data collection, and the response contains 204 with a Location header pointing to the supplemental URI; everything between for task monitoring is cleanly removed.
|
|
|
|
Post by AMI_ivywang on Jan 30, 2024 7:14:29 GMT
Hi,
Is there a specific format for the task monitor resource?
For example:
"TaskMonitor": "/redfish/v1/TaskService/Tasks/{{Task_ID}}/Monitor"
"TaskMonitor": "/redfish/v1/TaskService/TaskMonitors/{{Task_ID}}"
|
|
|
|
Post by mraineri on Jan 30, 2024 14:30:08 GMT
The "Redfish-defined URIs and relative reference rules" clause calls out the form "/redfish/v1/TaskService/TaskMonitors/<TaskMonitorId>" for task monitor URIs.
|
|
