| commit | 2d5404f1381861f1d85ada402ab155e2bddc4abe | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Thu Dec 08 06:18:23 2022 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Fri Dec 09 07:43:54 2022 -0600 |
| tree | 5793b83e63a7a2bf2b3d8c48a4ef43605196aa06 | |
| parent | d2ad09fb0c47a050ae864e1efd65054c6981c78d [diff] |
black: re-format black and isort are enabled in the openbmc-build-scripts on Python files to have a consistent formatting. Re-run the formatter on the whole repository. Change-Id: I66c89f20acb2c266c15ad9987b5c2b7548f976bd Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
This component implements middleware for sensors and metrics aggregation.
This application is implementation of Telemetry proposed in OpenBMC design docs [1].
It's responsible for:
[2],[3] updates.[4]There are two way to build telemetry service:
To build it using bitbake follow the guide from OpenBMC docs[5]. To build it using meson follow the quick guide to install meson[6] and then run below commands
meson build cd build ninja
After successful build you should be able to run telemetry binary or start unit tests
./tests/telemetry-ut ./telemetry
In case if system is missing boost dependency, it is possible to build it locally and set BOOST_ROOT environment variable to location of built files for meson. After this change meson should be able to detect boost dependency. See [7] for more details.
More information can be found in OpenBMC docs repository [8].