Drives in NVMe-oF JBOF mockup,

jebr224
Minnow

Posts: 2

Drives in NVMe-oF JBOF mockup, Jun 10, 2022 0:52:37 GMT

Quote

Post by jebr224 on Jun 10, 2022 0:52:37 GMT

There is a question related to correct redfish behavior, specifically in the to the NVMe-oF JBOF mockup.

The drive resource can be accessed from both:

"redfish » v1 » Chassis » 1 » Drives"
"redfish » v1 » Storage » NVMeoF"

The chassis schema would indicate this is correct

redfish.dmtf.org/schemas/Chassis.v1_20_0.json

"Drives": {
   "description": "An array of links to the drives located in this chassis.",
   "items": {
     "$ref": "http://redfish.dmtf.org/schemas/v1/Drive.json#/definitions/Drive"
    },
    "longDescription": "This property shall contain an array of links to resources of type Drive that are in this chassis.",
    "readonly": true,
    "type": "array",
    "versionAdded": "v1_2_0"
}

The storage schema would indicate this is correct

redfish.dmtf.org/schemas/Storage.v1_13_0.json

"Drives": {
   "description": "The set of drives attached to the storage controllers that this resource represents.",
   "items": {
      "$ref": "http://redfish.dmtf.org/schemas/v1/Drive.json#/definitions/Drive"
   },
   "longDescription": "This property shall contain a set of the drives attached to the storage controllers that this resource represents.",
   "readonly": true,
   "type": "array"
}

Thank you

Last Edit: Jun 11, 2022 3:44:47 GMT by jebr224: Total re-write of the question.

mraineri
Administrator

Posts: 1,050

Drives in NVMe-oF JBOF mockup, Jun 13, 2022 13:02:35 GMT

Quote

Post by mraineri on Jun 13, 2022 13:02:35 GMT

When the Storage model was first introduced, "Drives" was placed directly in Storage. Over time, this created problems in terms of understanding the physical location of drives. For example, a storage sub-system for a server might have drives in a cabled enclosures that is not physically with the server. Drives was added to Chassis to help with this, and it's recommended to model Drives under Chassis in order to make the physical containment of devices clear to users.

jebr224 Minnow Posts: 2	Drives in NVMe-oF JBOF mockup, Jun 13, 2022 17:34:44 GMT Quote Select Post Deselect Post Link to Post Back to Top Post by jebr224 on Jun 13, 2022 17:34:44 GMT Thanks for getting back to me, and thanks for providing some context. Would it be a correct usage of Redfish, to have the same Drive resources modeled in Chassis, and in Storage? (similar to the NVMe-oF JBOF mockup) Thank you

mraineri
Administrator

Posts: 1,050

Drives in NVMe-oF JBOF mockup, Jun 13, 2022 17:52:00 GMT

Quote

Post by mraineri on Jun 13, 2022 17:52:00 GMT

Yes, showing it in both places is important; the storage view allows a user to see the drives that are available within a single storage subsystem, while the chassis view allows a user to see the physical containment. In addition, as shown in the mockup, the URIs shown in the "Drives" property in Storage will be the same URIs found in the DriveCollection under Chassis, so two different clients following the different property paths will ultimately end up at the same URI for a given drive.

However, keep in mind the NVMe-oF JBOF mockup is rather simplistic in that there's a single storage subsystem containing all of the drives in the sole chassis. It's entirely possible that a single enclosure has many storage subsystems, or drives from multiple enclosures participate in a single storage subsystem.

Post by jebr224 on Jun 10, 2022 0:52:37 GMT

Post by mraineri on Jun 13, 2022 13:02:35 GMT

Post by jebr224 on Jun 13, 2022 17:34:44 GMT

Post by mraineri on Jun 13, 2022 17:52:00 GMT