commit | 5f7ca1a466099638ce906eff5c461fefe1d177f7 | [log] [tgz] |
---|---|---|
author | Szymon Dompke <szymon.dompke@intel.com> | Thu Oct 13 17:58:48 2022 +0200 |
committer | Szymon Dompke <szymon.dompke@intel.com> | Thu Oct 13 18:45:56 2022 +0200 |
tree | ad9d13e383b2d121a555ca29dfed17008806cd90 | |
parent | 7e114c045e44dcf916db6399bd684283fa84785d [diff] |
Remove scripts directory Scripts directory contains 2 files which were failing CI. They are not needed and can be removed. Testing done: - CI is passing. Signed-off-by: Szymon Dompke <szymon.dompke@intel.com> Change-Id: Ib5f8168c7c3a2d49a482ef10658de292764616f7
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]
.