| commit | 55640771fddee3c1145e60dc6eabcf91552d71e8 | [log] [tgz] |
|---|---|---|
| author | Matt Spinler <spinler@us.ibm.com> | Thu Apr 11 14:09:19 2024 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Mar 03 15:57:33 2025 +0000 |
| tree | 97f9241c182a7298dc0bcb5de152e03faecc7252 | |
| parent | 8a248c727a1ecadef4916e5acc5a3858d71c9f24 [diff] |
State: Add BMC redundancy interface Define an interface in support of redundant BMC functionality as mentioned in the design doc https://gerrit.openbmc.org/c/openbmc/docs/+/70233. To start with, it defines the Role and RedundancyEnabled properties. With this usage one BMC is considered the active BMC, and the other is the passive. There will be a new application running on each BMC that hosts this interface. This implementation is not related to the one that uses the xyz.openbmc_project.State.BMCRedundancy interface, of which there doesn't appear to be any upstream uses of. Change-Id: I6415175bbee03f6c07b14e1db1ee0082bd1724ed 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