| commit | 9f14591205aa47cf3e99c44cc8a0469cb87ed8da | [log] [tgz] |
|---|---|---|
| author | Wludzik, Jozef <jozef.wludzik@intel.com> | Thu Feb 11 08:54:10 2021 +0100 |
| committer | Wludzik, Jozef <jozef.wludzik@intel.com> | Thu Feb 11 09:23:01 2021 +0100 |
| tree | c5847d9b75cb36ad8e5f1030f051e7d5f1a84762 | |
| parent | 405c1e4bf8b993cb3800adead546e91b030ecb9b [diff] |
Match DBus Trigger with phosphor-dbus-interfaces Matched Trigger DBus interface to the one defined in phosphor-dbus-interfaces repository. Changed enum (int) type to string to reflect enum type defined in Trigger.yaml. Fixed style in boost_build_1.74.0.sh script. Tested: - Passed unit tests - Verified manually Trigger DBus object in witherspoon image on QEMU Change-Id: I87175fc285afd182d1383da5879f89233b9de6a0 Signed-off-by: Wludzik, Jozef <jozef.wludzik@intel.com>
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].