In the last week we worked on the OpenBMP migration, documentation, builds, ToS aggregate flow support, moving to JDK 11, and more.
Github Project Updates
Internals, APIs, and Documentation
- Sean did some more work on updating our Kafka components to a newer release
- Chandra continued his work on moving our OpenBMP integration to core code
- I updated our packaging to soft-depend on
haveged for better SSL performance
- Bonnie did more work on the migration of docs to Antora
- Ronny worked on updating our CircleCI build images to a newer JDK (and OS updates)
- Zoë updated the
snmpifdescr column to be arbitrarily-sized
- Stefan did more work on ToS/QoS support
- Ronny updated PRIS to build with JDK 11
Thanks to the following contributors for committing changes since last OOH:
- Benjamin Reed
- Bonnie Robinson
- Chandra Gorantla
- Christian Pape
- Ronny Trommer
- Sean Torres
- Stefan Wachter
- Zoë Knox
January Horizon and Meridian Releases
In January we released point updates for Horizon 27 and Meridians 2019 and 2020.
Horizon 27.0.3 is a minor release with a number of mostly esoteric bug fixes, and a few small enhancements.
The codename for 27.0.3 is Dolphins.
For a complete list of changes in 27.0.3, see the release notes.
Meridians 2019.1.15 and 2020.1.4
Both Meridian releases had just a few small changes, including a new soft dependency on Haveged.
For a list of changes, see the release notes:
The next OpenNMS release day is February 2nd, 2021.
Currently we expect a Horizon 27 point release.
Next Horizon: 28 (Q1 2021)
The next major Horizon release will be Horizon 28.
We're still in the development cycle for it, but at a high level it is expected to contained our finished work moving OpenBMP's functionality into OpenNMS, as well as enhancements to handle ToS/QoS in flows.
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.
Resolved Issues Since Last OOH
- NMS-2013: Added Admin group members to magic-users.properties automatically
- NMS-12801: Notifications Not Auto-Acking
- NMS-12976: Increase length of snmpinterfaces.snmpifdescr
- NMS-13012: Migrate Admin Guide
- NMS-13067: Inconsistent breadcrumbs on Locations/Minions
- NMS-13069: The makerpm.sh script requires the mingw32-nsis package
- NMS-13071: Upgrade Container base images
- NMS-13079: Make OpenNMS compile on Apple Silicon
- NMS-13084: Fix vmwareconfigbuilder script to run with JDK9+