| commit | 405c1e4bf8b993cb3800adead546e91b030ecb9b | [log] [tgz] |
|---|---|---|
| author | Wludzik, Jozef <jozef.wludzik@intel.com> | Thu Jan 28 16:24:27 2021 +0100 |
| committer | Jozef Wludzik <jozef.wludzik@intel.com> | Wed Feb 10 12:11:45 2021 +0000 |
| tree | c92b95176863344d8230c4bac44e4175c543f547 | |
| parent | e8fc57514575f07565035db07cb522fe21988224 [diff] |
Add simple Redfish tests Added Redfish tests to validate connection between Redfish Telemetry that is implemented in bmcweb and Telemetry service. Change-Id: Iacc63aeb7f2852d5acac5d5615f98b402f7c4417 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].