In the last week we worked on Elasticsearch indexing, malformed SNMP, CircleCI, documentation, OpenBMP migration, Nephron, Minion configuration, flow aggregation, and Helm.

Github Project Updates

Internals, APIs, and Documentation

  • Chandra backported his fix to elasticsearch indexing to foundation-2020
  • Chandra did some additional work on handling malformed SNMP responses
  • I updated some of our CircleCI projects to cache NPM differently
  • Bonnie continued her work on moving our documentation to Antora
  • Chandra continued his work on migrating our BMP support from OpenBMP to in-core
  • Dustin and Christian did more work on expanding our Nephron testing
  • Matt did more work on making Minion confd configuration more robust
  • Stefan has continued his work on supporting ToS/QoS in flow aggregation

Web, ReST, UI, and Helm

  • I fixed a Grafana compatibility issue in Helm flow datasource
  • Stefan worked on adding TypeScript support to Helm's build
  • Stefan added a "host" panel to the flow deep dive dashboard in Helm


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

  • Benjamin Reed
  • Bonnie Robinson
  • Chandra Gorantla
  • Christian Pape
  • Dustin Frisch
  • Matthew Brooks
  • Stefan Wachter

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

  • HELM-261: The transformation withGroupByInterval from the Flow DS is not working
  • NMS-11043: MailTransportMonitor
  • NMS-12818: ArrayIndexOutOfBoundsException thrown by the SNMP Interface Poller
  • NMS-13001: bad repository settings?
  • NMS-13030: When using a custom prefix, the Elasticsearch Forwarder for events and situation-feedback creates a wrong template.
  • NMS-13042: ArrayIndexOutOfBoundsException thrown by the SNMP Interface Poller

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 14th, 2020Last Updated: December 14th, 20203 min readTags: , , , , , , , , , , , , , , ,