| commit | 495981805244269650bee13d1ee8f13543b2bc5a | [log] [tgz] |
|---|---|---|
| author | George Liu <liuxiwei@inspur.com> | Tue Mar 02 17:06:57 2021 +0800 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Apr 19 12:07:14 2021 +0000 |
| tree | 8ded4bba0ac5863901e748efa336fa51a0528dd9 | |
| parent | 30417976a391ffe8c415840ba507f68fff2e0cc2 [diff] |
Telemetry: Add ReportingUpdate property to Report and ReportManager interfaces - Currently, the Telemetry service only supports `ReportUpdates = Overwrite`. - Right now, there is a requirement: need to support `ReportUpdate = AppendWrapsWhenFull` which allows for more than 1 metric report. Therefore, we need to add the `ReportingUpdate` property to the Report and ReportManager interfaces to obtain the currently supported update types. - Also, add AppendLimit property to Report and ReportManager interfaces. - At the same time, we also need to update the `telemetry` and `bmcweb` repositories. Ref: https://redfish.dmtf.org/schemas/v1/MetricReportDefinition.v1_4_0.json Tested: - Successful build and verified changes in server.hpp and server.cpp. Signed-off-by: George Liu <liuxiwei@inspur.com> Change-Id: Id59f60d64c37900962d6d62421530a3917e8e349
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
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 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