|
Post by zephyryin on Apr 16, 2021 17:56:41 GMT
Hi
I run redfish service validator on my redfish server, the check passed on uri /redfish/v1/Systems/system/Storage/U2_2, while it failed on uri /redfish/v1/Systems/system/Storage/U2_2#/StorageControllers/0: "NVMeControllerProperties not defined in schema Storage.v1_10_0" I wonder if "@odata.type": "#StorageController.v1_1_0.StorageController" should be added under the StorageControllers?
Here is my storage payload: { "@odata.id": "/redfish/v1/Systems/system/Storage/U2_2", "@odata.type": "#Storage.v1_10_0.Storage", "Drives": [ { "@odata.id": "/redfish/v1/Systems/system/Storage/U2_2/Drives/0" } ], "Id": "U2_2", "Name": "U2_2", "StorageControllers": [ { "@odata.id": "/redfish/v1/Systems/system/Storage/U2_2#/StorageControllers/0", "Links": { "PCIeFunctions": [ { "@odata.id": "/redfish/v1/Systems/system/PCIeDevices/0000:b1:00/PCIeFunctions/0" } ] }, "NVMeControllerProperties": { ... }, } ] ... }
|
|
|
Post by jautor on Apr 16, 2021 20:44:03 GMT
That is an accurate error being flagged by the tool. The NVMe controller support was not added to the "StorageControllers" object array in Storage. Rather, that support was created in the (replacement) StorageController schema, which will attach under your Storage resource - the relatively new "Controllers" link to a collection of StorageController resources.
That should be a relatively easy change for you - the contents of the StorageController schema were copied from the Storage/StorageController definitions. And I think you'll find that your client-side software will be much happier dealing with a resource collection instead of a JSON array for that data.
Jeff
|
|
|
Post by j2hilland on Apr 16, 2021 21:18:06 GMT
|
|