commit | 0e7ae5dbf1c07c19f11166acc812907e4ccd01ec | [log] [tgz] |
---|---|---|
author | Ed Tanous <edtanous@google.com> | Tue Feb 23 14:06:49 2021 -0800 |
committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Fri Mar 05 08:45:52 2021 +0000 |
tree | 534f55683c16a1580515af1611b2aea9ad482af5 | |
parent | 753e4b3c843dd5d1068949c4106a6389f0e0ffbc [diff] |
async changes to support 40749 https://gerrit.openbmc-project.xyz/c/openbmc/sdbusplus/+/40749 Is currently proposing changing these APIs to use C++ asio style callbacks instead of the javascript callbacks. This was the only usage of these callbacks that I found, so this patchset is to move to the new type. Requires 40749 to be merged before this will build. Signed-off-by: Ed Tanous <edtanous@google.com> Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com> Change-Id: I1e950c096e36d2150a94c459e794bbac7303100d
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]
.