|
Post by harim on Feb 17, 2017 19:39:42 GMT
I am new to redfish and swordfish. In trying to understand the swordfish schema, I was going through the mockups posted on SNIA. The StorageGroup schema points to a volume collection. However, one mockup shows a list of volumes while the other shows a collection of volumes. I presume the latter is correct? See relevant cut pastes below-
/redfish/v1/StorageServices/FileService/Storage/StorageGroups/1 :-
"@odata.context": "/redfish/v1/$metadata#StorageGroup.StorageGroup",
"@odata.id": "/redfish/v1/StorageServices/FileService/Storage/StorageGroups/1",
"@odata.type": "#StorageGroup_1_0_0.StorageGroup",
...
"Volumes": [
{
"@odata.id": "/redfish/v1/StorageServices/FileService/Volumes/61001234876545676100123487654567"
},
{
"@odata.id": "/redfish/v1/StorageServices/FileService/Volumes/65456765456761001234876100123487"
}
],
...
Whereas /redfish/v1/StorageServices/1/StorageGroups/1 shows a volume collection :-
"@odata.context": "/redfish/v1/$metadata#StorageGroup.StorageGroup/1",
"@odata.id": "/redfish/v1/StorageServices/1/StorageGroups/1",
"@odata.type": "#StorageGroup_1_0_0.StorageGroup",
...
"Volumes": {"@odata.id": "/redfish/v1/StorageServices/1/Volumes"},
...
|
|
|
Post by Richelle Ahlvers on Feb 21, 2017 16:35:31 GMT
Hamim,
Thanks for your question - you are correct. The "Volumes" property in the StorageGroup mockup under FileService should point to the StorageServices/1/Volumes Collection, not to an array on the (non-existent) FileService/Volumes.
"Volumes": {"@odata.id": "/redfish/v1/StorageServices/1/Volumes"},
We will log an issue and fix this in the next mockup release.
Thanks, Richelle
|
|
|
Post by harim on Feb 21, 2017 19:03:50 GMT
Thank you.
|
|