In the last week we did more bugfixing, continued to work on JDK11-based builds, a new config API, in-core BMP support, build infrastructure updates, UI/UX cleanups, and tons of documentation tweaks.

Github Project Updates

Internals, APIs, and Documentation

  • Jesse did more work on getting everything building reliably on JDK11
  • Patrick and Jesse did more work on a new unified configuration API
  • Chandra did more work on a core BMP implementation
  • Bonnie worked on some cleanup of obsolete remote poller references in documentation, plus some other Kafka, datacollection, and event translator updates
  • Ronny worked on updating our Debian build images to Buster
  • Christian added some smoke tests for daemon reloads
  • Ronny added some deployment diagrams for documentation
  • Dustin fixed a bug in Newts cache priming

Web, ReST, UI, and Helm

  • Christian added support for searching nodes that match CDP/LLDP links
  • I fixed a bug where node/interface/service availability timelines didn't scale properly (and didn't re-scale when window size changes)
  • Jane worked on a bug in handling requisitions with duplicate services
  • Jane worked on some other UI and UX bugs

Contributors

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

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

Release Roadmap

March Releases

The next OpenNMS release day is March 2nd, 2021.

Currently we expect new releases for all supported Horizon and Meridian (2018, 2019, 2020) releases.

Next Horizon: 28 (Q1 2021)

The next major Horizon release will be Horizon 28.
It is currently expected to be released during the March release cycle.

It will primarily contain enhancements to flow processing to handle ToS/QoS (DSCP) aggregation, as well as a refactor of our BGP Monitoring Protocol support to bring it in-core, rather than relying on an external OpenBMP instance.

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-12606: Rename button on Threshold Groups screen
  • NMS-12834: Broken provisiond policy does not appear in the logs
  • NMS-12879: Remote poller: review all documentation to update RP references
  • NMS-13107: Add SNMP Data Collection example to Horizon Docs
  • NMS-13117: Create smoke test that verifies all Reload daemon are successful
  • NMS-13129: Searching node link informations
  • NMS-13135: add service status to rest /info API
  • NMS-13136: Update Kafka settings for multiple instances documentation
  • NMS-13148: The OpenNMS Web User Interface Has Experienced an Error observed when searching for a Event under Event notifications
  • NMS-13153: Node's sub-option 'Availability' exceeds table alignment and overlaps next table of 'Notifications' under Topology section
  • NMS-13161: Dependabot: Upgrade Apache POI to 3.17 (CVE-2017-12626)