In the last week we did more documentation migration, Elasticsearch flow storage and queries, Netflow, traps, tests, and topology maps.

Github Project Updates

Internals, APIs, and Documentation

  • Bonnie continued her work on migrating the admin and installation guides to Antora
  • Chandra worked on a fix to Elasticsearch templates when using prefixes
  • Ronny did more work on updating Minion documentation
  • I worked on documentation for JICMP
  • Christian worked on Netflow v9 updates for flowStartMilliseconds and flowEndMilliseconds
  • Marcel did some work on the Slack notification strategy
  • Chandra fixed a bug that could occur when receiving traps on Minion
  • Dustin did some work on flink test infrastructure

Web, ReST, UI, and Helm

  • Stefan worked on updating the flow Elasticsearch and ReST APIs to support querying raw ToS/QoS
  • Patrick continued his work on fixing up topology map application support

Contributors

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

  • Benjamin Reed
  • Bonnie Robinson
  • Chandra Gorantla
  • Christian Pape
  • Dustin Frisch
  • Marcel Fuhrmann
  • Matthew Brooks
  • 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.1 and Meridians 2018 through 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.

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 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-12733: No support for TLS v1.3 in MailTransportMonitor
  • NMS-13006: flowStartMilliseconds/flowEndMilliseconds for NetFlow v9
  • NMS-13014: Cortex plugin shows only data for counters in a window > 3 hours
  • NMS-13015: Null pointer exception whe minion receives traps
  • NMS-13023: Add clock skew correction mechanism
  • NMS-13024: Check flow sequence numbers to detect missing packets

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