The OpenNMS Group, Inc.
Toll Free (US): (877) ONMS-911 
Toll Free (US): (877) ONMS-911
It's time for This Week (Month?) in OpenNMS. In the last month, we've been pretty busy on a number of projects, including reporting and maps. My new year's resolution is to get back on track writing TWiO regularly. =)
Stable: Current Release is 1.6.8
1.6.8 is the current stable release, tagged December 10th. It adds a few small features and fixes a few bugs, as well as adding a new web-based "easy installer" UI. For a full list, see the bugzilla 1.6.8 milestone. This is a non-critical but recommended upgrade for anyone on OpenNMS versions older than 1.6.8.
Unstable: Current Release is 1.7.8
1.7.8 is the current unstable release, tagged December 8th. Since 1.7.7, there have been quite a few bug fixes. A 1.7.x overview is available in the release notes on the site.
Unstable: Reporting
Jason Aras continued his work on a dynamic reporting engine. Additionally, Jonathan Sartin has been working on the reporting scheduling daemon some more. See below for more on Jonathan's work.
Unstable: Lots of Updates
I've been slack in doing TWiO, and there's been a ton of work going on in unstable since the last post.
The move to Git is complete, and went pretty smoothly. SVN has been marked as read-only, and the new Git repository is available through http://opennms.git.sourceforge.net/ (which provides a web interface).
Full instructions on working with the git repository are available in the OpenNMS wiki.
Jonathan has finished up his work on the report scheduling API, and is ready for code review. Here's what he wrote to me about this new feature:
I have just about completed the initial work on feature-report-api. Features of this branch are:
The old availability reports can now be run on demand (as they always have been), or scheduled to run in the future (no more messing around with cron jobs outside of OpenNMS). You can save these reports as well as mail them, and they can be downloaded on demand.
There is an API in place now that should allow other report engines to use the framework that we've written (it was designed with BIRT and Jasper in mind).
The beginnings of a unified XML config are there to allow report parameters to be entered via the webUI when the report is run (it only accepts integer, string and date parameters at the moment). Multiple report xsl can used to simultaneously support multiple languages.
Next steps are to move the old reports into a new project that reflects the amended structure, and further tidying up of the old code. Demands on my time permitting, this should be in an unstable release soon.
January 25th-29th, 2010: OpenNMS training will be available through The OpenNMS Group at the OpenNMS training facility in Pittsboro, NC.
February 19th-21st, 2010: OpenNMS will be attending the Southern California Linux Expo. Additionally, Tarus Balog will be the keynote speaker.
May 6th-7th, 2010: The second annual OpenNMS Users Conference will be held in Frankfurt, Germany, thanks again to Nethinks. The call for papers ends January 31st, if you are interested in presenting.
If you have anything to add to the events list, please let me know.
As always, if there's anything you'd like me to talk about in a future TWiO, or you just have a comment, criticism, or UFO evidence that explains my loss of time you'd like to share, don't hesitiate to say hi.
