It's time once again for OpenNMS On the Horizon.
Since last time, we worked on JDK 17 support, device config backup, config management, detectors in OIA, Karaf 4.3.6, Alarmd in Sentinel, TIMETETRA LLDP linkd, documentation improvements, CircleCI updates, the Zabbix plugin, Grafana reports, chart UI, AngularJS fixes, core and Helm JS build updates, node rescan REST support, and Sentinel smoke test improvements.
Github Project Updates
Internals, APIs, and Documentation
- I got OpenNMS running on JDK 17. There's still a lot of work to fix test infrastructure before this is actually ready, though.
- Stefan worked on making a utility for doing basic scripting of remote SSH interaction for device config backup.
- Puskhar did more work on migrating SNMP configs to the config management API.
- Stefan did more work on TFTP support for device config backup.
- Yang Li continued his work to support writing detectors in OIA.
- Yang Li finished upgrading our embedded Karaf to 4.3.6.
- Patrick updated the CM migrator to handle multiple configs of the same type.
- Freddy did more work on config management test infrastructure.
- Arthur worked on running alarmd and the event REST service in Sentinel.
- Antonio fixed an issue with persisting links for TIMETETRA LLDP devices.
- I spent more time trying to clean up flapping tests.
- Chandra worked on device config backup tests.
- Bonnie migrated some info from Discourse to the official docs.
- I fixed up some CircleCI changes related to splitting the builds.
- Julian worked on publishing Minion Docker images to Azure.
- Brent worked on getting Sonar code coverage pushing again.
- Jesse did some dependency updates to the Zabbix plugin.
- Bonnie worked on improving the main
README.mdfile. - Marcel did more work on cleaning up some doc rearranging.
- Chandra worked on poller integration for device config backups.
Web, ReST, UI, and Helm
- I fixed a bug in the grafana report editor UI.
- Stefan started work on a REST endpoint for device config backup.
- Mike continued to work on charts and graph data display in the new Vue UI.
- I fixed some issues with AngularJS template handling.
- I did a bunch of dependency and build cleanup in the core webapp and helm build systems.
- Christian did more work on graph templates for flow thresholds.
- Stefan merged his updates to Helm to use native JS promises.
- Alex did more work on being able to trigger a rescan of a node through REST.
- Alberto added documentation for the healthcheck REST API.
- Alberto worked on making the smoke tests use the healthcheck REST API rather than SSH to check test containers.
Contributors
Thanks to the following contributors for committing changes since last OOH:
- Chandra Gorantla
- Marcel Fuhrmann
- Bonnie Robinson
- Benjamin Reed
- Mike Rose
- Jesse White
- Julian Buliga
- Stefan Wachter
- Brent Borovan
- Alberto Ramos
- Freddy Chu
- Dmitri Herdt
- Alex May
- Pushkar Suthar
- Arthur Naseef
- Antonio Russo
- Christian Pape
- Patrick Schweizer
- Yang Li
- Dustin Frisch
Release Roadmap
Upcoming February Releases
OpenNMS is on a monthly release schedule, with releases happening on the second Wednesday of the month.
The next OpenNMS release day is February 9th, 2022.
We currently expect updates to Horizon 29 and all supported Meridian releases.
Next Horizon: 30 (Q2 2022)
The next major Horizon release will be Horizon 30.
Horizon 30 is currently expected to have the following features:
- the start of a new Vue-based UI using the Feather Design System
- thresholding support for Flow data
- support for running OIA plugins on Minion and Sentinel
- support for backing up router configuration files
Next Meridian: 2022 (Q1 2022)
The current expectation is that we will release Meridian 2022 in Q1 of next year. It will be based on Horizon 29 plus any bug fixes that happen between November and the Meridian release.
Disclaimer
Note that this is just based on current plans; dates, features, and releases can change or slip depending on how development goes.
The statements contained herein may contain certain forward-looking statements relating to The OpenNMS Group that are based on the beliefs of the Group’s management as well as assumptions made by and information currently available to the Group’s management. These forward-looking statements are, by their nature, subject to significant risks and uncertainties.
...We apologize for the excessive disclaimers. Those responsible have been sacked.
Mynd you, møøse bites Kan be pretti nasti...
We apologise again for the fault in the disclaimers. Those responsible for sacking the people who have just been sacked have been sacked.
Until Next Time…
If there’s anything you’d like me to talk about in a future OOH, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.
- Ben
Resolved Issues Since Last OOH
- HELM-301: Use official Grafana typings
- NMS-13386: Add docs to Health-Check Rest API
- NMS-13645: Smoke tests should use HealthCheck Rest instead of connecting to SSH
- NMS-13658: Upgrade Karaf to v4.3.6
- NMS-13710: Flow Thresholds: Graph Templates
- NMS-13745: Allow detectors exposed via OIA to be scheduled with provisiond
- NMS-13758: Split Database Reports docs into multiple pages
- NMS-13759: Split Asset Topology Provider docs into multiple pages
- NMS-13796: Implement TFTP Server to fetch config from network devices
- NMS-13848: Outdated javascript library
- NMS-13899: ssh scripting support for triggering TFTP upload of device configurations
- NMS-13909: Integrate SonarCloud with CircleCI builds for develop branch
- NMS-13910: org.opennms.core.commands never got added to Karaf build
- NMS-13913: Sanitize application names in resources
- NMS-13915: Flow Thresholds: Improve logging and debug
- NMS-13917: grafana endpoint can be used to port-scan internal resources
Top comments (0)