Since last time, we worked on Selenium monitor, VMware, BSF and other documentation, Nephron, Karaf, Minion, UI layout, notifications, opennms.js, and Helm.
Github Project Updates
Internals, APIs, and Documentation
- Ronny did some work on creating test docker images for the Selenium monitor rework
- Christian made some fixes for timeout handling in the VMware code
- Marcel did some work on BSF detector documentation
- Chandra, Craig, and Jesse continued the work on making the Selenium monitor Minion-compatible
- Stefan fixed some dependency issues with Nephron and Catheter
- Stefan worked on a race condition in container startup
- Chandra fixed the default Minion flow config
Web, ReST, UI, and Helm
- Jane worked on modernizing some of the admin help page links
- Jane worked on some new layout stuff for the login page
- Christian worked on an update to support setting parameters in the notification config UI
- I converted Helm to TypeScript and the new Grafana toolkit to solve a number of initialization and related bugs
- I added some missing types to the opennms.js convenience
Thanks to the following contributors for committing changes since last OOH:
- Benjamin Reed
- Chandra Gorantla
- Christian Pape
- Craig Gallen
- Dustin Frisch
- Jane Hou
- Jesse White
- Marcel Fuhrmann
- Ronny Trommer
- Stefan Wachter
The next OpenNMS release day is May 11th, 2021.
Currently we expect a new Horizon 27 release, as well as Meridians 2019, 2020, and 2021.
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 the 2nd quarter of 2021. It is expected to be based on the Horizon 27 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-9966: nodelabel-host-name setting on HttpMonitor not applying
- NMS-13090: Build prototype of configuration system for vacuumd config
- NMS-13095: Replace ConfigTesterTest with something that uses the configservice
- NMS-13096: Yang Vacuumd Configuration and Generation
- NMS-13110: Shipped minion flow listener config does not create a working listener
- NMS-13122: Intergate support for OSGI into configuration system
- NMS-13225: Update Help page with doc links in the Web UI