hardware: alarms report the crossed threshold value

The exceeded threshold value for sensors is now propagated to sysrepo.

Our alarm daemon does not implement history yet so we talked about
how the alarm message should be updated during the lifecycle of the
alarm. We thought that clearing the alarm should not change the
alarm-text so we know what was wrong and what was the last value leading
to raising the alarm. However, we decided not to go with that and rather
implement the alarm history (status-changes in RFC 8632 [1]). Therefore,
the alarm-text reflects the current state of the alarm for now.

[1] https://datatracker.ietf.org/doc/rfc8632/

Change-Id: If62c44a54981bb620931bf4b268c3cefb50e8ee4
5 files changed
tree: 6ca879b78cf4d13b2dbcfa902d4f6fdea8d75a53
  1. .clang-format
  2. .gitmodules
  3. .zuul.yaml
  4. CMakeLists.txt
  5. Doxyfile.in
  6. LICENSE
  7. LICENSE.md
  8. README.md
  9. ci/
  10. cmake/
  11. docs/
  12. src/
  13. tests/
  14. yang/
README.md

YANG System management for embedded devices running Linux

Together with sysrepo, this software provides "general system management" of embedded devices. The target platform is anything that runs Linux with systemd. This runs in production on CzechLight SDN DWDM devices.

Health tracking

This component tracks the overal health state of the system, including various sensors, or the state of systemd units. As an operator-friendly LED at the front panel of the appliance shows the aggregated health state.

System management

Firmware can be updated via RAUC, and various aspects of the system's configuration can be adjusted. This includes a firewall, basic network settings, and authentication management.

Supported YANG models

For a full list, consult the yang/ directory in this repository.

Installation

For building, one needs:

The build process uses CMake. A quick-and-dirty build with no fancy options can be as simple as mkdir build && cd build && cmake .. && make && make install.