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

This Week in OpenNMS, Friday December 19th

It’s been a pretty busy week here in OpenNMS land.

Project Updates

Stable: RT Ticketing Plugin

Jonathan got his RT ticketing updates finished, along with some OTRS cleanup. These have been merged back into trunk and the 1.6-testing branch, so should be ready pending a review, for the 1.6.2 release.

Stable: More Vendor Traps

Jeff spent some time adding more SNMP collection, graphs, and trap events for a number of agents, including SNMP Informant and AIX.

Trunk: IfIndex Persistence

Antonio committed a small change to the event and alarm persistence code to allow Trapd to extract IfIndex from varbinds if it is available.

Trunk: Provisioning

We continued to focus on the new provisioning daemon and API, with a lot of design work and pair programming going on, especially on Matt’s part. We all spent time this week breaking the work up into smaller chunks so we can get a better idea of what our progress is.

Donald continued to work on the detector code, adding more detectors, tests, and cleanups to the existing code.

I’ve been working on creating the model for the configuration that will drive provisioning, including changing the default . . . → Read More: This Week in OpenNMS, Friday December 19th

Share on Facebook

This Week in OpenNMS, Friday December 12th

So far the response has been positive to TWiO, so it’s time again for another chapter.

Project Updates

Stable: Ticketing Updates

Jonathan Sartin worked more on the OpenNMS trouble-ticketing API, finishing up a change to allow ticketer plugins to be able to raise exceptions when errors occur. In addition, he resurrected work on an RT (Request Tracker) ticketer plugin. Both will be merged to the 1.6 branch when they’re ready.

Stable: Bug Fixes

I spent a little time this week cleaning up some bugs, mostly exceptions, simple bugfixes, and other minor changes.

Stable: Windows Updates

Bobby Krupczak was kind enough to lend a Win64 machine with Visual Studio so I could get 64-bit binaries built. They are available now on SourceForge. (Copy the jicmp and msvcr90 DLLs to your system directory, don’t forget to rename them to remove the -win64 bit.)

In the process of working on that, a reasonably serious bug was found in the JICMP libraries on Windows. Windows passes around HANDLEs instead of file descriptors for the purposes of file I/O (and socket I/O). We were treating them as if they were normal file handles (ie, integers), which just . . . → Read More: This Week in OpenNMS, Friday December 12th

Share on Facebook

This Week in OpenNMS, Friday December 5th

I was recently remembering fondly the oldskool “OpenNMS Updates” that Shane O’Donnell used to do, and I thought I’d take a crack at reviving the tradition. So, without further ado…

Project Updates

Stable: Current Release: 1.6.1

OpenNMS 1.6.1 seems to be holding up without any huge bugs reported. There are no immediate plans for a 1.6.2 release but I would expect we’ll look into doing one in a month or so just to roll up any bugfixes that have happened, if nothing else.

Stable: Configuration Tweaks

David did some configuration changes that will be in a future 1.6 release which automatically roll up SNMP LinkUp and LinkDown traps into an alarm. Also, Jeff added a bunch of IETF and vendor MIB data collection and graphs to the 1.6 branch.

Trunk: Provisiond

Development is still churning along in trunk, with the focus on the Capsd rewrite. Since this is the first (of hopefully many) TWiO, I will go into a bit more depth.

OpenNMS has always been written with scalability in the forefront of our minds, but JVM technology and development methodologies have moved a lot since we first started the project 9 years ago. Since . . . → Read More: This Week in OpenNMS, Friday December 5th

Share on Facebook

PostgreSQL ‘IPLIKE’ Plugin Available for Windows

Since we (regrettably <g>) support a couple of customers running OpenNMS on Windows, I spent some time yesterday getting IPLIKE built on it, finally. You no longer have to rely on the slow PL/PGSQL version of it, and can instead use the nice speedy native C version instead.

For details, see the wiki page for IPLIKE.

