By RangerRick, on December 12th, 2008%
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
By RangerRick, on December 5th, 2008%
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
By RangerRick, on November 22nd, 2008%
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
By RangerRick, on October 29th, 2008%
…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
By RangerRick, on October 23rd, 2008%
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
By RangerRick, on October 16th, 2008%
I swear, this is the only political post I will do before the elections. No, really!
As the elections get closer and closer, the more I realize Neal Stephenson is not an author, but a prophet. He (co-)wrote a book called Interface which was a book about a politician who has a stroke, and has a chip implanted in his brain by the shadow government. It restores his motor control, but has the side-effect of having the ability to trigger memories with the direction of an external wireless device (designed to be a kind of “pacemaker” for the chip).
I know it sounds pretty crazy, but in the context of the book, it actually flows pretty believably.
Anyways, he goes on to run for President, and his campaign works out a way to use this memory-trigger to their advantage. They pick a small sample of people that represent a cross-section of the country, and then hook them up to a little Dick Tracy TV with an EKG in it that transmits their immediate emotional response to whatever they show them back to the campaign (sound familiar?). . . . → Read More: The Age of Scrutiny
Share on Facebook
By RangerRick, on October 10th, 2008%
I’ve got Mono 2.0 updated and packaged up for Fink unstable. It includes Cocoa#, Gtk#, and MonoDevelop 1.0, all tested and working.
Congratulations to the Mono team on getting 2.0 released!
Share on Facebook
Share on Facebook
By RangerRick, on October 1st, 2008%
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
By RangerRick, on September 15th, 2008%
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
By RangerRick, on September 3rd, 2008%
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.
Woot!
Share on Facebook
Share on Facebook
|
|
|
Comments are closed 
