In the last week we worked on Nephron and flows, Karaf, Antora documentation, ticketing and alarms, smoke tests, the Minion, Swagger UI for ReST, BSM editing, and Jetty TLS configs.
Github Project Updates
Internals, APIs, and Documentation
- Stefan did more work on Nephron and flow improvements, plus his benchmarking tools
- Jesse worked on updating our embedded Karaf to 4.2.11
- Bonnie and Ronny continued to work on finalizing and improving the big Antora doc update
- Dustin fixed an issue with timeout config for flows
- Chandra fixed the default telemetry config
- Chandra worked on a bunch of fixes and improvements to ticketing and alarms
- Jesse and I worked on fixing up flapping smoke tests
- Christian fixed an issue to handle alarm reduction keys better when multiple Minions are in the same location
Web, ReST, UI, and Helm
- Jane worked on adding Swagger UI support for our ReST API
- Christian fixed a bug editing BSM edges
- Jeff tightened up the TLS settings for the default Jetty config
Thanks to the following contributors for committing changes since last OOH:
- Benjamin Reed
- Bonnie Robinson
- Chandra Gorantla
- Christian Pape
- Dustin Frisch
- Jane Hou
- Jeff Gehlbach
- Jesse White
- Marcel Fuhrmann
- Ronny Trommer
- Stefan Wachter
The next OpenNMS release day is April 6th, 2021.
Currently we expect new bug fix releases for Horizon 27 and Meridians 2019 and 2020.
Next Horizon: 28 (Q? 2021)
The next major Horizon release will be Horizon 28.
Horizon 28 will still be coming down the pipeline soon.
Currently, we hope for it to contain the move to building with JDK 11 (and, consequently, a requirement to only run on JDK 11 or higher), QoS flow aggergation, and some other improvements in the pipeline.
Next Meridian: 2021 (Q2 2021)
Meridian 2021 is on track for a release in 2nd quarter of 2021. It is expected to be based on the Horizon 27.1 codebase, which means it will contain all of the bug fixes and new features introduced in Horizon 26 and 27.
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-270: Grafana dependency for Helm install
- NMS-10188: Evaluate Swagger for REST API documentation
- NMS-10256: Change Jetty default settings to eliminate TLS 1.0 and TLS 1.1 support
- NMS-12670: Overview chapter
- NMS-12697: Can't edit reductionKey in BSM
- NMS-13028: Add WebDetector documentation
- NMS-13074: Create Win32ServiceDetector documentation
- NMS-13075: Create WmiDetector documenation
- NMS-13076: Create BgpSessionDetector documentation
- NMS-13187: Investigate using openAPI&Swagger to document v2 RESTful API
- NMS-13189: The behavior of the Ticketing API differs from older versions.
- NMS-13196: Editing a scheduled Grafana report resets the selected Grafana dashboard
- NMS-13210: The %dpname% breaks the alarm life-cycle when having multiple minions per location
- NMS-13227: Change Jetty default settings to exclude vulnerable cipher suites, expose client-initiated renegotiation