OpenNMS On the Horizon – JDK11, OpenBMP, ToS/QoS, Flows, Documentation
In the last week we continued our work on JDK11 migration, moving OpenBMP functionality into OpenNMS, ToS/QoS flow aggregation, Antora documentation, a new configuration API/implementation, and plenty of bug fixes.
Github Project Updates
Internals, APIs, and Documentation
Jesse continued to work on JDK11 builds.
Dustin and Stefan did some more fixes to hostname resolution in flow aggregation.
Chandra worked on some a fix for some Karaf poller commands not working when Telemetryd is disabled.
Stefan continued his work on ToS/QoS flow aggregation.
Christian fixed a bug where a dbonly provisiond scan would not preserve node metadata.
Patrick and Jerry did more work on a prototype configuration system using Vacuumd.
Chandra continued his work on the OpenBMP core migration.
Matt made some fixes to the flow parser schema.
Bonnie did some wrapup work on the Antora documentation migration.
Christian made some improvements to his fix for running the WMI collector on Minion.
Ronny filled in some of the missing descriptions in the new Minion config schema definition.
Jesse worked on bumping our embedded Karaf to 4.2.10.
Web, ReST, UI, and Helm
I worked on more fixes to time zone handling in the schedule report UI.
Thanks to the following contributors for committing changes since last OOH:
The next OpenNMS release day is February 2nd, 2021.
Currently we expect a Horizon 27 point release.
Next Horizon: 28 (March 2021)
The next major Horizon release will be Horizon 28.
It is currently expected to be released during the March release cycle.
It will primarily contain enhancements to flow processing to handle ToS/QoS (DSCP) aggregation, as well as a refactor of our BGP Monitoring Protocol support to bring it in-core, rather than relying on an external OpenBMP instance.
Next Meridian: 2021 (Q2 2021)
With the recent release of Meridian 2020, plans are still tentative.
However, the current plan is that Meridian 2021 will be based on Horizon 28.
We'll know more once development plans start to firm up.
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.