OpenNMS, Chef and Vagrant

Configuration management is good and a lot of people use Puppet and Chef to get their zoo of machines under control.

David Schlenk build a really nice OpenNMS cookbook and published it free as in freedom on GitHub and in the Chef supermarket. The cookbook is up to date for OpenNMS 14 and allows very detailed configuration of OpenNMS through Chef.

There is also a really light Chef cookbook, which does just some configuration stuff like JRobin/RRDtool and some basic OpenNMS settings which is mainly designed to spin-up OpenNMS in a Vagrant Environment.

So feel free to give it a try.

Big thank you to David Schlenk for the work maintaining his great OpenNMS cookbook.

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

[Release] – OpenNMS 14

We are happy to announce the new OpenNMS stable release. Yes, there is no typo in the headline, OpenNMS *fourteen*.

opennms-release-1.14

Since 12 years, the makers of OpenNMS decided to drop the “1.” from the version numbers. There is also a change how the OpenNMS is developed and it is now following the Gitflow model. This will result in a much more stable Master branch and will be the next major stable release 15, followed by 16, etc.

You can find all the new features described in the What’s New page.

During the last year, OpenNMS started to develop a new time series data storage library. Published under the Apache License, this technology is built on Cassandra. This project is aimed at meeting Big Data and Internet of Things needs by providing fast, hugely scalable and redundant data storage. You can find out more about this technology here http://newts.io

newts-logo

While not yet integrated with OpenNMS, the 1.0 release is the first step in the process. Users will have the option to replace the JRobin/RRDtool storage strategies with Newts. Since Newts stores raw data, there will be a number of options for post-processing and graphing that data that I know a number of you will find useful. Whether your data needs are simple or complex, Newts represents a way to meet them.

You can get the new release from the repos for RHEL based systems on yum.opennms.{org,eu} or for Debian based systems on debian.opennms.{org,eu}.

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr
m4s0n501

[Release] – OpenNMS 1.12.9-2

There is a hotfix release of OpenNMS 1.12.9-2 available. The reason is an issue with the SSH access to Karaf which is listening on all public network interfaces in 1.12.9-1. The isssue is in

File: $OPENNMS_HOME/etc/org.apache.karaf.shell.cfg

--- sshHost=0.0.0.0
+++ sshHost=127.0.0.1

The change in 1.12.9-2 fixes the listening to local loopback.

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

[Release] – OpenNMS 1.12.9

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.

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

[Meeting] CW32/14 Documentation

We preparing our next meeting talking about the official documentation and the community wiki based documentation. If you want to participate you can find information here:

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.

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

[Meeting] CW30/14 Documentation

We preparing our next meeting talking about the official documentation and the community wiki based documentation. If you want to participate you can find information here:

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.

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

[Release] – Provisioning Integration Server (PRIS) 1.1.0

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.

More information:

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

Poll results for OpenNMS Wiki Theme

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?

  • yes (56%, 20 Votes)
  • no, leave it as it is (44%, 16 Votes)

Total Voters: 36

Loading ... Loading ...
Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr

[Dev-Jam] Documentation workshop

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.

Tweet about this on TwitterShare on Google+Share on LinkedInShare on RedditShare on StumbleUponShare on Tumblr