|
|
Post by kilgorep on Jan 17, 2024 21:48:12 GMT
Would it be considered a violation of DSP0248 to publish a single entity, as defined by a unique combination of Entity Type, Entity Instance Number, and Container ID, in a Entity Association PDR that represents a collection of like physical objects?
For example, consider as a PLDM terminus a storage controller with multiple drives attached, and the controller would like to provide sensor data for the drives to the MC. Would the controller be expected to define individual entity tuples for each drive, or would a single entity representing the collection of drives suffice, relying on the sensorId's to differentiate among the collection members?
|
|
|
|
Post by pmschoeller on Jan 23, 2024 16:18:03 GMT
Would it be considered a violation of DSP0248 to publish a single entity, as defined by a unique combination of Entity Type, Entity Instance Number, and Container ID, in a Entity Association PDR that represents a collection of like physical objects?
For example, consider as a PLDM terminus a storage controller with multiple drives attached, and the controller would like to provide sensor data for the drives to the MC. Would the controller be expected to define individual entity tuples for each drive, or would a single entity representing the collection of drives suffice, relying on the sensorId's to differentiate among the collection members?
Great and timely question. There is a proposal being discussed within the PMCI WG around a PLDM Scalable Sensor Model to address this exact scenario. Depending on the underlying details, this might work as a data model for your use case. For your model, there would be at 1 physical container (also known as an Entity Association Record) with a corresponding logical container to represent redundancy. I also suspect a logical container for the "logical RAID drive), comprised of multiple physical drives. For each physical drive, depending on the level of complexity, there may be an explicit container (entity association record) OR if all sensors on a drive reference the same tuple (Entity Type, Entity Instance Number, and Container ID), an implicit container can be formed by the PLDM Requester (such as the baseboard BMC). Where the PLDM Scalable Sensor model works is you might be able to reference each individual physical drive instance with one instance of PDR's and Containers and then scale out using an index (for the instance indicator). Today's PLDM enumerations do require full PDR enumerations for each object in the collection. The PLDM Scalable Sensor Model, if approved and published, will address this exact concern. |
|