As far as I’m aware, there is not a win64 version of PostgreSQL, so I’ve punted investigating what it would take to get stuff built on it, but I would like to get a 64-bit JICMP built at least. Does anyone have a win64 development environment that could get it building for us? I have no Win64 licenses, much less development environment. A little investigating dug up a MinGW64 preview, but I have no idea if it would actually work or not. =)

If you run into any problems with it, let me know!

Share on Facebook

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

OpenNMS 1.6.0 On the Horizon

So I just finished getting OpenNMS 1.5.98 out the door. This is the first release that we’ve left a few (small) known issues in because we’re in hard freeze.

I am so ready for this release to be out; there have been a ton of improvements since 1.2.x and the sooner we can get folks to the current codebase, the better.

Of course, while I was in the process of writing this blog post, Dave found a small but not-insignificant bug that is worth doing another RC for, so here comes 1.5.99! 😉

Share on Facebook

Share on Facebook

OpenNMS 1.5.94/1.5.95/1.5.96 Released

After a few issues with an annoying poller bug and some cross-site scripting issues that ended up triggering a series of quick releases over just a few days, things are settling down again in the wake of the OpenNMS 1.5.94-1.5.96 releases.

Let me start by saying, holy crap we fixed a lot of bugs, and we’re on track to get 1.6 out the door in the next month or so. There’s only a few bugs left, and we’re pretty much 100% focused on finishing those off.

For the first time in a while, this is more than just a suggested update, since a number of cross-site security issues were fixed. If you’re running anything in the OpenNMS 1.3.x or 1.5.x series, it is very strongly recommended that you upgrade to 1.5.96.

As always, feedback is encouraged, please let us know if you run into issues, awesomeness, or anything inbetween. 😉

Share on Facebook

Share on Facebook

OpenNMS 1.5.94 Coming

So I’m getting really excited about the next OpenNMS release on the road to 1.6. We’ve got over 100 more bugs closed since 1.5.93, and only 22 left before we can release a 1.6 release candidate. We’re holding off on 1.5.94 because of a rather interesting bug that can cause strange outage results for nodes not using the “critical service” functionality. Matt’s worked out a unit test for it, so hopefully we’ll have it wrapped up shortly and get the release out this week.

That said, if you’re interested in helping us wrap up the bug-search for 1.6, feel free to try out the “1.6 testing” snapshot RPMs by following the yum installation instructions for the “testing” release and giving it a shot, and open a bug if you find any issues.

One of the big blockers holding up a real release is consolidating the installation documentation in one place, be it the wiki, or the out-of-date install guide. If you have suggestions on things that could be clearer for installation, configuration, or anything else, please open a bug! At this point OpenNMS is pretty . . . → Read More: OpenNMS 1.5.94 Coming

Share on Facebook

OpenNMS Dev-Jam 2008 Developer Journal

So I’ve been meaning to do a Dev-Jam 2008 summary since we got back last weekend, and I can put it off no longer.

In summary: Dev-Jam 2008 was a huge success!

Sunday, July 27th, SVN revision 9618

We loaded up in the Dev-Jam Express and started the drive from North Carolina to the Georgia Tech campus. After plenty of rest stops, food breaks, passing water towers that look like giant spanked butts, and picking up of supplies, we arrived.

We got settled in, got room keys, met with the other folks who had arrived, and recuperated from a long drive.

Monday, July 28th, SVN revision 9622

Tarus started out by welcoming everyone and doing a “State of OpenNMS.” Since last year we blew away our goal, “2007: The Year of 4 Releases”. Development has increased dramatically, despite the fact that off and on, OpenNMS regulars have been busier than ever with non-OpenNMS projects. Of course, new regulars have joined in the fray. (Does that make us “more regular”?) Anyways, OpenNMS has gotten easier to install, more robust, and just plain better in every . . . → Read More: OpenNMS Dev-Jam 2008 Developer Journal

Share on Facebook