|
Post by hanktsai on Jul 13, 2023 2:18:04 GMT
I check on the " Swordfish Scalable Storage Management API Users Guide_v1.2.5a" for chapter 7.1.21, it describe the use case of how to create a new Volume from a StoragePool. In this scenario, we need to POST to StoragePool resource with request body, then create volume. Follow previous description, which means the StoragePool resource property "insertable" value should be "true", but there seems some conflict for the definition. (1) In Swordfish schema file "StoragePool.json", the property "insertable" value is "false". (this means can not POST to create ?) (2) In Redfish doc DSP0266, in POST (create) chapter, which describe this operation " To create a resource, services shall support the POST method on resource collections.". (this means we can only POST to resource collections ?) I think the scenario "POST StoragePool resource to create new Volume resource" is reasonable, so might (1),(2) both need to do some adjust. Thanks for any reply !
|
|
|
Post by Richelle Ahlvers on Jul 14, 2023 13:42:39 GMT
There is a typo in that use case. The POST should be directed to the AllocatedVolumes Collection (posting the new volume to the VolumeCollection within the StoragePool). This matches the description in the "Basic course of events" section #1, to change the Request as follows:
POST /redfish/v1/Storage/1/StoragePools/PrimaryPool/AllocatedVolumes
|
|
|
Post by hanktsai on Jul 17, 2023 7:15:19 GMT
There is a typo in that use case. The POST should be directed to the AllocatedVolumes Collection (posting the new volume to the VolumeCollection within the StoragePool). This matches the description in the "Basic course of events" section #1, to change the Request as follows: POST /redfish/v1/Storage/1/StoragePools/PrimaryPool/AllocatedVolumes Thanks for the reply, understand it !
|
|
|
Post by hanktsai on Jul 17, 2023 7:55:46 GMT
There is a typo in that use case. The POST should be directed to the AllocatedVolumes Collection (posting the new volume to the VolumeCollection within the StoragePool). This matches the description in the "Basic course of events" section #1, to change the Request as follows: POST /redfish/v1/Storage/1/StoragePools/PrimaryPool/AllocatedVolumes I also check on the Swordfish_v1.2.5a_UserGuide, in chapter "7.1.21 Create Volume from an Existing Storage Pool". It describes the response body and location header as below image, seems the "odata.id" in the response body should be the same as "location header". Maybe also typo ? - (I know in some design, ".../StoragePools/<storagepool_id>/AllocatedVolumes/<volume_id>" can directly mapping to ".../Volumes/<volume_id>", which stands for the same volume) 
|
|
|
Post by Richelle Ahlvers on Jul 18, 2023 15:59:18 GMT
Thanks hanktsai - the response body should also refer to the full @odata.id in the AllocatedVolumes Collection. We will review the doc for other similar errors.
|
|