| commit | 669f3182ab0001f6812875b884ecfbfbd1c8ae2c | [log] [tgz] |
|---|---|---|
| author | Matt Spinler <spinler@us.ibm.com> | Mon Jun 02 10:37:39 2025 -0500 |
| committer | Matt Spinler <spinler@us.ibm.com> | Mon Nov 10 19:47:32 2025 +0000 |
| tree | 7de5184547230104d7c8c8a9017dba15278f0bff | |
| parent | 0814d6a59fbe7c7a3f7c3e4657441be3bcaa7d20 [diff] |
State: Redundancy interface updates Make the following changes: 1. Change 'FailoversPaused' to 'FailoversAllowed'. Changed to 'Allowed' as it can actually be a long lasting condition, such as if only 1 BMC is present. 2. Add 'FailoverImminent'. This will be available on the BMC being failed away from so it can do anything it needs to. At the very least it can do a journal sync before it is reset, assuming it is alive. 3. Add 'FailoverInProgress'. This indicates that a failover is in progress. 4. Add an entry to the 'segments' YAML for the sibling BMC, as this interface will be used on that object path as well. Change-Id: I56602323097b4c8ab90c076928c5e05db75b99c4 Signed-off-by: Matt Spinler <spinler@us.ibm.com>
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.
This project can be built with meson. The typical meson workflow is: meson builddir && ninja -C builddir.
The meson files used to handle the YAML files are automatically generated and found under the gen subdirectory. When adding or removing YAML files, this must be regenerated. This can be done with the helper script found in the gen subdirectory: cd gen && ./regenerate-meson.
Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true-Ddata_org_open_power=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir