#
7e114c04 |
| 13-Oct-2022 |
Szymon Dompke <szymon.dompke@intel.com> |
Use clang-format-15
Some files required reformating.
Testing done: - Clang-format is passing on CI
Signed-off-by: Szymon Dompke <szymon.dompke@intel.com> Change-Id: I39d53715840818ffabcb3903a5efc9
Use clang-format-15
Some files required reformating.
Testing done: - Clang-format is passing on CI
Signed-off-by: Szymon Dompke <szymon.dompke@intel.com> Change-Id: I39d53715840818ffabcb3903a5efc97639ed48df
show more ...
|
#
fdb06a14 |
| 11-Feb-2022 |
Szymon Dompke <szymon.dompke@intel.com> |
Report: make dbus properties writable
ReadingParametersFutureVersion interface for Reports is enhanced from read-only to read write and supports modification of readingParameteres, which is done by
Report: make dbus properties writable
ReadingParametersFutureVersion interface for Reports is enhanced from read-only to read write and supports modification of readingParameteres, which is done by updating metrics at the first place and re-registering them for sensors updates. Similar ReportActions interface is enhanced to read write. Additionally reportActions policy was modified that reports always contain 'LogToMetricReportsCollection' action. The whole change enables Redfish support for PATCH method added on webserver side.
Tested: - New unit tests were created, ran all new and previous UTs, all passed - Tested under QEMU, interface was checked for RW via dbus cli commands, checked if Reading Parameters of the Report can be read or written, if metrics are properly updated and registration/unregistration for updates works properly, checked if actions of Report can be read or written, if actions are properly updated and related action behavior follows the change accordingly - Tested under QEMU, verified if 'LogToMetricReportsCollection' action is always added when Report is created or when actions of Report are updated by dbus interface - Tested via webserver if it communicates properly with dbus interfaces of Telemetry and read/write operations via Redfish can be successfully executed
Signed-off-by: Lukasz Kazmierczak <lukasz.kazmierczak@intel.com> Change-Id: I7f2fe8eae1631c436cf61a516d5fd0b8358a76bd
show more ...
|
#
60fee077 |
| 13-Jan-2022 |
Krzysztof Grobelny <krzysztof.grobelny@intel.com> |
added property SupportedOperationTypes
- removed OperationType::single - for backward compatibility incomming OperationType::single alted to produce same output functionality - added property Supp
added property SupportedOperationTypes
- removed OperationType::single - for backward compatibility incomming OperationType::single alted to produce same output functionality - added property SupportedOperationTypes to ReportManager interface
Tested: - In cases where OperationType::single is used same MetricValues are produced - New property is visible on dbus
Change-Id: I838581c954abc0d8401e0ed530ce7e9c8013860b Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com>
show more ...
|
#
e2362796 |
| 27-Oct-2020 |
Wludzik, Jozef <jozef.wludzik@intel.com> |
Implement Report persistency
Now Report properties are stored in non-volatile memory. It allows to restore Report after system restart. Persistency of a report is controlled by Persistency property
Implement Report persistency
Now Report properties are stored in non-volatile memory. It allows to restore Report after system restart. Persistency of a report is controlled by Persistency property in Report interface.
Tested: - Passed unit tests - Verified that report is stored in /var/lib/telemetry dir - Verified that report is restored from storage after telemetry service start
Signed-off-by: Wludzik, Jozef <jozef.wludzik@intel.com> Change-Id: Iccfe21603eecffc4e174a4403f699b03de320db9
show more ...
|