|
|
Post by nanzhou on Jul 14, 2021 17:19:04 GMT
Hi everyone,
In OpenBMC, there is a concept of Fan Zones. A fan zone groups several fans together and control them in a PID loop. Fan zones have an important property: mode, which can either be Auto or Manual to indicate status of PID control. I've searched the Redfish Schema a bit but didn't find a clear way to model such "Zone" concept. We currently use an OEM under the Thermal subsystem to control the mode of fan zones. But we would like a formal way in the Redfish Schema so everyone (in the OpenBMC community) can use it.
Any suggestions?
|
|
|
|
Post by jautor on Jul 15, 2021 19:34:27 GMT
We'd like to see a proposal for this, but if this is only for system validation / testing purposes (we don't normally see products allowing users to disable PID loops as that leads to failures and service provider/warranty issues, etc.), it may be sufficient to just add a "TestMode" boolean property on Fan that allows that (perhaps with a "system under test" flag elsewhere to enable that feature). A "fan group" on its own doesn't describe much more than what PhysicalContext already provides - unless that concept is fleshed out to really show what that group really means (what subsystems is it cooling?). For the actual implementation, take a look at the Controls schema proposal: www.dmtf.org/sites/default/files/standards/documents/DSP-IS0017-v0.5.zip - although for a simple "mode" property this may just be a simple boolean property as I mentioned above. Jeff |
|
|
|
Post by echuang on Dec 30, 2021 4:50:37 GMT
The PhysicalContext provides context, but seems it doesn't provide instance info. For example, if there are 2 fan zones, one for bay 0, and the other for bay 1, physical context seems not able to identify which bay the fan associates.
|
|
|
|
Post by jautor on Jan 4, 2022 21:58:47 GMT
That's correct, PhysicalContext won't help identify instances.
Thinking about this again, with the new Fan and ThermalSubsystem schemas (replacement for the now deprecated Thermal schema), we defined the FanRedundancy[] array using the new RedundancyGroup common definition, which can model a fan group easily.
The one piece missing there would be perhaps an additional enumeration value in RedudancyType to show a "manual vs automatic" mode. That property is currently read-only but it could be changed to read-write. I want to look at those values to see if we should add a value for "Group" to show a difference between a set/group of devices vs a set that is not redundant due to the current configuration.
Take a look at the RedundancyGroup definition to see what else you think it may need to accomplish this...
Jeff
|
|
