Welcome to a new OpenNMS stable release with code name Bruce Springsteen aka 1.12.9 in our repositories. The release fixes various bugs and has a few nice enhancements. JRobin user are now able to use the HRULE directive which caused some compatibility issues with graph definitions between RRDtool and JRobin. For heavy non-english users working with SNMP traps have improved translated trap content. The new release allows to monitor JBoss EAP 6 or later, cause they don’t support default JMX with jmx-remoting. A new monitor is introduced to monitor an Asterisk SIP client or peer.
The full list of bugs and enhancements can be found in the Relase Notes.
If you want to join and you have something which should be on the agenda, please register the opennms-docs mailing list if you haven’t already and drop a mail with your topic under the subject: [Agenda] cw32/2014.
If you want to join and you have something which should be on the agenda, please register the opennms-docs mailing list if you haven’t already and drop a mail with your topic under the subject: [Agenda] 30/14.
We spent a lot of time during Dev-Jam refactoring the OpenNMS Provisioning Integration Server (PRIS). Most of the refactoring is regarding maven modules and OpenNMS dependencies. We have now a maven module structure for additional sources as opennms-pris-plugins. The dependency to the OpenNMS is slimmed, we build the model for Provisiond from the XSD instead of depending on a quite large opennms-service.jar from the OpenNMS Project.
The poll for changing the Wiki theme ended yesterday. As everybody can see, only 36 people had really an opinion about it. With 20 to 16 the result is close. In my opinion there is no reason to put effort in changing the Wiki theme to “Vector” as default. If somebody is still interested in this topic is welcome on opennms-discuss.
Feedback is always welcome.
Should we make "Vector" the default theme in the OpenNMS Wiki?
On OUCE 2014 in Southampton we had a very interesting discussion about how we can improve the documentation off the project. Jeff and Ken where interested to spend time on Dev-Jam on this topic. We had a brainstorming workshop and started draft for possible layout and did some research about state-of-the-art technologies. Currently there exist two parts of documentation one in the OpenNMS Wiki and one in the code base in Docbook format. We discussed some advantages and disadvantages about Docbook and Markdown with the experience from the OpenNMS PRIS project. The documentation in the code base is quite outdated and unused and the only source finding things for OpenNMS is the Wiki. We started a side project to get things sorted out. If you want to get involved in this process, feel free to get in contact with the people on the Wiki project page.
Also, a reminder: as of OpenNMS 1.12.7 and 1.13.2, the way OpenNMS starts Jetty has changed, so if you have configured OpenNMS to use AJP, or used other esoteric tweaks to the Jetty configuration in opennms.properties, you will need to adapt them to jetty.xml instead. For details, see: Whats New in OpenNMS 1.12
In OpenNMS you can use the Correlator daemon which runs Drools Expert. The current version of OpenNMS uses Drools in version 5.1.1. For the Dev-Jam week Markus, Dustin and Jeff spend time together upgrading Drools to the latest version 6.0.1 Final. The update in the code of the Correlator is done. The part in progress right now is to get the JUnit tests green for some rules build in OpenNMS. There was quite a lot of change between the old and the new version.
OpenNMS Dev-Jam has started today. Christian Pape started a small feature for showing outages in a more visual way as a timeline graph. This visual component is used on the node detail page. The box with the IP interfaces and services is reworked to have clear distinction for a current outage and an availability degradation. You want to try this? You can use a Vagrant box against the feature branch. Issues and details can be found here: