DEV Community

Cover image for OpenNMS On the Horizon – New Year, New OOH
Benjamin Reed for OpenNMS

Posted on • Originally published at opennms.com on

OpenNMS On the Horizon – New Year, New OOH

In the last few weeks we did very little, as The OpenNMS Group is officially on holiday from Christmas to the New Year. However, a few small changes made it in before everyone disappeared for a while.

No matter what you celebrate, I hope y'all had a good holiday while we were radio silent, and have a better 2021 than you did 2020.

Github Project Updates

Internals, APIs, and Documentation

  • Stefan did more work on time-window and aggregation logic in Nephron
  • Ronny worked on some Minion documentation updates
  • Matt continued to work on tweaking his Minion confd improvements
  • Ronny updated a bunch of build environment Docker configs to newer versions (Ubuntu, JDK, etc.)

Contributors

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

  • Matthew Brooks
  • Ronny Trommer
  • Stefan Wachter

Release Roadmap

January Releases

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

The current expectation is that there will be Meridian 2019 and 2020 bug fix releases, as well as 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 deep 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.

Disclaimer

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

Top comments (0)