|
Post by dpugachev on Jul 2, 2024 18:32:21 GMT
Hello,
We have a device (power distribution unit) with a number of external sensor ports, which can be used to connect various environmental sensor devices. Each sensor device may include one or more sensors (temperate, humidity, etc). I'm wondering if there is a standard way/schema to represent such devices in Redfish, or should I just include each individual sensor in the Chassis SensorCollection as soon as it is detected? I would prefer to group them under a "sensor device" resource, but this does not seem to fit in any of the available resource types/schemas. I guess I could define an OEM resource type/collection (ExternalSensor, ExternalSensorCollection) and add a link to it from ServiceRoot (as an OEM property) so that it is discoverable, but I'm not sure if this will be visible to standard Redfish clients? I'm new to Redfish, so I may be missing something... I would appreciate any recommendations/pointers.
Thanks in advance, Dmitry
|
|
|
Post by mraineri on Jul 5, 2024 1:56:06 GMT
The best way to do this is to model a Sensor in the SensorCollection, but show its "State" as "Absent". This tells the client that the equipment supports a sensor in this location, but it's currently not populated. For example:
{ "@odata.id": "/redfish/v1/Chassis/1/Sensors/ExternalSensor1", "Id": "ExternalSensor1", "Name": "First external sensor slot", "Status": { "State": "Absent" }, "Location": { "PartLocation": { "ServiceLabel": "EXT SENS 1" } } } In this case, the resource it largely empty. Once a sensor is inserted, more properties can be added once the service detects the type of sensor installed.
We have these types of scenarios documented in the "Absent resources" clause of the Redfish Specification.
|
|