In the last week we worked on Nephron and flows, documentation, VMware updates, Minion certificate handling, OpenBMP migration, Grafana reports, and the topology map.

Github Project Updates

Internals, APIs, and Documentation

  • Dustin did more work on fixing flow data handling in Nephron
  • Bonnie worked on documentation updates for BMP and Provisiond
  • Christian worked on some fixups to VMware asset migration
  • Ronnie worked on Docker, Minion, Sentinel, and flow documentation changes
  • Dustin added some instrumentation to the flow receiver and processor
  • Stefan backported his work to support Minion server certificates to Horizon 27
  • Chandra did more work on migrating OpenBMP's functionality into the OpenNMS core
  • Jesse worked on some Nephron changes to provide near-real-time estimates

Web, ReST, UI, and Helm

  • I worked on fixing time zone handling in Grafana database reports
  • Patrick did more work on fixing topology application map alarm handling


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

  • Benjamin Reed
  • Bonnie Robinson
  • Chandra Gorantla
  • Christian Pape
  • Dustin Frisch
  • Jesse White
  • Patrick Schweizer
  • Ronny Trommer
  • Stefan Wachter

Release Roadmap

November Releases

The next OpenNMS release day is December 1st, 2020.

The current expectation is that there will be updates to Horizon 27.0.2 and Meridian 2020.

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 Week…

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-12928: Text for start page
  • NMS-12985: Upgrade script does not migrate VMware metadata
  • NMS-12998: Unable to enable Jaeger tracing in Sentinel
  • NMS-13000: backport Minion certificate management to Horizon 27
  • NMS-13002: Update typo in BMP docs

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: November 16th, 2020Last Updated: November 16th, 20202 min readTags: , , , , , , , , , ,