| commit | 12a4dec1033ce6974365f25bfeafb978c4aa109a | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Wed Jun 26 13:23:43 2024 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Jun 28 14:52:01 2024 +0000 |
| tree | 613ef8ee189abbd7d84d20738d411d18ebefd0a4 | |
| parent | edb3eead5a674aecaf031369d1b3b35915979ca6 [diff] |
inventory: define a decorator for managed hosts In order to support multi-host Redfish, we need a mechanism for bmcweb to find the associated objects for managing the host, such as the phosphor-state-management objects for power control. Most of the existing designs use a numerical index rather than an association. Define a decorator that can be added to inventory items, so that bmcweb has a clear mapping to the host management objects without requiring them to all add new associations. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Iee69e0a95c2e04089c5ac512d9c8825c62737179
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