OpenNMS On the Horizon – Non-Root, Docs, Dependencies, Thresholding, Persisting, Time-Series, Metadata, Nephron, Minion, UI, Helm
Since last time, we worked on running as non-root, a bunch of doc updates, dependency updates, threshold validation, collection set persisting, time-series API and metadata, Nephron, Minion health check, UI improvements, and Helm dashboards.
Github Project Updates
Internals, APIs, and Documentation
I continued to work on making OpenNMS run as non-root by default.
Marcel did some more detector documentation updates.
Bonnie worked on updating the development documentation introduction.
David Schlenk updated WMI dependencies.
Chandra updated threshold values to go through some basic validation at the XSD level.
Chandra worked on bumping our Newts dependency to the latest version.
I updated a few dependencies to their latest versions. (Apache Httpclient, logback-classic, thanks Dependabot!)
Jesse fixed an issue where collection sets with null or blank labels would throw an error, rather than just not persisting.
Patrick worked on an update to the time-series API to allow using regular expressions for indexing resource paths, as well as publishing some metadata to the TSDB rather than PostgreSQL.
I worked on publishing extra build metadata to the minion-config-schema.yml during builds.
Stefan did more work on Nephron testing and benchmarking.
Web, ReST, UI, and Helm
Jane and Chandra worked on some additional features for the Minion health check ReST service.
Christian updated the service web UI to show the effective (interpolated) values of metadata parameters.
Mark's Helm update to include a welcome dashboard was merged.
Mark updated the notification web UI to note that nodeid and foreignid can be referenced in notifications.
Bonnie updated the OpenNMS and Helm docs to note what is necessary to use the grafana-image-renderer with Helm's docker image.
Bonnie worked on documentation for the flow deep-dive Helm dashboard.
Thanks to the following contributors for committing changes since last OOH:
Jian Yet Lee
OpenNMS is on a monthly release schedule, with releases happening on the first Tuesday of the month.
The next OpenNMS release day is July 6th, 2021.
We currently expect at least a Horizon 28.0.1 release, plus updates for all supported Meridian releases.
Next Horizon: 29 (Q4 2021)
The next major Horizon release will be Horizon 29.
The current roadmap for Horizon 29 includes the following goals:
running as non-root by default
refactor the Minion's communication to get rid of out-of-band ReST calls to the OpenNMS core
add support for persistence of flows to Cortex
Next Meridian: 2022 (Q? 2022)
With Meridian 2021 recently out, we do not yet have a specific timeline for Meridian 2022.
Expect it to include -- at the very least -- the JDK11 requirement and flow aggregation improvements from Horizon 28.
Ideally it will contain work going into Horizons 29 (and probably 30) if our timeline holds. 😅
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.
Resolved Issues Since Last OOH
HELM-265: Cannot use grafana-image-renderer with Helm's Docker image