|
Post by manishg4 on Apr 28, 2018 17:13:01 GMT
The query is regarding the locationing of the DRIVE Elements in the schema; I have some confusion regarding the same because the mockup schemas for Redfish and Swordfish have different views: 1. Redfish Mockup : "Simple Rack-mounted Server with Local Storage " Link: redfish.dmtf.org/redfish/mockups/v1/864Under the Chassis Resource, in the LINKS section, there is no mention of Drives. This is even when the Chassis Schema has a provision for showing DRIVE data. In this mockup, the data related to Drives is present under Systems / <> / Storage resource. 2. Swordfish Mockup: swordfishmockups.com/redfish/v1/Here, the DRIVE info is showed under the Chassis resource as Chassis/ <>/ Links / Drive resource. Query: Going by the spec, the DRIVE info can be present under multiple resources; so I am not sure what should be the determining factor of where these should be placed. Is there any other resource where additional mock up schemas around Swordfish can be found? Thanks, Manish
|
|
|
Post by Manish on Apr 29, 2018 6:04:38 GMT
I have another related query to this: In the Chassis Schema files (latest being V1.6.0), I can see that under "Links" category, there is no reference to properties "StorageSystems" or even "StorageServices". Howerver, in the sample schema for Swordfish Mockup (http://swordfishmockups.com/redfish/v1/Chassis/StorageChassis1/), under the Chassis schema, there is a reference to "StorageSystems" under "Links". I think this is mis-leading.
Is there a different Chassis Schema that is to be referred?
Require some guidance.
Thanks, Manish
|
|
|
Post by Richelle Ahlvers on May 3, 2018 14:28:59 GMT
Manish - for your first question: It is generally up to the implementation to determine where to the instantiate the *actual* resource, unless there is an indicator in the schema to direct this. That is the "ContainsTarget=TRUE". (Note that this indicator generally refers to the Collection, not the actual object.) If this doesn't exist anywhere, it is left completely up to the implementation to decide.
|
|
|
Post by Richelle Ahlvers on May 3, 2018 14:33:57 GMT
For the Swordfish mockup bug - good catch. We use the mockups as a development tool when building and defining the spec, and this is a bug leftover from that process.
We'll update the mockups and remove this.
Thanks, Richelle
|
|
|
Post by manishg4 on Jun 8, 2018 7:55:05 GMT
Thanks, Manish
|
|