• Home
|
• About The OpenNMS Group
|
• Our Clients
|
• Partners
|
• News + Events
|
• Contact Us

Enterprise Support: (877) ONMS-911

OpenNMS Platform

Get the Network to Work™

Try OpenNMS Today!

This Week in OpenNMS: Long Time A-Comin’

by Benjamin Reed: April 13, 2010

It’s time for This Week in OpenNMS. This week we did more 1.8 work, and got the copyright for the original OpenNMS 1.0 code.

Project Updates

• Stable: Current Release is 1.6.5
  1.6.5 is the current stable release, released May 16th. It fixes a number of bugs, and adds a few features. For a full list, see the bugzilla 1.6.5 milestone. This is a non-critical but recommended upgrade for anyone on OpenNMS versions older than 1.6.5.
• Unstable: Current Release is 1.7.4
  1.7.4 is the current unstable release, released June 8th. Since 1.7.3, more work has gone on in the Provisiond code, as well as ACLs, RANCID reports, thresholding fixes, enabling maps by default, and an entirely new way of creating the OpenNMS database under the covers. A 1.7.x overview is available in the release notes on the site.
• Unstable: Modularizing the Web Build
  Donald has been continuing his work on breaking up the webapp build.
• Unstable: SMS Poller
  I spent a little time trying to mock up some code for the SMS poller feature.
• Unstable: ACL UI Work
  Massimiliano Dessì has been wrapping up his ACL UI work in his branch.
• Unstable: Alarm Cleanup
  Dave modified the database to automatically remove alarms when the node they are related to are deleted.
• Unstable: RANCID Updates
  Rocco made some changes to the RANCID API code.

Copyright Changes

In case you don’t follow Tarus’s blog, he announced some great news that’s been a long time coming: The OpenNMS Group has purchased the rights to the original OpenNMS 1.0 code.
If you don’t know the backstory, OpenNMS was first developed by PlatformWorks, which became Oculan, who distributed appliances based on the OpenNMS codebase. OpenNMS was developed as an open-source platform, but Oculan eventually stopped working on the OpenNMS code to focus on the appliance exclusively.
The OpenNMS open-source project was then continued by Tarus Balog, who grew the project into what you see today. (All the dirty details are in Tarus’s post if you’re interested.)
What does that mean for you? In the short term, not much. Our first order of business is trying to figure out where it makes sense to add the classpath exception to allow importing OpenNMS classes without GPL infection — for example, to be able to write a trouble-ticketer plugin that talks to a proprietary ticketing system’s Java API.
Step one is to clean up our horrible mishmash of copyright notices in class files and such. =)

SourceForge Community Choice Awards: OpenNMS is a Finalist – Vote Now!

There’s still time to vote for OpenNMS in the SourceForge Community Choice Awards. If you haven’t already, please vote for OpenNMS here!
We put together a video featuring some members of the OGP introducing themselves and discussing the reasons why OpenNMS should win this award. Have a watch!
If you don’t have ten minutes to spare, check out the one-minute trailer instead.
Either way, don’t forget to vote for all of your favorite projects!

Vote Now!

Upcoming Events

• August 12, 2009: Tarus will be giving a talk at OpenSourceWorld: DM4: The Open Source Management Stack.
• September 21st-25th, 2009: OpenNMS training will be available through The OpenNMS Group at the OpenNMS training facility in Pittsboro, NC.

If you have anything to add to the events list, please let me know.

Until Next Week…

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 OpenNMS-themed fireworks display you’d like to share, don’t hesitiate to say hi. Also, we’ve still got room for more Order of the Blue Polo members if you’d like to send your own testimonial. (Of course you would!)

Tags: acls, alarmd, build system, cca, copyright, oculan, OpenNMS, opensourceworld, rancid, sms, sourceforge, training