commit | ca1e9ea1f91ca98792b698ffd9c61d13697488e6 | [log] [tgz] |
---|---|---|
author | Matt Spinler <spinler@us.ibm.com> | Fri Feb 18 14:03:08 2022 -0600 |
committer | Matt Spinler <spinler@us.ibm.com> | Fri Feb 18 14:20:30 2022 -0600 |
tree | 0e9020fd92d99a96402b472d0f7018b2671407b7 | |
parent | 10fc6e8746d00faa638b29ba547d82d2f8057ddf [diff] |
psu-ng: Handle health rollup based on availability When a PSU is set to not available, create an association between the power supply and its chassis as a way to 'roll up' the health status to that chassis. It looks like: <chassis>/critical endpoints: <power supply> <power supply>/health_rollup endpoints: <chassis> There is Redfish code that look at the endpoints in that chassis association object to determine if the chassis health is OK or not. Note that some systems, such as IBM's, have other code that will fill in that association when it is called out in an event log, which is why this code doesn't have to do it for every single fault. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I262dd738ebadb72aa207011941066fc282bfe4df
This repository contains applications for configuring and monitoring devices that deliver power to the system.
To build all applications in this repository:
meson build ninja -C build
To clean the repository and remove all build output:
rm -rf build
You can specify meson options to customize the build process. For example, you can specify:
Several applications in this repository require a PSU JSON config to run. The JSON config file provides information for:
There is an example psu.json to describe the necessary configurations.
inventoryPMBusAccessType
defines the pmbus access type, which tells the service which sysfs type to use to read the attributes. The possible values are:/sys/bus/i2c/devices/3-0069/
/sys/bus/i2c/devices/3-0069/hwmon/hwmonX/
/sys/kernel/debug/pmbus/hwmonX/
/sys/kernel/debug/pmbus/hwmonX/cffps1/
fruConfigs
defines the mapping between the attribute file and the FRU inventory interface and property. The configuration example below indicates that the service will read part_number
attribute file from a directory specified by the above pmbus access type, and assign to PartNumber
property in xyz.openbmc_project.Inventory.Decorator.Asset
interface."fruConfigs": [ { "propertyName": "PartNumber", "fileName": "part_number", "interface": "xyz.openbmc_project.Inventory.Decorator.Asset" } ]
psuDevices
defines the kernel device dir for each PSU in inventory. The configuration example below indicates that powersupply0
's device is located in /sys/bus/i2c/devices/3-0069
."psuDevices": { "/xyz/openbmc_project/inventory/system/chassis/motherboard/powersupply0" : "/sys/bus/i2c/devices/3-0069", }