This Week in OpenNMS: Getting Things Done

Benjamin Reed <[email protected]> Mon, 07 Feb 2011 14:52:54 -0500
Newsgroups gmane.network.opennms.announce
Message-ID <4D504D96.3080700__15962.4062748209$1297109688$gmane$org@opennms.org>
It's time for This Week in OpenNMS <http://www.opennms.org/>. In the
last few weeks we worked on reports, IPv6, and a ton of bugs.


  Project Updates

    * 1.8: Current Release is 1.8.7 (Chuck-will's-widow)
      1.8.7
      <http://www.opennms.org/documentation/ReleaseNotesStable.html#opennms-1.8.7> is
      the current stable release, tagged 8 December 2010. For a complete
      list of changes and updates, see the "New and Noteworthy" page on
      the OpenNMS wiki
      <http://www.opennms.org/wiki/New_and_Noteworthy#New_in_OpenNMS_1.8.7>.
      As always, it is recommended that you back up your database before
      upgrading.
    * 1.9: Current release is 1.9.3 (Recorder)
      1.9.3 is the current unstable release, tagged 7 December 2010.
      This release is not recommended for production use, but for
      developers and users who want to try out the very latest features.
    * Lots and lots of bugfixes have been going on, in preparation for
      1.8.8 and 1.9.4. Expected release is sometime this week.
    * Donald did more work on reports. He's like a machine. A machine
      that works on reports. A lot.
    * Seth did some more refactoring in support of IPv6.
    * Matt worked on ICMPv6 a ton, getting most of the code fleshed out
      for doing IPv6 (and v4) ping on our supported platforms. There are
      still some bugs to work out, but the guts are there. Ben also
      spent a lot of time testing what works and what doesn't on
      different OSes.


  Issues Fixed

    * [IPL-15 <http://issues.opennms.org/browse/IPL-15>] --
      install_iplike.sh has issues on Debian-based systems
    * [NMS-3469 <http://issues.opennms.org/browse/NMS-3469>] -- webapps
      won't deploy with Tomcat in 1.7.7 and 1.7.8-SNAPSHOT
    * [NMS-4084 <http://issues.opennms.org/browse/NMS-4084>] --
      provision group does not validate ip-addr field on input
    * [NMS-4103 <http://issues.opennms.org/browse/NMS-4103>] -- Upgrade
      JasperReports 3.6.0 to 3.7.4
    * [NMS-4137 <http://issues.opennms.org/browse/NMS-4137>] -- Overload
      checkbox as state indicator in alarm list when acktype=both
    * [NMS-4201 <http://issues.opennms.org/browse/NMS-4201>] -- Sort
      saved database Reports and display more than 10 of them
    * [NMS-4207 <http://issues.opennms.org/browse/NMS-4207>] --
      httpd-datacollection.xml does not allow ? in url
    * [NMS-4252 <http://issues.opennms.org/browse/NMS-4252>] --
      Provisioning problem due to ipv6 address formatting
    * [NMS-4287 <http://issues.opennms.org/browse/NMS-4287>] -- NPE when
      trying to generate reports from JRB datasources
    * [NMS-4293 <http://issues.opennms.org/browse/NMS-4293>] -- Remove
      option C from SNMP Primary pick-list in provisioning groups editor
    * [NMS-4297 <http://issues.opennms.org/browse/NMS-4297>] --
      Provisiond discovers services on capsd provisioned nodes
    * [NMS-4298 <http://issues.opennms.org/browse/NMS-4298>] --
      impossible to run JRB reports on Windows
    * [NMS-4303 <http://issues.opennms.org/browse/NMS-4303>] -- linkd
      UndeclaredThrowableException
    * [NMS-4308 <http://issues.opennms.org/browse/NMS-4308>] --
      Provisioning Groups UI throws exception when trying to sync
      unmodified group
    * [NMS-4320 <http://issues.opennms.org/browse/NMS-4320>] -- [Build]
      Some changes needed to get a clean build in Eclipse
    * [NMS-4322 <http://issues.opennms.org/browse/NMS-4322>] -- Fonts
      Very Large on KSC Reports and Admin Surveillance Categories
    * [NMS-4325 <http://issues.opennms.org/browse/NMS-4325>] -- include
      script output in event reason text for GpPoller notifications
    * [NMS-4329 <http://issues.opennms.org/browse/NMS-4329>] -- Out of
      Bounds Exception when trying to change node label
    * [NMS-4331 <http://issues.opennms.org/browse/NMS-4331>] --
      Customize Subject on Emailed Batch Reports
    * [NMS-4332 <http://issues.opennms.org/browse/NMS-4332>] -- Catch
      NullPointer Exception when running BSFScripts
    * [NMS-4341 <http://issues.opennms.org/browse/NMS-4341>] -- Opennms
      cannot start up without Internet access
    * [NMS-4347 <http://issues.opennms.org/browse/NMS-4347>] -- Typo in
      MemcachedMonitor.java
    * [NMS-4349 <http://issues.opennms.org/browse/NMS-4349>] -- Make
      compile.pl / assemble.pl actually exit with maven exit code
    * [NMS-4358 <http://issues.opennms.org/browse/NMS-4358>] -- Make
      Node available to the Beanshell
    * [NMS-4362 <http://issues.opennms.org/browse/NMS-4362>] --
      Exception raised when trying to view ip route info
    * [NMS-4369 <http://issues.opennms.org/browse/NMS-4369>] -- Change
      the logmsg and description fields for events and alarms to text
      object.


  Issues with Issues

If you'll recall, about this time last year I was extolling the virtues
of Scrum-Ban
<http://www.opennms.com/this-week-in-opennms-banning-scrum-with-scrumban/>.
We were gung-ho for a long time, and it really helped us get out from
under a number of difficult projects we were juggling. Unfortunately,
when those projects cleared up, we moved on to bug work, and that's when
things started to fall apart. Turns out our grand scrum-ban process is
not all that great for doing lots of little "janitorial" things to the
codebase.

Lately we've been trying to evaluate what did and didn't work with that.
A while back, we moved to JIRA <http://issues.opennms.org/> to allow us
to manage our issues better --- insert joke here --- previously we'd
been using JIRA <http://www.atlassian.com/software/jira/> for internal
project work, and Bugzilla <http://www.bugzilla.org/> for community
bugs. If you've ever opened an issue with us, you'll probably have
noticed a lot of emails coming lately from our issue tracker. We've been
trying to figure out a good way to manage the open bugs, prioritize
things, and just plain keep track of project work *and* bugs. We're
hoping that treating JIRA as our TODO list (rather than just something
we check occasionally for issues) will let us keep up with community
issues better. Right now, the biggest way issues get attention because
someone brought it up on IRC or on the -discuss list, which obviously
doesn't scale well. :)

We're still trying to figure out some of the details, but next week I'll
talk a bit about how we're going forward with our issue tracker.


  Upcoming Events

    * 8 February 2011: Tarus to speak about OpenNMS at the Atlanta
      Network and Systems Management Technical User Group
      <http://atlnsmtug-feb-2011.eventbrite.com/>
    * 26 February 2011: Jeff to speak at SCaLE on Large-Scale Systems
      Management with OpenNMS
      <http://www.socallinuxexpo.org/scale9x/presentations/large-scale-systems-management-opennms%3Cbr%20/%3E>
    * 28 February through 4 March 2011: The OpenNMS Group will be
      offering training at the OpenNMS HQ in Pittsboro, NC. Details are
      available at the OpenNMS.com training page
      <http://www.opennms.com/training/>.
    * 26 March 2011: Tarus to keynote the inaugural Indiana LinuxFest
      <http://www.indianalinux.org/cms/>
    * 26 through 27 May 2011: OpenNMS Users Conference Europe
      <http://www.opennms.org/wiki/UCE#OpenNMS_User_Conference_Europe_2011>
    * 19 through 24 June 2011: OpenNMS Dev-Jam 6
      <http://www.opennms.org/wiki/Dev-Jam_2011>


  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 or criticism that you'd like to share,
don't hesitate to say hi <mailto:[email protected]>.


-- 
Benjamin Reed
The OpenNMS Group
http://www.opennms.org/

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb

_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/wiki/index.php?page=MailingListFaq

opennms-announce mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-announce