In the last week we did more work on flow aggregation (including ToS and QoS), continued to work on the OpenBMP migration, JDK 11 builds, JEXL cleanups, time zone handling, Minion metrics in Prometheus, and more.
Github Project Updates
Internals, APIs, and Documentation
- Dustin wrapped up his work on clock skew detection in flow processing
- Chandra continued his work on moving OpenBMP to the OpenNMS core
- Chandra updated the
developbranch (future Horizon 28) to enable single-topic Kafka RPC by default
- Jesse worked on integration test updates related to the JDK11 transition
- Bonnie did some more work on the new Antora-based documentation
- Christian and Jesse did some work on cleaning up our JEXL handling
- Stefan continued his work on QoS/ToS support in flow aggregation
- Ronny added support for exporting some Minion metrics to Prometheus
- I fixed an issue with timezone handling in the Grafana report backend
Web, ReST, UI, and Helm
- I did more work on fixing up topology map tests.
- Christian worked on fixing event search to allow events with single quotes in them
Thanks to the following contributors for committing changes since last OOH:
- Benjamin Reed
- Bonnie Robinson
- Chandra Gorantla
- Christian Pape
- Dustin Frisch
- Jesse White
- Matthew Brooks
- Ronny Trommer
- Stefan Wachter
The next OpenNMS release day is February 2nd, 2021.
Currently we expect a point release for Horizon and all active Meridians.
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.