DEV Community

loading...
Cover image for OpenNMS On the Horizon – Docs, Non-Root, Time-Series, Telemetryd, Karaf, VMware, Docker, Vue
OpenNMS

OpenNMS On the Horizon – Docs, Non-Root, Time-Series, Telemetryd, Karaf, VMware, Docker, Vue

Benjamin Reed
Developer at OpenNMS by day, member of SIBR and the Seattle Garages by night.
Originally published at opennms.com on ・5 min read

Since last time, we worked on more documentation, running as non-root, time-series API enhancements, a Telemetryd Karaf CLI, VMware script fixes, Docker Content Trust, and various Vue3 UI exploration.

Github Project Updates

Internals, APIs, and Documentation

  • Mark did more work on cleaning up various provisioning and detector documentation.
  • I worked on more fixes to the changes for running OpenNMS as non-root.
  • Patrick did more work on wrapping up his tag enhancements to the time-series API.
  • Bonnie updated a bunch of monitor docs and added docs on the search bar, plus other table formatting fixes.
  • Chandra did more work on his PoC of a state-sync API for Minion and OpenNMS communication.
  • Dustin wrapped up his code to add a Karaf CLI for examining Telemetryd.
  • Christian fixed a missing jar dependency in the VMware scripts.
  • I fixed an issue with Docker Content Trust signing not being triggered in certain build branches.
  • Marcel enhanced the Prometheus exporter docs.
  • I worked on bumping a number of our dependencies to newer versions.

Web, ReST, UI, and Helm

  • Mike and Freddy did more work on a Vue 3 PoC UI.
  • I continued my work on cleaning up the IP interface model to make it ReST queryable.
  • Jane continued her work exploring technology to be used in a Vue-based topology UI.

Contributors

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

  • Benjamin Reed
  • Bonnie Robinson
  • Chandra Gorantla
  • Christian Pape
  • Dustin Frisch
  • Freddy Chu
  • Jane Hou
  • Marcel Fuhrmann
  • Mark Mahacek
  • Mike Rose
  • Patrick Schweizer
  • Ronny Trommer
  • Stefan Wachter

Release Roadmap

July Releases

In July, we released updates to all OpenNMS Meridian versions under active support, as well as an update to Horizon 28.

Horizon 28.0.1

Release 28.0.1 contains a bunch of bug fixes and enhancements, plus a few security updates.

The codename for Horizon 28.0.1 is Optimus Prime.

For a high-level overview of what has changed in Horizon 28, see What’s New in OpenNMS Horizon 28.

Meridian Point Releases

All Meridian releases this month contained security updates, so it is recommended that you upgrade.

Starting in Meridian 2019, improvements to the Kafka provider were added, and Meridian 2021 includes a bunch of other small bug fixes and enhancements.

For a list of changes, see the release notes:

August Releases

OpenNMS is on a monthly release schedule, with releases happening on the second Wednesday of the month.

The next OpenNMS release day is August 11th, 2021.

We currently expect a Horizon 28.0.2 release, plus updates to Meridian 2021.

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
  • start the groundwork for replacing the topology UI with a pure-javascript version

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

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-8050: Documentation for Cassandra/Newts doesn't mention how to setup cassandra
  • NMS-8230: Database Report section in Admin Guide seems not merged correctly
  • NMS-8662: Create documentation for filter criteria
  • NMS-9521: Reorder the sections in the admin guide for better flow
  • NMS-11774: Improve install guide with SELinux and Firewall
  • NMS-11786: Create performance data collection user documentation
  • NMS-11798: Add information to the WEB GUI in the building rules area for notifications
  • NMS-11895: Create documentation for Enhanced Linkd
  • NMS-11939: User documentation for Enhanced Linkd
  • NMS-12011: Document best practices for tuning Newts
  • NMS-12373: Admin guide still uses deprecated term "provisioning group" in places
  • NMS-13005: Create docs about Newts confd parameters
  • NMS-13356: TSS 2.0: Improved Tag handling
  • NMS-13364: Table formatting issue in new docs
  • NMS-13434: Upgrade Influxdb plubin to TSS2.0
  • NMS-13444: vmwareconfigbuilder and vmwarecimquery not working anymore
  • NMS-13448: Doc typos - improper character escaping

Discussion (0)