In the last week we fixed a bunch of bugs including ticketing and thresholding fixes, continued to work on QoS/ToS and flow improvements, ReST additions, and documentation.
Github Project Updates
Internals, APIs, and Documentation
- Chandra worked on fixing the handling of metadata in thresholding
- I did a bit more work on improving our smoke test pipeline
- Ronny and Bonnie did more work finalizing the new Antora docs
- Stefan did more work on flow performance and processing
- Chandra worked on fixing some alarm ticketing integration bugs
- Chandra fixed the default config for the Minion listener
- Stefan continued to work on QoS/ToS in flows
- Marcel added documentation for a number of detectors
- Craig continued to work on modernizing the Selenium monitor
Web, ReST, UI, and Helm
- Jane wrapped up her enhancements to exposing Enlinkd data through ReST
- Jane did more work on generating ReST API docs
- Christian did some more work on cleaning up web UI forms
Thanks to the following contributors for committing changes since last OOH:
- Benjamin Reed
- Bonnie Robinson
- Chandra Gorantla
- Christian Pape
- Craig Gallen
- Jane Hou
- Marcel Fuhrmann
- Ronny Trommer
- Stefan Wachter
The next OpenNMS release day is April 6th, 2021.
Currently we expect new bug fix releases for Horizon 27 and Meridians 2019 and 2020.
Next Horizon: 28 (Q? 2021)
The next major Horizon release will be Horizon 28.
Horizon 28 will still be coming down the pipeline soon.
Currently, we hope for it to contain the move to building with JDK 11 (and, consequently, a requirement to only run on JDK 11 or higher), QoS flow aggergation, and some other improvements in the pipeline.
Next Meridian: 2021 (Q2 2021)
Meridian 2021 is on track for a release in 2nd quarter of 2021. It is expected to be based on the Horizon 27.1 codebase, which means it will contain all of the bug fixes and new features introduced in Horizon 26 and 27.
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
- NMS-12941: Raw Link Details via REST API
- NMS-13072: Add out of band management capabilities
- NMS-13120: Wrong UEI is picked when threshold alarms are generated
- NMS-13121: Document the Event Translator
- NMS-13149: Regular Expression field textbox greyed out for other Events except 'REGEX_FIELD' under Event notifications
- NMS-13201: CVE-2020-27223: Jetty DoS vulnerability