You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
health.hpp should be modified to look for OperationalStatus for the Health and HealthRollUp.
Ideally, all resources would then use health.hpp.
It might make sense to rename health.hpp to status.hpp and have it do the health, healthrollup, and state. #2795 (comment)
@ChicagoDuan Isn't health.cpp already looking at OperationalStatus to populate Health ?.
or , may be processor / DIMMs / Fans, individually have hooks on OperationalStatus and then use Health also ?. Because, I can today set health of Fan using OperationalStatus
@ChicagoDuan Isn't health.cpp already looking at OperationalStatus to populate Health ?.
or , may be processor / DIMMs / Fans, individually have hooks on OperationalStatus and then use Health also ?. Because, I can today set health of Fan using OperationalStatus
health.hpp should be modified to look for OperationalStatus for the Health and HealthRollUp.
Ideally, all resources would then use health.hpp.
It might make sense to rename health.hpp to status.hpp and have it do the health, healthrollup, and state.
#2795 (comment)
Step 1 :
We should push a paragraph to : https://github.com/openbmc/docs/blob/919a7b6816a5f16aa72d298e81e0756d95d5031e/designs/redfish-health-rolllup.md#proposed-design
E.g.
Step 2:
Modify the health.hpp to look for OperationalStatus for the Health and HealthRollUp.
The text was updated successfully, but these errors were encountered: