| commit | 458a37d19dcba48c6ff18ae4716faa7d39337300 | [log] [tgz] |
|---|---|---|
| author | Szymon Dompke <szymon.dompke@intel.com> | Fri Aug 05 10:16:39 2022 +0200 |
| committer | Szymon Dompke <szymon.dompke@intel.com> | Fri Aug 12 11:35:09 2022 +0000 |
| tree | 0cf57e965140609f8d7048bea1a6c47b2516cd2b | |
| parent | 935a70ab8900dee7e70d8723fc670272d63d6d0c [diff] |
Parameterize .service file in meson Depending on environment, TelemetryService may require some services to be present in the system, or specific order of starting them. This may be especially needed for some additional sensors providers, or persistency sync services. This change is parametrizing following .service file options: - After= - Before= - Requires= - Wants= They can be passed as array option to meson, like this: -Dservice-[option]="[....]" Example: -Dservice-wants="['some.service', 'other.service']" Testing done: - .service file is configured properly when new 4 options are passed. - .service file remains unchanged if none of new options are passed. Change-Id: I0982263c8981355db15527163460cc75ae197044 Signed-off-by: Szymon Dompke <szymon.dompke@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].