| commit | c0991cee33cdc8bfbd59e63d9b3178260166fe4d | [log] [tgz] |
|---|---|---|
| author | Tomáš Pecka <tomas.pecka@cesnet.cz> | Wed Dec 20 15:46:03 2023 +0100 |
| committer | Tomáš Pecka <tomas.pecka@cesnet.cz> | Thu Jan 11 11:32:34 2024 +0100 |
| tree | dc2b7e93bee972ff588e6c883e26831e0188dfff | |
| parent | bf39bcb976ed09ffe4d1c6fdcf8fd00e48f303d9 [diff] |
hardware: add new sensors to alarm-inventory After previous commits we saw failures on live boxes that nonoperational alarm is not registered in alarm-inventory for some components. And indeed. We fill alarm-inventory right after the Hardware classes are constructed. However, when the pluggable components are not present at that time, then its thresholds would not get passed to IETFHardware. And we read active sensors based on the keys of sensor XPath to Thresholds mapping. The simple solution was to load all the active sensors and their thresholds with every HW state poll. Then, we'd sync the alarm-inventory with the current state of the active sensors. However, this could not work. If the sensor is unplugged, we'd delete all alarm-inventory entries for this sensor but then we can't publish the missing sensor alarm. Therefore, let's do it like in health tracking alarms for systemd services: Publish new alarm-inventory entries but do not delete them. Change-Id: I8a9b85e3b11f3ea4d66a48241d39b808a8b5dffa
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.
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.
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.
For a full list, consult the yang/ directory in this repository.
ietf-access-control-list, RFC 8519 (with deviations)ietf-hardware, RFC 8348ietf-system, RFC 7317 (partial support)ietf-interfaces, RFC 8343 (generating config for systemd-networkd, with extensions)ietf-routing, RFC 8349 (see above)czechlight-systemFor building, one needs:
1.78)pkg-configlibnl-route for talking to the Linux kernellibsystemd and systemd at runtimelibyang-cpp - C++ bindings for libyangsysrepo-cpp - C++ bindings for sysrepospdlog - a logging librarysdbus-c++ - C++ library for D-Busfmt - C++ string formatting librarynlohmann_json - C++ JSON librarydocopt for CLI option parsingnft - the netfilter tooliproute2 - the ip tool for testingThe 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.