| commit | f7f4a2b95f7321f17802d577048f1b97b68d9162 | [log] [tgz] |
|---|---|---|
| author | Matt Spinler <spinler@us.ibm.com> | Thu Feb 20 14:24:00 2025 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Oct 10 00:12:49 2025 +0000 |
| tree | d3f345fbac6835336530e613508107e11fd29d8c | |
| parent | 2765ab3079327f32b1fc69d0eb9e6996f379ef2c [diff] |
Control: Add Failover interface Create an interface to start a failover, where a failover is the mechanism where one entity takes over the operation of another. The first use will be to failover to another BMC, using the design at https://gerrit.openbmc.org/c/openbmc/docs/+/70233, though the intent is the interface can also be used for other sorts of failovers. Change-Id: I32789f6b8f01d1baed95d387e6815a797d5b45b8 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