In the last week we worked on OpenBMP refactoring, ToS handling in flows, OpenNMS.js updates, documentation, PostgreSQL 13, filtering outages in the application topology view, and bug fixes.
Github Project Updates
Internals, APIs, and Documentation
- Chandra continued his work on removing OpenBMP as an external dependency
- Christian worked on adding support for ToS handling in flows
- I worked on modernizing a bunch of build and runtime dependencies in OpenNMS.js
- I worked on moving OpenNMS.js documentation to Antora
- Bonnie worked on installation, minion, and provisioning documentation
- I updated our PostgreSQL support to include 13
- David Schlenk made a fix for the
opennmsstartup script not knowing its PID in some cases
Web, ReST, UI, and Helm
- Patrick worked on updating the application topology view to support filtering outages
Contributors
Thanks to the following contributors for committing changes since last OOH:
- Benjamin Reed
- Bonnie Robinson
- Chandra Gorantla
- Christian Pape
- David Schlenk
- Dustin Frisch
- Patrick Schweizer
Release Roadmap
November Releases
The next OpenNMS release day is November 3rd, 2020.
The current plan is to release Horizon 27 as well as Meridians 2019 and 2020.
Next Horizon: 27 (Q4 2020)
The next major Horizon release will be Horizon 27.
It's going to contain a bunch of great stuff:
- improvements to node caching for flow processing
- VMware meta-data has been moved from assets to the new node meta-data
- Minion improvements, including configuration enhancements and an overhaul to RPC thread-handling
- a new handy global search bar in the web UI
- improved SNMPv3 auth configuration
- a major rework of remote poller functionality, now integrated with the Minion (we're calling it Application Perspective Monitoring)
Next Meridian: 2021 (Q2 2021)
With the recent release of Meridian 2020, plans are still tentative.
However, the current expectation is that Meridian 2021 will be based on Horizon 28, which is expected to build on Horizon 27 with additional flow and metadata improvements.
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
Jump to section
About the Author: RangerRick
