docs/designs/psu-monitoring.md

1 # Power Supply Monitoring Application
12 supply application for enterprise class systems. Some enterprise class systems
14 supply types and numbers. An application capable of communicating with the
23 that contains a power supply monitor application and a power sequencer monitor
24 application. The current power supply application is lacking things desired for
27 The intent of this new application design is to enhance the OpenBMC project with
28 a single power supply application that can communicate with one or more
30 in the existing application that has multiple instances talking to a single
38 1. The power supply application must detect, isolate, and report individual
40 2. The power supply application must determine power supply presence,
42 3. The power supply application must report power supply failures to IPMI and
44 4. The power supply application must report power supply present/missing changes
47    moved from the `phosphor-dbus-monitor` to this application, depending on if
50 5. The power supply application must ensure proper power supply configuration
52 6. The power supply application must collect and report power supply VPD (unless
53    that VPD is collected and reported via another application reading an EEPROM
55 7. The power supply application must allow power supply hot-plug and concurrent
57 8. The power supply application should create and update average and maximum
59 9. The power supply application must be able to detect how many power supplies
63 10. The application must be able to recognize if the power supplies present
65     the application updating properties for a Minimum Ship Level ([MSL][3])
67 11. The application must create error logs for invalid configurations, or for
70 12. The application would periodically communicate with the power supplies via
83 The proposal is to create a single new power supply application in the OpenBMC
84 [phosphor-power][6] repository. The application would be written in C++17.
86 Upon startup, the power supply application would be passed a parameter
93 The power supply application would then detect which system type it is running
95 information, what type each supply is, etc. The application would then try to
97 would be considered invalid. The application should continue to check what if
101 to the system. At that point the application will start to and continue to
106 The proposed power supply application would not control any fans internal to the
107 power supply, that function would be left to other userspace application(s).
121 The application is expected to have some impact on the PLDM API, due to the
129 The application is expected to have a similar or lesser performance impact than
130 the one application per power supply.
137 - Application detects and logs faults for power supply faults including input