In the last week we continued to work on bug fixing and improvements related to Nephron and flows, Minion, packaging and configuration, and the web UI.

Also, this is your reminder that The OpenNMS Group shuts down offices from Christmas Eve through the new year. A number of us will probably stay randomly active on chat, but you won't see a new OOH until January.

Whether you celebrate Christmas, or something else, or nothing at all, I hope you have a good holiday season and I'll see you on the other side of 2020!

Github Project Updates

Internals, APIs, and Documentation

  • Chandra fixed an issue in timeouts in a few custom SNMP-related Karaf commands
  • Dustin continued to work on fixing flow timestamp issues
  • Jesse, Christian, and Dustin worked on some test tools for analyzing flow captures
  • Marcel updated the PostgreSQL JDBC driver to handle newer auth protocols
  • Zoë worked on a fix to JRobin handling that could cause failures in special cases
  • Matt created a schema for our confd Minion configuration
  • I added a weak dependency on haveged to our OpenNMS packages
  • Stefan made some date-related fixes to Nephron

Web, ReST, UI, and Helm

  • Stefan continued his work on enhancing the flow deep dive dashboard with QoS/ToS data
  • Chandra and Bonnie made more UI tweaks to the provisioning scan UI


Thanks to the following contributors for committing changes since last OOH:

  • Benjamin Reed
  • Bonnie Robinson
  • Chandra Gorantla
  • Christian Pape
  • Dino Yancey
  • Dustin Frisch
  • Jesse White
  • Marcel Fuhrmann
  • Matthew Brooks
  • Stefan Wachter
  • Zoë Knox

Release Roadmap

January Releases

The next OpenNMS release day is January 5th, 2020.

The current expectation is that there will be a Horizon 27.0.3 release with bug fixes.

Next Horizon: 28 (Q1 2021)

The next major Horizon release will be Horizon 28.

We're still early 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.

- Ben

Resolved Issues Since Last OOH

  • NMS-13040: Updating UI to clarify rescan process
  • NMS-13049: Update PostgreSQL JDBC drivers
  • NMS-13055: Karaf command 'snmp-fit' not functional
  • NMS-13060: Long datasource names are truncated and are not accessable on read

Jump to section

About the Author: RangerRick

Principal Software Engineer. Manages the release process of OpenNMS Horizon and Meridian, and a bunch of other stuff.
Published On: December 21st, 2020Last Updated: December 21st, 20203 min readTags: , , , , , , , , , , ,