This Week in OpenNMS: Halt! Hammerzeit!

It’s time for This Week in OpenNMS. This week we put out a new release, as well as continued development on the road to 1.8.

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.3
    1.7.3 is the current unstable release, released May 3rd. It fixes a number of 1.7.2 bugs, and is the first public release including the new ACL code. A 1.7.x overview is available in the release notes on the site.
  • Unstable: Database Schema Management
    I finished recreating our schema in LiquiBase, and am now working on replacing our existing (scary) schema-transitioning code to use it. I hope to have things wrapped up this week.
  • Unstable: ACL UI Work
    Massimiliano Dessì has been working on converting his awesome ACL web UI proof-of-concept to Hibernate so it will integrate with our system more deeply. Hopefully this will be finished up before 1.8 goes final, but if not, it will probably be included in a later 1.8.x release.
  • Unstable: Thresholding Rework
    Alejandro has been working on the new thresholding code a lot this week. I’m told this will reduce the memory footprint of thresholds quite a bit, as well as support in-line thresholding of latency data in addition to collections.
  • Unstable: RANCID Updates
    Guglielmo made some changes to the RANCID integration code; he’s started working on reporting from RANCID data. Also, RANCID web service 0.93 was released this last week, which had a few bugfixes in the RANCID side of the integration.

OpenNMS 1.6.5 Released

New Features and Enhancements

  • Capsd will now use ifHighSpeed instead of ifSpeed when available (Bug #1822)
  • The SNMP configuration shipped with OpenNMS now uses SNMP v2c, fewer retries, and a longer timeout by default, for more efficient scanning. (Bug #3050)
  • Data collection and graphing has been added or updated for Alcatel-Lucent, Allot, Alteon, Aruba, Ascend, Avocent, Bluecat, BlueCoat, Cisco Airespace, Lucent, NetApp, Overture, Packeteer, and Powerware devices (Bugs #3096, #3099, #3109, and #3138)
  • Support has been added for using raw instance identifiers in thresholds when no data source label can be inferred (Bug #3108)
  • Support was added for a number of new Cisco devices in Linkd (Bug #3110)
  • Support has been added for extracting the bgpPeerRemoteAddr instance identifier from the varbinds of the bgpEstablished and bgpBackwardTransition traps defined in the BGP4-MIB. This allows us to make meaningful alarm annotations for these events so that the resulting alarms can self-clear. (Bug #3156)
  • Some tools have been added to OpenNMS “contrib” for creating SNMP walk dumps suitable for debugging with OpenNMS’s mock SNMP server. (Bug #3173)
  • The default “Database” category now includes MSSQL and Oracle in addition to MySQL and PostgreSQL. (Bug #3175)

Bug Fixes

  • The Capsd HTTP plugin now properly honors response-text parameters. (Bug #2774)
  • The HTTP collector now properly honors the “retry” parameter. (Bug #3133)
  • The Hyperic HQ service monitor definition now detects Hyperic HQ 4.x properly. (Bug #3106)
  • Multiple nodes with the same name/label can now be distinguished from each other in category views. (Bug #3112)
  • Vacuumd cleans out old (invalid) nodes from topology map tables. (Bug #3121)
  • The JMX collector now works when store-by-group persisting is enabled. (Bug #3160)
  • Configuration file filtering has been fixed so that tags aren’t properly expanded in opennms.properties. (Bug #3174)
  • The remote poller build now ensures it is compiled with the correct version of Groovy. (Bug #3176)

The full list of changes is available in bugzilla.

SourceForge Community Choice Awards

Last week, SourceForge opened nominations for the 2009 Community Choice Awards. These annual awards provide a chance for the larger open source community to recognize the projects that they get the most out of. The OpenNMS project has made a strong showing in past years in the “Best Project for the Enterprise” category: a crowded field to be sure, but we think the most appropriate for a product that spans so many of the other categories.
If you use and love OpenNMS, you can help by nominating the project yourself — just click below, then select “Best Project for the Enterprise” from the drop-down list. Thanks in advance!
Nominate OpenNMS

Halt! Hammerzeit!

In case you missed Tarus’s Post, we now have an OpenNMS mailing list for discussion in German. We have quite a few German-speakers using OpenNMS (especially given the increased mindshare thanks to Nethinks and iX Magazine) — so if you’d like to connect with other users, feel free to sign up for the mailing list here.

Upcoming Events

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

Auf Wiedersehen

That’s it for this 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 lawn care tip 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: , , , , , , , , , , , , , ,

Stay Connected

Subscribe to this site and get the latest project and event updates

Subscribe via RSS
  • Facebook
  • Twitter
  • identi.ca

OpenNMS Site Archives