|
Post by dchanman on Aug 31, 2021 18:01:43 GMT
Our specific question is on modelling an SSD. The resources for this would be: - Storage (representing the entire unit)
- Drive (representing the persistent memory)
- Processor (representing an FPGA)
- StorageController
- PcieDevice (representing its PCI endpoint in the host system)
How would we associate everything together to say that if any one of these parts fail, the SSD is the servicable unit that should be replaced?
There seems to not be Links for all of the resources to one another. Is it recommended that we add a Chassis to model the replaceable unit, and then link it to all of the above resources?
|
|
|
Post by mraineri on Sept 3, 2021 17:09:05 GMT
Primarily most of the FRU type of info would be found in the Drive resource. Things internal to the drive (such as processors and memory) are things an end user has no control over and typically does not have visibility in those details.
For NVMe drives, I can certainly see PCIeDevice resources being shown in the model alongside Drive resources to show the PCIe view of the device. Some clients may not care about this information, but it is supported in the model today.
Storage and StorageController are useful if you need to represent the subsystem view of the device. Depending on the construction of the subsystem, there may be multiple drives that support RAID types of operations, and various controllers that provide connectivity with the host system.
From a serviceability perspective, I would expect the Drive resource to be the container of that info. That resource represents the physical view of the FRU in question, and would have information such as the location of the drive in the enclosure. I would also expect a Chassis resource to represent the physical container around the drive, but it's probably going a step too far to have a Chassis resource for the drive itself. I would think it's more common to have some sort of rack mount enclosure represented as the Chassis resource (or whatever makes the most sense for the type of system you're using), which contains a collection of drives.
|
|