It's time once again for OpenNMS On the Horizon.
Since last time, we worked on documentation (provisioning, capabilities, device config backup UI, ticketer), a number of device config backup changes (roles, filename and suffix handling, scheduling, authentication, REST), Netflow 9 parsing, Keycloak, time-series tag matching, ID types, HTTPS smoke tests, OIA, hardware inventory, notification editing, surveillance dashboards, Helm filtering, and topology in the new UI.
Github Project Updates
Internals, APIs, and Documentation
- Bonnie did more work on provisioning documentation
- Mark made some improvements to the documentation on capabilities in the deployment guide
- Christian added a role for device config backup
- I worked on cleaning up our Spring dependency-handling in Karaf
- Bonnie made some updates to the device config backup documentation
- Christian added parsing of
egressPhysicalInterface to the Netflow 9 parser
- Christian made some changes to the way unique filenames and suffixes are handled in DCB
- Mark did some cleanups to the ticketer documentation
- Bonnie did more work on documenting the DCB UI
- Arthur worked on Keycloak support in Stream
- Freddy did more work on doing datacollection from events
- Dustin fixed some issues with DCB scheduling
- Chandra and Dustin worked on Secure Credentials Vault support for DCB authentication
- Patrick did some more fixes to tag matching in the time-series API
- Yang Li worked on converting IDs to be
Longs in Stream
- Alexander worked on fixes for issue with smoke tests running in HTTPS mode
- Freddy worked on updating the handling of thresholding definitions in OIA
Web, ReST, UI, and Helm
- Pushkar worked on fixing a bug with POSTing bad data to the hardware inventory REST API
- Christian cleaned up some input-handling in the notification path editor
- Christian fixed an issue with availability calculation in the surveillance dashboard
- Alberto worked on some filtering improvements in Helm
- Scott fixed an issue with device counts in the DCB REST interface
- Mike did more work on topology in the new UI
- Chinh Le fixed an issue with handling of spaces in foreign source names in the new UI
Thanks to the following contributors for committing changes since last OOH:
- Freddy Chu
- Chinh Le
- Alexander Chadfield
- Marcel Fuhrmann
- Patrick Schweizer
- Chandra Gorantla
- Bonnie Robinson
- Mike Rose
- Dustin Frisch
- Benjamin Reed
- Mark Mahacek
- Alberto Ramos
- Christian Pape
- Scott Theleman
- Pushkar Suthar
Releases and Roadmap
April 2022 Releases
In April, we released updates to all OpenNMS Meridian versions under active support, as well as Horizon 29.
Meridian Stable Updates
Meridians 2019.1.33 and 2020.1.22 contained a few targeted security fixes and enhancements.
On top of those changes, Meridian 2021.1.14 includes additional documentation updates and a few more small bug fixes.
Meridian 2022.1.2 contains more documentation updates, plus a few fixes for running as non-root, XML processing dependency cleanups, and a few other minor improvements.
For a list of changes, see the release notes:
Release 29.0.9 contains all of the fixes included in Meridian 2022.1.2.
For a high-level overview of what has changed in Horizon 29, see What’s New in OpenNMS Horizon 29.
For a complete list of changes, see the changelog.
The codename for Horizon 29.0.9 is Kiwi.
Upcoming May Releases
OpenNMS is on a monthly release schedule, with releases happening on the second Wednesday of the month.
The next OpenNMS release day is May 11th, 2022.
We currently expect the first release of Horizon 30, plus Meridians 2019 through 2022.
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
- initial work moving configuration from XML files to the database -- the first config file implemented on top of the new system will be
- support for running OIA plugins on Minion and Sentinel
- support for backing up router configuration files
Next Meridian: 2023 (Q1 2023)
Meridian 2023 is early in its development cycle, but you can expect it to contain, at the very least, the work that's going into Horizon 30.
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.
Resolved Issues Since Last OOH
- HELM-311: Add a transform to swap Ingress and Egress
- NMS-13443: Jira Cloud Support
- NMS-13802: DCB - Document how to use the polling packages and the requisition to configure backups
- NMS-13992: Docker usage documentation is out of date
- NMS-14048: Node availability > 100% in the dashboard
- NMS-14111: Destination Path Edit Button fails when Name field is empty
- NMS-14130: Support for netflowv9 fields ingressPhysicalInterface & egressPhysicalInterface
- NMS-14146: DCB: Backup is triggered after provisioning
- NMS-14162: Update docs for binding ports <1024
- NMS-14165: DCB: Display Device Count for queries
- NMS-14166: Merge feature/device-config back to develop
- NMS-14168: DCB: Backup is always triggered on minion
- NMS-14172: Cleanup Ticketer docs formatting