This Week in OpenNMS, Friday January 9th

The holidays are over, the hangovers have been recovered from, and in the meantime, a flurry of activity has been happening in the OpenNMS world. It’s time for another This Week in OpenNMS!

Project Updates

Stable: 1.6.2 Coming

The goal is to release version 1.6.2 next week. There have been a number of bugs fixed (and a few small features added) since 1.6.2.

Trunk: Provisioning

Work continues on the new provisioning code at a frantic pace. We’re not yet at a milestone where people can use it, but lots of pieces are coming together.

Trunk: Acknowledgement Daemon

Dave has begun work on Ackd, the OpenNMS acknowledgement daemon. This will allow API and user-interactive access to acknowledging alarms. The goal is to be able to acknowledge alarms through jabber, email, etc. upon receiving a notification of an issue.

Trunk: Alarm Daemon

Dave also worked on Alarmd, a daemon for managing persistence of alarms to improve event persistence performance and reduce delay in forwarding events to listeners.

This immediately began discussions with a large Telco in Europe about their contributing a 3GPP compliant alarm strategy. Cool.

Trunk: IRC Notification Strategy

DJ committed a notification strategy that can . . . → Read More: This Week in OpenNMS, Friday January 9th

Share on Facebook

OpenNMS 1.6.0 Is Out

…and it features a ton of changes since the last stable release. Here’s what I put in the release notes as an introduction to the 1.6.0 release:

Release 1.6.0 is the first stable release in the OpenNMS 1.6 series.

It’s been 3 and a half years since the last OpenNMS stable version, 1.2, was branched and released as production-ready. In that time, OpenNMS as a project has changed tremendously, the community has grown exponentially, and massive numbers of new features have been incorporated into the “unstable” 1.3.x series.

In that time, the unstable codebase solidified to the point that The OpenNMS Group supported it as if it were stable; it was at least as stable as 1.2.x was, but many users held off on upgrading because of the unstable moniker.

After a lot of work, and a renewed focus on getting the next stable release out the door, we are now prepared to declare OpenNMS 1.6 release-candidate-ready.

Why 1.6 instead of 1.4? 3 years is a lot of time, and a lot has happened in that time. We’re not ready to call it 2.0, we want to redo the . . . → Read More: OpenNMS 1.6.0 Is Out

Share on Facebook

Google Chrome on Mac OS X (In Wine)

Just a quick note to say that based on these instructions, I was able to get Google Chrome running on Mac OS X, using Fink.

You’ll need to enable unstable (“fink configure”, followed by “fink selfupdate-rsync”), and then do a “fink install wine cabextract”. Then start at the “offline installer” part of the instructions.


Share on Facebook

Share on Facebook

Microsoft, Why Do You Treat Me Like A Pirate?

Do you see that picture on the right? I bought Windows XP when it came out. An actual legitimate copy of Windows XP Home Edition. It promised a lot of things that it eventually pretty much delivered after a couple of service packs. It’s moved from machine to machine as I’ve updated hardware. I’ve gotten rid of basically all of my old PC hardware and now it lives on my Macbook Pro. I’ve been reasonably happy with it. Except…

With such a long history, I’ve long-since passed the time when Microsoft accepted my key without question through internet activation. Do you know what happens when you pass that time? Painful crushing phone activation.


First, you have to call a number, and enter 9 sets of 6 digits (they’re kind enough to let you use the touch-tone phone to do it, instead of braving their voice recognition system). Then, on the 9th set, it always complains that it didn’t understand the last set of digits, until you’re forced to tell it to forward you to a human without finishing the automated input.

Then, since it didn’t . . . → Read More: Microsoft, Why Do You Treat Me Like A Pirate?

Share on Facebook

OpenNMS Installer

So I’ve spent the last week or so working on a Windows installer for OpenNMS, using IzPack, an awesome Java-based installer. After some trial-and-error getting it to handle paths nicely (some of our code is not spaces-in-paths clean, so I had to hack something up to get the DOS 8.3 filename), it seems to be working!

We’re going to spend some time testing it and making sure everything works well enough to be considered an “alpha”, but this certainly appears to put us on track to have a nice installer working shortly after 1.3.8 is out — which should be any day, there are only a couple of bugs left on the blocker list.

…and since IzPack is a Java-based installer, it actually works on Mac OS X and Linux as well, and in theory, anywhere else that supports Java 1.5… (Although it is still recommended you use native package management, since you’ll get config-file management and other nice stuff…)

Share on Facebook

Share on Facebook

Embracing and Extending OpenNMS

Let me start with a story. It’s a story of answering a simple question in the #fink irc channel. What was my answer? It doesn’t really matter. What matters is that I used “..\lib” in my response.


That’s right, this week I’ve been in the Land Of Evil, working on porting OpenNMS to Windows. I’ve been so heads-down into it, I actually started thinking in backslashes even in a Mac OS X channel. Oh, the shame. <grin>

Anyways, it actually (surprisingly!) mostly works. The hardest part was porting jicmp, which required setting up a mingw environment and fixing our configure stuff in a lot of ways. And I’ve gotta say, libtool and I have had our differences in the past, but it performed beautifully at hiding the details of making a .dll file out of our code.

There’s still plenty left to do. The docbook stuff doesn’t run right. Our GWT maven plugin inexplicably fails, even though the command-line it generates actually works . . . → Read More: Embracing and Extending OpenNMS

Share on Facebook