Since last time, we released Meridian 2021, plus worked on the DNS requisition handler, documentation, Newts, Nephron and Catheter, smoke tests, the Minion, PRIS, flows, notifications, and Helm.
Github Project Updates
Internals, APIs, and Documentation
- Christian updated the DNS requisition URL handler to be location-aware.
- Marcel did some more work on BSF detector documentation.
- Chandra worked on bumping our guava dependency to match updated Newts.
- Chandra and I worked on cleaning up some flapping tests.
- Pierre worked on some updates to the Minion confd schema.
- Bonnie did a bunch of doc updates to match newer style guides.
- Christian updated PRIS to support setting metadata.
- I did a bunch of small updates to Nephron and Catheter to clean up builds and release process.
- Stefan fixed some NPE issues in missing aggregations for Elasticsearch flow queries.
- Chandra worked on fixing notification behavior during a scheduled outage.
- Jane worked on exposing the OpenNMS healthcheck on Minion through ReST.
Web, ReST, UI, and Helm
- I made more preparations for the new Helm release.
- Mark worked on some updated flow dashboards for Helm.
Thanks to the following contributors for committing changes since last OOH:
- Benjamin Reed
- Bonnie Robinson
- Chandra Gorantla
- Christian Pape
- Dustin Frisch
- Jane Hou
- Marcel Fuhrmann
- Mark Mahacek
- Pierre Bouffard
- Ronny Trommer
- Sean Torres
- Stefan Wachter
May 2021 Releases - Horizon 27.2.0, Meridians 2021.1.0, 2020.1.8, 2019.1.19, and 2018.1.28
In May, we released updates to all OpenNMS Horizon and Meridian versions under active support, and released the first iteration of Meridian 2021.
Horizon 27.2.0 is a release primarily targeting bug fixes, plus it includes our new branding refresh.
The codename for 27.2.0 is Magrathea.
For a high-level overview of what has changed in Horizon 27, see What’s New in OpenNMS Horizon 27.
For a complete list of changes in 27.2.0, see the detailed release notes.
Meridian Point Releases
Meridian 2018.1.28 was a tiny release, containing only an update to Apache Commons IO.
Meridian 2019.1.19 adds a backport of a number of browser security issues fixed the previous month in newer releases, plus a few other bug fixes.
Meridian 2020.1.8 contains all of those changes, plus a few other small bug fixes.
For a list of changes, see the release notes:
May also saw the release of Meridian 2021.1.0, the first in the 2021 series.
It is based on Horizon 27, which has proven to be one of our most solid series in quite a while. The most notable changes since Meridian 2020 (based on Horizon 26) are the removal of the legacy Remote Poller and the introduction of Application Perspective Monitoring, performing a similar set of functions using the Minion. Additionally, there are tons of bug fixes and other smaller feature improvements.
For an overview of what's changed since Meridian 2020, see the What's New section of the Meridian 2021 documentation.
Sharp readers will notice this is on our new docs.opennms.com site. We are in the process of moving projects from publishing to docs.opennms.org to the new Antora-based unified docs site.
The next OpenNMS release day is June 1st, 2021.
Barring complications, we expect the first Horizon 28 release.
Next Horizon: 28 (Q2 2021)
The next major Horizon release will be Horizon 28.
It will be the first OpenNMS release requiring JDK 11.
It will also contain a number of other improvements, plus a new feature for flows: DSCP QoS/ToS aggregation for nodes, plus a bunch of plumbing work to improve flow aggregation in general.
Next Meridian: 2022 (Q? 2022)
With Meridian 2021 out, we do not yet have a specific timeline for Meridian 2022.
Expect it to include, at the very least, the JDK11 requirement and flow aggregation improvements of Horizon 28.
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