| commit | dffc8a8c49797822d60c52550943257aea3ee2a4 | [log] [tgz] |
|---|---|---|
| author | Janet Adkins <janeta@us.ibm.com> | Wed Jul 30 16:59:21 2025 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Sep 08 19:19:55 2025 +0000 |
| tree | 3ab0c58161919dcb90ae49517d97bac1096ff843 | |
| parent | 6cfabdfe936b3bbcac15eec2bb060fafb9c8ba41 [diff] |
State: Add min and max to Redundancy interface Add RedundancyMinimum and RedundancyMaximum properties to the Redundancy interface to specify how many BMC objects can be part of the redundant group. These properties can be utilized by bmcweb to support the Redundancy property of the Manager Redfish schema.[1] The Redfish definition for Redundancy requires minimum to be reported.[2] [1] http://redfish.dmtf.org/schemas/v1/Manager.v1_22_0.json#/definitions/Manager [2] http://redfish.dmtf.org/schemas/v1/Redundancy.v1_5_0.json#/definitions/Redundancy Change-Id: I02db0fb7259b2922711fb56cdb1455185d4a609a Signed-off-by: Janet Adkins <janeta@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