gmane.network.opennms.announce http://blog.gmane.org/gmane.network.opennms.announce hourly 1 1901-01-01T00:00+00:00 Gmane http://gmane.org/img/gmane-25t.png http://gmane.org Final Reminder: Early Bird Discount Ends Fridayfor OUCA http://comments.gmane.org/gmane.network.opennms.announce/262 <pre>The first ever OpenNMS Users Conference Americas will be held the last week in June at the University of Minnesota: http://www.opennms.org/wiki/OUCA2012 The cost for three days of intense OpenNMS discussion is $300, and if you register before Friday it's only $250. We also have discounted dorm rooms available which makes this one of the least expensive ways to get OpenNMS training available. Click on the link above to see the current agenda, and hope to see you there. -T </pre> Tarus Balog 2012-05-23T12:50:44 OpenNMS 1.10.2 on Hold,OpenNMS 1.10.3 Coming Soon http://comments.gmane.org/gmane.network.opennms.announce/261 <pre>Gang: We've discovered a nasty bug in provisiond in 1.10.2. It's so nasty that we need to release a 1.10.3 with the fix, but we want to do some further testing, so 1.10.3 will be out on Monday, Tuesday at the latest. If you have already upgraded and you are experiencing issues with synchronizing provisioning groups, you can active the "testing" repository and upgrade to a 1.10.3-0 version that contains the fix. http://www.opennms.org/wiki/Tutorial_Choosing_a_Release For those of you who detest detail, you can skip this next part. The problem arose from an attempt to fix an issue at a client with a) a large network and b) a lot of provisioning changes. They were experiencing file handle leaks, and we believe we have found an issue with a library that we import into OpenNMS. We applied the fix and this leak disappeared. Unfortunately, the fix allowed a deadlock condition. A deadlock is a nasty little loop which occurs when one part of the code is waiting on another part of the code to finish, and that second part is, in turn, waiting on the first. We've addressed the deadlock condition and we are spending the weekend trying to determine if this also addresses the file handle leak. Once we are happy that both issues have been resolved, we'll send out a 1.10.3 (and I'll send out another e-mail). Again, sorry for the inconvenience. -T </pre> Tarus Balog 2012-05-18T16:59:23 OpenNMS Users Conference Americas Agenda http://comments.gmane.org/gmane.network.opennms.announce/260 <pre>Gang: Having just returned from the fourth OpenNMS Users Conference Europe we are heads down preparing for the first OpenNMS Users Conference Americas to be held in Minneapolis, MN, USA at the end of June. http://www.opennms.org/wiki/OUCA2012 The Call for Papers is still open, but below is a list of talks we've already approved. Remember that the early bird discount ends on 25 May. -T ==== Planned Talks ==== Keynote: OpenNMS Futures by Matt Brozowski Matt is the chief architect of OpenNMS and this presentation will highlight some of the new features currently under development, from a new user interface, topology discovery and the distribution of collected data as we make our slow and careful way toward OpenNMS 2.0. Project Management of OpenNMS Installations by Alex Finger. This presentation will focus on the best practices for deploying OpenNMS in a large scale environment. The necessity of good project management techniques can not be overstated in order to create a successful solution. Alex was responsible for one of the largest deployments of OpenNMS when we worked at Swisscom Hospitality Services. Instrumenting Java Applications Using JMX by Markus Neumann Java Management Extensions (JMX) provide a powerful way to expose application performance data. This presentation will discuss code changes needed to implement JMX in a Java application, as well as how to configure OpenNMS to collect this data. Markus will introduce a number of new tools created to make this process easier. Integration of Puppet with OpenNMS by Jeff Gehlbach and Ronny Trommer The addition of configuration management functions provided by Puppet into the OpenNMS platform is a great way move closer toward bringing IT management under one "pane of glass". This talk was given to a packed room at FOSDEM this year, and it is a great way to both extend OpenNMS functionality as well as to demostrate the numerous integration points the platform provides. Using OpenNMS with NagViz by Michael Batz NagViz was designed as a network visualization platform for Nagios, but with a few changes it can be used with OpenNMS. This presentation will show how NagViz can be integrated with OpenNMS to provide geographical and logical views of the network and to reflect the status of network elements. Selling Open Source and OpenNMS in Your Organization by Tarus Balog Despite the success of open source software, many organizations are still hesitant to adopt it for a variety of reasons. This session will present some ideas on selling open source in general and OpenNMS specifically in your organization. It will focus on the benefits of open source software in terms to which management can relate, focusing on improving the big three of time to deploy, quality of results and cost of ownership. </pre> Tarus Balog 2012-05-16T12:23:42 Upcoming OpenNMS Events http://comments.gmane.org/gmane.network.opennms.announce/259 <pre>Gang: We have a lot of great events coming up in the next two months. Next week is our fourth annual OpenNMS Users Conference Europe. There is still time to sign up (until Friday) if you want to join us in Germany for four days of classes and presentations: http://www.opennms-conference.info/ We have also announced our next week-long training class to be held at company headquarters in Pittsboro, NC, USA the week of 4-8 June: http://www.opennms.com/training/ Next, our seventh (wow) annual developers conference, Dev-Jam, will be held in Minneapolis, MN, USA the last week in June. http://www.opennms.org/wiki/Dev-Jam_2012 If you develop on OpenNMS, this is a great way to spend a week with most of the major contributors and to sharply hone your skills with respect to the OpenNMS code. And now for the big news, we are also announcing the first ever OpenNMS Users Conference Americas to be held for three days starting 26 June: http://www.opennms.org/wiki/OUCA2012 Modeled on the European conference, the first day will consist of a seminar (taught by yours truly) covering the basics of OpenNMS. The last day will consist of a barcamp. This is an "unconference" where the attendees set the agenda. We'll entertain suggestions for talks, vote on them, and then present the most popular ones. With most of the development team in attendance, pretty much any topic is up for grabs and expect it to be addressed by experts. The middle day is very special. It is a standard conference day that we would like to use to focus on our community. That means you. We'll be giving a roadmap presentation first thing, but then we'd love to fill the day with presentations by you on how you use OpenNMS. If you are interested, send an e-mail to the call for papers: cfp&lt; at &gt;opennms.org telling us what you'd like to talk about. If it gets accepted, you'll receive a complementary conference pass. I wish I could cover the air travel as well, but we will cover the conference, room and board for our speakers. Since I have your attention (I hope - sorry for the long e-mail) let me take the opportunity to once again thank you for your business. Not only do you make OpenNMS better by testing its limits, you make it possible. Hope to see you in person soon. -T </pre> Tarus Balog 2012-05-03T10:58:27 OpenVND - The Open VeNDing Project http://comments.gmane.org/gmane.network.opennms.announce/258 <pre>Gang: Here at OpenNMS we like to say we can use the management application to monitor just about anything you can put on a network. So how about a drink machine? We set out to do just that, and the result is the OpenVND project: http://www.openvnd.org This is how we manage the soda machine in the office, and we hope it give you some ideas on solving some of your more complex management problems. -T </pre> Tarus Balog 2012-04-01T14:11:09 OpenNMS User Conference - May 2012 http://comments.gmane.org/gmane.network.opennms.announce/257 <pre>Registration is now open for the OpenNMS User Conference in Europe this May: http://www.opennms-conference.info/ This is one of my favorite events of the year, and this year we are making available two days of training - "bootcamp-style" accelerated lectures that are the fastest way to come up to speed on OpenNMS. Hope to see you there, -T </pre> Tarus Balog 2012-02-29T16:08:04 OpenNMS iOS App 40% Off Until February 26th http://comments.gmane.org/gmane.network.opennms.announce/256 <pre>In case you missed it on Twitter, we are celebrating the release of OpenNMS 1.10 by offering the iPhone/iPad app for 40% off ($2.99 US) now until February 26th. You can get it here: http://itunes.apple.com/app/opennms/id389479744?mt=8 </pre> Benjamin Reed 2012-02-15T14:59:00 OpenNMS 1.10 Released http://comments.gmane.org/gmane.network.opennms.announce/255 <pre>Gang: I am happy to announce that we have officially released OpenNMS 1.10 - the first new stable release since June of 2010. A lot of work went into this release, and although the web user interface has not changed much, this version of OpenNMS should be more stable and better performing than any version before it. We delayed the release by 10 days in order to document a lot of the changes. You can visit the new documentation here: http://www.opennms.org/wiki/Docu-overview and the full release notes can be found here: http://www.opennms.org/wiki/What%27s_New_in_OpenNMS_1.10 We hope you find it useful. -T * What's New in OpenNMS 1/10 * ** Architectural Changes *** IPv6 Support The OpenNMS core was completely refactored in 1.10 to deal with IP addresses in a consistent manner, including adding complete IPv6 support. You should now be able to use IPv6 addresses anywhere you would use IPv4 addresses in 1.8. Additionally, Provisiond can scan the newer IPv6-capable IP-MIB to detect IPv6 interfaces on provisioned nodes. IPv4 and IPv6 ICMP (ping) support can be configured in the "opennms.properties" file in $OPENNMS_HOME/etc. *** Database Schema Management Improvements The Liquibase database management introduced in 1.8 has been improved, and thanks to a newer Liquibase core, is much faster. *** XML Serialization Updates A number of configuration classes which used Castor for serializing configuration files have been updated to use JAXB instead, which gives us a lot more flexibility in how the configuration objects are dealt with. *** Web UI Infrastructure Updates A number of changes have happened in the Web UI core, including more GWT-based components, and removing our old Ext-JS-based UI elements. *** Logging Updates Logging has been cleaned up significantly in a number of places since 1.8, which should make it easier to debug problems. *** Love Each compile of OpenNMS 1.10.x contains 20% more love than 1.8. ** Updated Features *** Drools While there has previously been support for Drools for doing complex business logic based on OpenNMS events, it was non-functional in 1.8 because of some incompatibilities in a number of OpenNMS's dependencies. The Drools engine has been cleaned up and is working properly. An overview of using Drools in a modern OpenNMS install is available in the March 14th, 2011 TWiO (http://www.opennms.com/twio-drooling-all-over-your-network/) *** Major Reporting Engine Updates The Jasper reports introduced in OpenNMS 1.8 have gone through a number of significant updates, including adding support for report parameters, as well as retrieving RRD data in reports. *** Instrumentation Log Reader Updates The instrumentation log reader (used for evaluating collection performance) has been updated to include a web UI. It also supports a number of options for filtering and sorting collection times. *** Link Daemon Refactoring Linkd, the OpenNMS link daemon, has gone through a huge refactoring. While the existing Linkd in 1.8 worked for some people, there were a large number of use cases that should have worked that just plain failed. Linkd went through a lot of cleanup, and should work to detect links for a lot more devices, especially with force-ip-route-discovery-on-ethernet set to true. *** Provisiond Overhaul Provisiond has been through a ton of cleanups and fixes. Besides IPv6 support, a lot of corner cases in provisiond behavior have been resolved. Also, detectors have been implemented for every service that Capsd supports. *** Asset Management Asset management data has been expanded to include a number of new attributes, and the asset management UI has been updated. *** Syslogd Overhaul Syslogd has been refactored to improve performance and add support for better parsing of known formats including SyslogNG and RFC 5424 messages. See the comments in "syslogd-configuration.xml" for details. *** HTTP API Updates Our HTTP code has been updated to use Apache HTTP Components rather than the older HTTPClient API. In addition, we support relaxed standards for SSL certificates when making HTTPS connections. *** Data Collection Updates In addition to the configuration file changes, support for the new "PersistRegexSelectorStrategy" gives you more control over what data is persisted when doing data collection. And example would be the Net-SNMP configuration for disk IO, in "$OPENNMS_HOME/etc/datacollection/netsnmp.xml", which lets you ignore "ram" and loopback devices when persisting. ** Configuration File Updates *** Split Configuration Files A number of configuration files now support being split up into multiple files for ease of maintenance, to continue work done to the event configuration in 1.8: datacollection-config.xml snmp-graph.properties syslogd-configuration.xml *** Many Updates to Device Configuration Many new additions and fixes have been made to event configurations, data collection, thresholding, and more. ** New Features *** JNA-Based ICMP While ICMP (ping) still relies on some native code, we have added an alternate ICMP strategy which uses JNA. It supports both IPv4 and IPv6, and can be run straight from Java code without installing a corresponding native component. While it is not enabled by default (the JNI implementation of ping is still more performant), it can be used by remote pollers for doing ICMP availability. *** New Plugins and Monitors DNS resolution monitor, for testing V4 or V6 DNS resolution LDAPS plugin and monitor, for monitoring LDAP-over-SSL Selenium monitor, for doing complex scripted web site monitoring using Selenium ** ReST Service Additions A number of new ReST services have been added: /rest/stats/alarms - retrieve statistics on alarms (newest, oldest, acknowledged and unacknowleged) /rest/remotelocations - retrieve remote poller availability information /rest/sched-outages - retrieve scheduled outage information </pre> Tarus Balog 2012-02-13T16:15:17 The First OpenNMS Training Courses in 2012: USAand UK http://comments.gmane.org/gmane.network.opennms.announce/254 <pre>Gang: I am happy to announce that we have scheduled the first two training courses for the new year, and these will be the first ones taught on OpenNMS 1.10 (the latest major stable OpenNMS release). There is one week-long course being taught at our company headquarters in Pittsboro, NC, USA the week of 26 February, and another week-long course being held at the University of Southampton in Southampton, Hampshire, UK the week of 27 March. These courses are the fastest, most cost-efficient way to get up to speed on OpenNMS quickly and I hope to see you there. Space is limited, so please register early: http://www.opennms.com/training -T _______________________________________________________________________ Tarus BALOG, OpenNMS Maintainer Main: +1 919 533 0160 The OpenNMS Group, Inc. Fax: +1 773 345 3645 Email: tarus&lt; at &gt;opennms.org URL: http://www.opennms.org PGP Key Fingerprint: 8945 8521 9771 FEC9 5481 512B FECA 11D2 FD82 B45C ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ 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 </pre> Tarus Balog 2012-02-08T13:19:39 OpenNMS iOS Client Update http://comments.gmane.org/gmane.network.opennms.announce/253 <pre>Just wanted to send a quick note that the OpenNMS iOS client, version 1.0.4, was accepted to the app store and is now downloadable. Changes since 1.0.2: * add graphical representation of alarm state, for color-blind users * better handling of user configuration errors * works with self-signed certificates * better error messages on authentication issues * fix a bug where node display would be cached too long * add support for URL schemes to open the app The URL scheme change is especially handy, since it lets you open the iOS client to a particular page by clicking an onms:// URL from an email or SMS (or anywhere else, really). For details on this feature, see: http://www.opennms.org/wiki/iOS_Client#Using_URL_Schemes You can buy or update it from the iTunes Store: http://itunes.apple.com/app/opennms/id389479744?mt=8 </pre> Benjamin Reed 2012-02-01T23:29:59 New RPM and Debian Signing Keys http://comments.gmane.org/gmane.network.opennms.announce/252 <pre> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As you may or may not recall from previous messages, our package signing keys were technically OK, but because of re-signing to extend the expiration date, they were in a format that some tools (notably YUM) could not handle. Despite doing a bunch of work attempting to get the GPG key signature happy with all supported platforms, I've been unable to find a solution that works everywhere, so I've gone ahead and created a new signing key: pub 2048R/CE0FF0F0 2012-01-20 [expires: 2015-01-19] Key fingerprint = 1F94 B8B7 BA2D 26A6 206A 655C DC1A 1B59 CE0F F0F0 uid OpenNMS Signing Key 2012 &lt;opennms&lt; at &gt;opennms.org&gt; == Importing to GnuPG == You should be able to import it from the public keyservers: gpg --recv-keys CE0FF0F0 == Importing to APT == wget -O - http://debian.opennms.org/OPENNMS-GPG-KEY | sudo apt-key add - == Importing to RPM == rpm --import http://yum.opennms.org/OPENNMS-GPG-KEY ...once you have added the key to the relevant keyring(s), you should be able to continue normally. - -- Benjamin Reed The OpenNMS Group http://www.opennms.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFPGbj6Uu+jZtP2Zf4RAhjHAJ9jj7fss5v2perWHJH4f7OpB7AXpQCdFa1E 4JaeuXSbCDqADDusNDzNGE0= =Miay -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d_______________________________________________ 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</pre> Benjamin Reed 2012-01-20T18:56:58 YUM repository updates http://comments.gmane.org/gmane.network.opennms.announce/251 <pre> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We have been working on cleaning up our release and repository-management process. A bug was recently introduced in the scripts that update the YUM repository RPMs which could cause you to see errors like this: http://yum.opennms.org/common/common/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found Trying other mirror. Error: Cannot retrieve repository metadata (repomd.xml) for repository: opennms-common-common. Please verify its path and try again If you are experiencing this issue, it can be fixed by installing the latest repository RPM from http://yum.opennms.org/. For example, if you are running OpenNMS stable on RHEL5, you would browse to yum.opennms.org, look for "Stable", and download the RPM linked by the text, "RedHat Enterprise Linux 5.x and CentOS 5.x". Then install it, using: rpm -Uvh opennms-repo-stable-rhel5.noarch.rpm Sorry for the inconvenience. - -- Benjamin Reed The OpenNMS Group http://www.opennms.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFPDERhUu+jZtP2Zf4RAtocAKCPQUcgxaThFSKAUhiWTV1gwY8Y5ACgmAi4 hCzVBlP7JpkdU95gA7if37w= =9+b9 -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev_______________________________________________ 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</pre> Benjamin Reed 2012-01-10T14:00:01 OpenNMS Training in the US: 27 Feb - 2 Mar http://comments.gmane.org/gmane.network.opennms.announce/250 <pre>Gang: Just a quick note that we'll be hosting our week-long OpenNMS training in the US at the end of February: http://www.opennms.com/training/ We are hoping to have one in the UK in March - I'll let you know as soon as the dates are firm. -T _______________________________________________________________________ Tarus BALOG, OpenNMS Maintainer Main: +1 919 533 0160 The OpenNMS Group, Inc. Fax: +1 773 345 3645 Email: tarus&lt; at &gt;opennms.org URL: http://www.opennms.org PGP Key Fingerprint: 8945 8521 9771 FEC9 5481 512B FECA 11D2 FD82 B45C ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ 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 </pre> Tarus Balog 2012-01-04T15:41:59 OpenNMS Training in the US: 27 Feb - 2 Mar http://comments.gmane.org/gmane.network.opennms.announce/250 <pre>Gang: Just a quick note that we'll be hosting our week-long OpenNMS training in the US at the end of February: http://www.opennms.com/training/ We are hoping to have one in the UK in March - I'll let you know as soon as the dates are firm. -T _______________________________________________________________________ Tarus BALOG, OpenNMS Maintainer Main: +1 919 533 0160 The OpenNMS Group, Inc. Fax: +1 773 345 3645 Email: tarus&lt; at &gt;opennms.org URL: http://www.opennms.org PGP Key Fingerprint: 8945 8521 9771 FEC9 5481 512B FECA 11D2 FD82 B45C ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ 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 </pre> Tarus Balog 2012-01-04T15:41:59 Training in London, UK and Pittsboro, NC, USA http://comments.gmane.org/gmane.network.opennms.announce/249 <pre>Gang: We are happy to be able to announce that we are bringing our week long training course on OpenNMS back to the UK - this time in London. Thanks to the Girl Guiding Association we have a place to hold training in London, right near Buckingham Palace. The course will run from 28 November through 2 December: http://www.opennms.com/training The room is smaller than the one we had in Reading earlier in the year, so space is limited. In addition, the week after that we will be holding training at the OpenNMS HQ in Pittsboro, NC. We already have a number of students confirmed, so there are only four seats left. The next training probably will not be until March of 2012. Hope you can make it. -T </pre> Tarus Balog 2011-10-24T18:48:15 This Week in OpenNMS: Who Bugs the Reporters? http://comments.gmane.org/gmane.network.opennms.announce/248 <pre>It's time for These Weeks in OpenNMS. (See what I did there? &lt;g&gt;) In the last couple of weeks we fixed a lot more bugs in preparation for 1.10, and released 1.8.14 and 1.9.91. Seth also did a HUGE triage of the JIRA database, cleaning up a lot of duplicates, as well as un-closed issues that have actually been resolved in the past. Speaking of triaging the JIRA database, I'd like to re-post an article I wrote on my personal blog &lt;http://www.raccoonfink.com/blog/2011/08/23/schrodingers-bugs/&gt; about reporting issues. The TL;DR version is: don't be afraid to open an issue! Here it is in it's entirety: Schrödinger's Bugs Working on an open-source project &lt;http://www.opennms.org/&gt; teaches you a few things about dealing with software developers, and reporting bugs. I've been in the open-source world for a long time, and I remember when I first started out as a user of software, I felt glad to even have access to these tools at all, and I felt a reluctance to "bother" the developers with issues if I wasn't sure it was only me. The problem is, issues are a bit like Schrödinger's cat &lt;http://wikipedia.org/wiki/Schr%C3%B6dinger%27s_cat&gt;: they don't exist until the developer knows about them. Since I've become a developer of open-source software and seen things from the other side, I have one request: *err on the side of opening an issue*. There's nothing I love more than having an issue opened, and being able to /fix/ it, and tell the user their problem is solved. It's that kind of feedback loop that is one of the best parts of developing software without a marketing and sales department sitting between you and your users. So without further ado, I'd like to point out a few comments in this vein. Note that when I say "issue," it could be anything: a showstopper bug, an annoyance, or just a new feature you /wish/ the software had. *Always Open an Issue* Sure, sometimes it's a pain to figure out where the issue reporter link is, and create an account, and validate your email, and figure out what component it goes into... but don't worry about it. If you get it in the wrong place, /they'll/ know where it belongs and (hopefully) triage it. But if you /don't/ open that issue, they may never know it's a problem. *Don't Worry If It's a Duplicate* Of course, you should always try searching for your issue first, maybe someone else has reported it. Make a comment if someone has. But if you can't find it, don't worry that it might be a duplicate, go ahead and open that issue. As a developer, I'd rather close a million duplicates than to never know about the issue in the first place. *Don't Just Describe the Issue, Describe What You're Trying to Do* It may be that the issue you're trying to solve is meant to work a different way, or is part of another feature you haven't used yet, or has a workaround. Make sure when you describe the problem you're having, also describe what you want to accomplish. *A Closed Issue is Not an Ultimatum* This is a corollary to "describe what you're trying to do." Just because an issue is closed does not mean it is closed for discussion. Sometimes the developer doesn't realize what you're trying to actually do, or the original issue was described in a way that doesn't make it clear that the /real/ issue is elsewhere. For example, OpenNMS supports creating a "path outage," which describes how particular nodes are related. There was an issue opened that said if you created a path outage, it would be wiped out when using Provisiond. It was closed, saying that you create path outage relationships with the "parent-id" tag in the provisioning group file. What the issue did not say is that these manually-created path outages were created through the UI. So the /real/ issue is that the web UI path outage editor is not Provisiond-aware, and the issue should be reopened. *It's Better to Be Too Verbose than Not Enough* Configuration files, logs, output from `dmesg` or similar, anything you can add that makes it easier to diagnose the problem. It's a lot harder to fix a problem with a one-line error message than with 200 lines of context telling you what the software was doing just before the error. The more information you give, the more likely it is the developer will be able to figure out what's going on when the issue happened. Does this mean your issue will be resolved quickly? Not necessarily. Everyone has their own set of priorities, and their own time set aside for working on issues. I can say that a good issue report, with a lot of detail and a good description of what you're trying to accomplish, will get a lot more traction than a 1-line report saying "it doesn't work," and it will get a /heck of a lot/ more traction than no report at all. To paraphrase Wayne Gretzky &lt;http://thinkexist.com/quotation/you_miss-of_the_shots_you_never_take/227454.html&gt;, you miss fixing 100% of the issues you never report. ;) Project Updates * 1.8: Current Release is 1.8.14 (Red-breasted Nuthatch) 1.8.14 &lt;http://www.opennms.org/documentation/ReleaseNotesStable.html#opennms-1.8.14&gt; is the current stable release, tagged 13 Sep, 2011. For a complete list of changes and updates, see the "New and Noteworthy" page on the OpenNMS wiki &lt;http://www.opennms.org/wiki/New_and_Noteworthy#New_in_OpenNMS_1.8.14&gt;. As always, it is recommended that you back up your database before upgrading. * 1.9: Current release is 1.9.91 (Crumhorn) 1.9.91 is the current unstable release, tagged 14 Sep, 2011. This release is not yet recommended for production use, but for developers and users who want to try out the very latest features, or for test environments to evaluate upgrades to 1.10 when it is released. For a list of changes and updates, see the "New and Noteworthy" page on the OpenNMS wiki &lt;http://www.opennms.org/wiki/New_and_Noteworthy#New_in_OpenNMS_1.9.91&gt;. Upcoming Events OpenNMS training will be held in Fulda, Germany, September 26th through 30th, 2011. It is done in conjunction with our partner, NETHINKS &lt;http://www.nethinks.com/&gt;. You can register on their site, here &lt;http://www.nethinks.com/opennms-schulung&gt;. Issues Resolved Since the last TWiO, the following issues were resolved as "fixed": * [NMS-1322 &lt;http://issues.opennms.org/browse/NMS-1322&gt;] -- CAPSD loops infinitely on misbehaving ipAddrTable * [NMS-2052 &lt;http://issues.opennms.org/browse/NMS-2052&gt;] -- small patch to add regex filtering of eventparms * [NMS-2374 &lt;http://issues.opennms.org/browse/NMS-2374&gt;] -- When running the database checker rethrow any exceptions with details (e.g.: database URL) * [NMS-2375 &lt;http://issues.opennms.org/browse/NMS-2375&gt;] -- Make the severity element in event configuration an enumeration and fix our default config files * [NMS-2738 &lt;http://issues.opennms.org/browse/NMS-2738&gt;] -- Include a failure reason in data collection failure events * [NMS-2812 &lt;http://issues.opennms.org/browse/NMS-2812&gt;] -- normalize radius code * [NMS-2822 &lt;http://issues.opennms.org/browse/NMS-2822&gt;] -- PSQLException when discovering interface/address that has not yet been deleted from database * [NMS-2889 &lt;http://issues.opennms.org/browse/NMS-2889&gt;] -- Move org.opennms.netmgt.ping.Ping and its dependencies into jicmp package * [NMS-2907 &lt;http://issues.opennms.org/browse/NMS-2907&gt;] -- More reduction keys for APC events * [NMS-2977 &lt;http://issues.opennms.org/browse/NMS-2977&gt;] -- Deleted node appear in KSC report creation * [NMS-3005 &lt;http://issues.opennms.org/browse/NMS-3005&gt;] -- ONMS Version not display correct -- Windows install * [NMS-3066 &lt;http://issues.opennms.org/browse/NMS-3066&gt;] -- JavaMailNotificationStrategy fails when passing -nm * [NMS-3073 &lt;http://issues.opennms.org/browse/NMS-3073&gt;] -- Weird redirect on login * [NMS-3143 &lt;http://issues.opennms.org/browse/NMS-3143&gt;] -- GUI error if we remove Switches from Surveillance * [NMS-3194 &lt;http://issues.opennms.org/browse/NMS-3194&gt;] -- Reporting is truncated by URL length limitation * [NMS-3319 &lt;http://issues.opennms.org/browse/NMS-3319&gt;] -- HTTPS don't support SSLv3-only servers * [NMS-3515 &lt;http://issues.opennms.org/browse/NMS-3515&gt;] -- Broken paged grid in Select SNMP Interfaces * [NMS-3540 &lt;http://issues.opennms.org/browse/NMS-3540&gt;] -- General node information not displayed using Internet Explorer 8 in IE7 Compatability view or IE7 * [NMS-3594 &lt;http://issues.opennms.org/browse/NMS-3594&gt;] -- provisiond does not create nodelabelchanged event * [NMS-3606 &lt;http://issues.opennms.org/browse/NMS-3606&gt;] -- WMI/WQL Poller -- Wrong text in event * [NMS-3622 &lt;http://issues.opennms.org/browse/NMS-3622&gt;] -- Allow HttpCollector and PageSequenceMonitor to accept all SSL certificates * [NMS-3651 &lt;http://issues.opennms.org/browse/NMS-3651&gt;] -- Create detectors for all protocol plugins * [NMS-3785 &lt;http://issues.opennms.org/browse/NMS-3785&gt;] -- Provisiond crashes against Procurve 1810G * [NMS-3823 &lt;http://issues.opennms.org/browse/NMS-3823&gt;] -- Clicking a Vlan interface (SVI) on a Cisco router throws Jasper Exception * [NMS-3848 &lt;http://issues.opennms.org/browse/NMS-3848&gt;] -- Reasons Missing From nodeLostService events * [NMS-3863 &lt;http://issues.opennms.org/browse/NMS-3863&gt;] -- provisiond has issues with two IPs on the same ifIndex -- I think * [NMS-3887 &lt;http://issues.opennms.org/browse/NMS-3887&gt;] -- webUI shows 100% availability although service is not monitored * [NMS-3912 &lt;http://issues.opennms.org/browse/NMS-3912&gt;] -- Alarm Description in Dashboard not formatted * [NMS-3959 &lt;http://issues.opennms.org/browse/NMS-3959&gt;] -- eventd logging missing file name * [NMS-3979 &lt;http://issues.opennms.org/browse/NMS-3979&gt;] -- Notification Dashlet doesn't format HTML message text * [NMS-4020 &lt;http://issues.opennms.org/browse/NMS-4020&gt;] -- Too many CLOSE_WAIT on port 5817 * [NMS-4029 &lt;http://issues.opennms.org/browse/NMS-4029&gt;] -- dns provisiond -- fqdn trailing dot * [NMS-4040 &lt;http://issues.opennms.org/browse/NMS-4040&gt;] -- SNMPPoller is the cause of loss of snmpinterfaces during the re-import / synchronization Provision Groups. * [NMS-4049 &lt;http://issues.opennms.org/browse/NMS-4049&gt;] -- Can't provision a node with one IP address and a policy to avoid all IP address * [NMS-4091 &lt;http://issues.opennms.org/browse/NMS-4091&gt;] -- Page Sequence Monitor and invalid SSL certificates * [NMS-4157 &lt;http://issues.opennms.org/browse/NMS-4157&gt;] -- org.apache.mina.util.DefaultExceptionMonitor: Unexpected exception * [NMS-4232 &lt;http://issues.opennms.org/browse/NMS-4232&gt;] -- Configure scheduling outages via RESTful Web Service * [NMS-4390 &lt;http://issues.opennms.org/browse/NMS-4390&gt;] -- Nearly impossible to make head or tail of why Maven build is failing. * [NMS-4475 &lt;http://issues.opennms.org/browse/NMS-4475&gt;] -- Provisiond fails with a Unable to return specified BeanFactory instance exception at startup * [NMS-4502 &lt;http://issues.opennms.org/browse/NMS-4502&gt;] -- [patch] Show correct values in net-snmp CPU Usage graph * [NMS-4526 &lt;http://issues.opennms.org/browse/NMS-4526&gt;] -- Remote Poller implodes with lack of WMI classes * [NMS-4544 &lt;http://issues.opennms.org/browse/NMS-4544&gt;] -- Provisiond HOST-RESOURCES process detector * [NMS-4593 &lt;http://issues.opennms.org/browse/NMS-4593&gt;] -- Report Issue -- Surveillance Category Not Correctly Chosen * [NMS-4673 &lt;http://issues.opennms.org/browse/NMS-4673&gt;] -- Discovery fails with JNA pinger * [NMS-4675 &lt;http://issues.opennms.org/browse/NMS-4675&gt;] -- Resource Graph Resources -- limited to 55 Resources or less * [NMS-4683 &lt;http://issues.opennms.org/browse/NMS-4683&gt;] -- SNMP interface poller filtering not allowing data collection after provisioning group sync * [NMS-4704 &lt;http://issues.opennms.org/browse/NMS-4704&gt;] -- Service monitored with 100% availability instead of Not Monitored * [NMS-4749 &lt;http://issues.opennms.org/browse/NMS-4749&gt;] -- Requisition REST Service allows duplicate nodes * [NMS-4754 &lt;http://issues.opennms.org/browse/NMS-4754&gt;] -- Event analysis report, missing legend in pie graph * [NMS-4799 &lt;http://issues.opennms.org/browse/NMS-4799&gt;] -- Events generated from trapd are not associated with any node * [NMS-4800 &lt;http://issues.opennms.org/browse/NMS-4800&gt;] -- Node.jsp -- double clicking physical interfaces goes to interface.jsp instead of snmpinterface.jsp * [NMS-4815 &lt;http://issues.opennms.org/browse/NMS-4815&gt;] -- Make Jetty headerBufferSize property configurable * [NMS-4817 &lt;http://issues.opennms.org/browse/NMS-4817&gt;] -- Null (\0) characters in logmsg field of events causes org.postgresql.util.PSQLException: ERROR: invalid byte sequence for encoding "UTF8?: 0×00 * [NMS-4831 &lt;http://issues.opennms.org/browse/NMS-4831&gt;] -- notifd.log -- Info if message was send * [NMS-4833 &lt;http://issues.opennms.org/browse/NMS-4833&gt;] -- Poorly used INFO log message * [NMS-4834 &lt;http://issues.opennms.org/browse/NMS-4834&gt;] -- Remote Poller state changes from Paused to Running * [NMS-4838 &lt;http://issues.opennms.org/browse/NMS-4838&gt;] -- jmx collector does direct db lookup of nodeid * [NMS-4839 &lt;http://issues.opennms.org/browse/NMS-4839&gt;] -- Check if a node is currently covered by a scheduled outage using Rest * [NMS-4841 &lt;http://issues.opennms.org/browse/NMS-4841&gt;] -- OpenNMS Version not displayed correctly * [NMS-4845 &lt;http://issues.opennms.org/browse/NMS-4845&gt;] -- RrdUtils.createRRD log message is unclear * [NMS-4851 &lt;http://issues.opennms.org/browse/NMS-4851&gt;] -- Notification not being sent event if status="on", looks like notifd is not using the status in the config file properly * [NMS-4853 &lt;http://issues.opennms.org/browse/NMS-4853&gt;] -- unit tests on windows creates directories outside of temp directory * [NMS-4857 &lt;http://issues.opennms.org/browse/NMS-4857&gt;] -- StorageStrategy documentation does not match API in code * [NMS-4861 &lt;http://issues.opennms.org/browse/NMS-4861&gt;] -- Runaway threads consuming CPU when rendering certain graphs * [NMS-4871 &lt;http://issues.opennms.org/browse/NMS-4871&gt;] -- With Jetty + HTTPS, certain Web UI actions prompt browser to "Save As" JSP and HTML files * [NMS-4872 &lt;http://issues.opennms.org/browse/NMS-4872&gt;] -- Show all nodes with asset info not working * [NMS-4880 &lt;http://issues.opennms.org/browse/NMS-4880&gt;] -- java.lang.ClassCastException when building an event notification with a category filter * [NMS-4882 &lt;http://issues.opennms.org/browse/NMS-4882&gt;] -- IP address formatting does not match * [NMS-4886 &lt;http://issues.opennms.org/browse/NMS-4886&gt;] -- HttpCollector ignores "port" parameter from Collectd config * [NMS-4895 &lt;http://issues.opennms.org/browse/NMS-4895&gt;] -- 1.9.90 newer graphics display inconsistency -- node.jsp * [NMS-4899 &lt;http://issues.opennms.org/browse/NMS-4899&gt;] -- notifd DEBUG message "supress" mispelling * [NMS-4903 &lt;http://issues.opennms.org/browse/NMS-4903&gt;] -- base-url not used when viewing resource graphs * [NMS-4913 &lt;http://issues.opennms.org/browse/NMS-4913&gt;] -- Change StorageStrategy to throw an IllegalArgumentException when the arguments (or parameters) are not properly configured on datacollection-config.xml * [NMS-4914 &lt;http://issues.opennms.org/browse/NMS-4914&gt;] -- wrong implementation of org.opennms.netmgt.correlation.Correlator$EngineAdapter.getName() ? * [NMS-4917 &lt;http://issues.opennms.org/browse/NMS-4917&gt;] -- update ksc page * [NMS-4921 &lt;http://issues.opennms.org/browse/NMS-4921&gt;] -- after upgrade to 1.8.13 RadiusAuthMonitor gives exception "The RADIUS Server returned the wrong Identifier" * [NMS-4923 &lt;http://issues.opennms.org/browse/NMS-4923&gt;] -- Add PostgreSQL 9.1 support * [NMS-4926 &lt;http://issues.opennms.org/browse/NMS-4926&gt;] -- OpenNMS 1.8.14-1 fails to install on Ubuntu Server 10.04.3 LTS , reason opennms-db depends on iplike-pgsql91 which is not available at debian.opennms.org * [NMS-4931 &lt;http://issues.opennms.org/browse/NMS-4931&gt;] -- Availability Miscalculated in NodeAvailabilityReport.jrxml (and others) 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 &lt;mailto:ranger&lt; at &gt;opennms.com&gt;. </pre> Benjamin Reed 2011-09-19T16:24:02 Yum Repository Repaired for Fedora 15 and RHEL/CentOS/Scientific Linux 6 http://comments.gmane.org/gmane.network.opennms.announce/247 <pre> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There is a bug in the way yum handles PGP keys that cause OpenNMS installation through yum to fail on Fedora 15 and RHEL6 (and it's derivatives). The key we've been using to sign our RPMs contained multiple old self-signatures, which were created as part of extending the expiration of our PGP keys over the years. The key has now been updated to clean out the old expired signatures, but if yum has already imported the older version of the key, you will continue to see this error: Invalid GPG Key from http://yum.opennms.org/OPENNMS-GPG-KEY: first PGP packet should be a public-key packet, not signature packet To fix it, you will need to re-import the key. To do so, run: rpm --import http://yum.opennms.org/OPENNMS-GPG-KEY ...and yum will work as expected when installing OpenNMS packages. - -- Benjamin Reed The OpenNMS Group http://www.opennms.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFOcACTUu+jZtP2Zf4RAq7WAJ9THZja0o7vfyAoVKNFuGAXPyxCggCggEs0 luYocc/0v5TgxjgBvvVja8s= =wDbu -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Using storage to extend the benefits of virtualization and iSCSI Virtualization increases hardware utilization and delivers a new level of agility. Learn what those decisions are and how to modernize your storage and backup environments for virtualization. http://www.accelacomm.com/jaw/sfnl/114/51434361/ _______________________________________________ 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 </pre> Benjamin Reed 2011-09-14T01:17:14 Towerstream and OpenNMS http://comments.gmane.org/gmane.network.opennms.announce/246 <pre>One of our clients, Towerstream, a large ISP in New England providing 4G wireless services, was kind enough to share some of their experiences using OpenNMS and working with the OpenNMS Group. If you are interested in such things, check out their story on our website: http://www.opennms.com/towerstream/ -T _______________________________________________________________________ Tarus BALOG, OpenNMS Maintainer Main: +1 919 533 0160 The OpenNMS Group, Inc. Fax: +1 773 345 3645 Email: tarus&lt; at &gt;opennms.org URL: http://www.opennms.org PGP Key Fingerprint: 8945 8521 9771 FEC9 5481 512B FECA 11D2 FD82 B45C ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ 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 </pre> Tarus Balog 2011-08-30T11:41:19 This Week in OpenNMS: Release Candidate WantsYour Votes! http://comments.gmane.org/gmane.network.opennms.announce/245 <pre>It's time for This Week in OpenNMS. In the last couple of weeks we worked on smoke tests, fixed more bugs, and released 1.8.13 and 1.9.90. New Releases It's been a bit since we last did a release, we pretty much put all releases on hold until we could put a 1.10 release candidate out. That said, we found a couple of reasonably important bugs (in both 1.8.x and 1.9.x) and decided it was time to take the plunge. 1.9.90 is the first release candidate for the 1.10 series, meaning that we are feature-complete and plan only on fixing important bugs before 1.10.0 gets released. That said, Linkd should be still considered beta for this release. It's gone through a significant refactor, but still has not reached parity with 1.6 (or even 1.8) Linkd. We will not release 1.10.0 until we have that parity, but for now, if you're relying on Linkd, stick with 1.8. If you have the ability to help us test the new Linkd code against your devices, bug reports would be helpful, however. Podcast Jeff has been planning on making an OpenNMS podcast for a while now, but Dev-Jam was the perfect opportunity to get a few folks on the mic and talk about the state of OpenNMS and what happened during Dev-Jam. If you subscribe to the Planet OpenNMS &lt;http://planet.opennms.org/&gt; RSS feed, then you've already seen this, but if not, please check it out! * OpenNMS Audiocast (MP3) &lt;http://feeds.feedburner.com/NMSCast-mp3&gt; * OpenNMS Audiocast (Ogg Vorbis) &lt;http://feeds.feedburner.com/NMSCast-ogg&gt; Project Updates * 1.8: Current Release is 1.8.13 (Northern Lapwing) 1.8.13 &lt;http://www.opennms.org/documentation/ReleaseNotesStable.html#opennms-1.8.13&gt; is the current stable release, tagged 10 Aug, 2011. For a complete list of changes and updates, see the "New and Noteworthy" page on the OpenNMS wiki &lt;http://www.opennms.org/wiki/New_and_Noteworthy#New_in_OpenNMS_1.8.13&gt;. As always, it is recommended that you back up your database before upgrading. * 1.9: Current release is 1.9.90 (Balafon) 1.9.90 is the current unstable release, tagged 10 Aug, 2011. This release is not recommended for production use, but for developers and users who want to try out the very latest features, or for test environments to evaluate upgrades to 1.10 when it is released. For a list of changes and updates, see the "New and Noteworthy" page on the OpenNMS wiki &lt;http://www.opennms.org/wiki/New_and_Noteworthy#New_in_OpenNMS_1.9.10&gt;. Issues Resolved * [JICMP-4 &lt;http://issues.opennms.org/browse/JICMP-4&gt;] -- jicmp IcmpSocket.h byte swapping macros don't work on OpenIndiana * [JRD-7 &lt;http://issues.opennms.org/browse/JRD-7&gt;] -- JRRD Report runs fine in iReport but has errors when running via Reportd * [NMS-696 &lt;http://issues.opennms.org/browse/NMS-696&gt;] -- Availability report time periods * [NMS-1769 &lt;http://issues.opennms.org/browse/NMS-1769&gt;] -- columnName argument to AssetModel.searchAssets allows SQL injection * [NMS-1802 &lt;http://issues.opennms.org/browse/NMS-1802&gt;] -- HTTP monitor nits * [NMS-1865 &lt;http://issues.opennms.org/browse/NMS-1865&gt;] -- The installer should catch systems where TCP connections cannot be made to localhost * [NMS-2079 &lt;http://issues.opennms.org/browse/NMS-2079&gt;] -- Opennms not honoring changes in opennms.conf * [NMS-2893 &lt;http://issues.opennms.org/browse/NMS-2893&gt;] -- Node when deleted remains in performance report list * [NMS-2995 &lt;http://issues.opennms.org/browse/NMS-2995&gt;] -- Trapd is not able to process SNMPv3 traps * [NMS-3651 &lt;http://issues.opennms.org/browse/NMS-3651&gt;] -- Create detectors for all protocol plugins * [NMS-3771 &lt;http://issues.opennms.org/browse/NMS-3771&gt;] -- reportd missing ability to select mailer from javamail-configuration.xml * [NMS-3905 &lt;http://issues.opennms.org/browse/NMS-3905&gt;] -- reload of Threshold configuration does not work -- only after restart OpenNMS new threshold are applied * [NMS-4038 &lt;http://issues.opennms.org/browse/NMS-4038&gt;] -- translated events are displayed like the original event * [NMS-4350 &lt;http://issues.opennms.org/browse/NMS-4350&gt;] -- spring/beanfactory issue Java 1.7.0 -- pointcut issues * [NMS-4668 &lt;http://issues.opennms.org/browse/NMS-4668&gt;] -- Create a poller monitor to "proxy" pings via the CISCO-PING-MIB * [NMS-4725 &lt;http://issues.opennms.org/browse/NMS-4725&gt;] -- LDAP authorization fails -- group to role mapping does not work * [NMS-4745 &lt;http://issues.opennms.org/browse/NMS-4745&gt;] -- java.net.SocketException: Too many open files * [NMS-4817 &lt;http://issues.opennms.org/browse/NMS-4817&gt;] -- Null (\0) characters in logmsg field of events causes org.postgresql.util.PSQLException: ERROR: invalid byte sequence for encoding "UTF8?: 0×00 * [NMS-4862 &lt;http://issues.opennms.org/browse/NMS-4862&gt;] -- Add command option to NRPE in provisiond * [NMS-4873 &lt;http://issues.opennms.org/browse/NMS-4873&gt;] -- Upgrade bug when Linkd tables contain data * [NMS-4875 &lt;http://issues.opennms.org/browse/NMS-4875&gt;] -- Older builds ov OpenNMS are not available for download * [NMS-4877 &lt;http://issues.opennms.org/browse/NMS-4877&gt;] -- Typo in datacollection-config.xml 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 &lt;mailto:ranger&lt; at &gt;opennms.com&gt;. </pre> Benjamin Reed 2011-08-22T20:33:22 OpenNMS Training in the USA and Europe http://comments.gmane.org/gmane.network.opennms.announce/244 <pre>Gang: Just a reminder that we have two training courses scheduled in September. The first course will be held at OpenNMS HQ in North Carolina the week of 12 September: http://www.opennms.com/training/ The second course will be held in Europe, specifically Fulda, Germany, which was the site of our Users Conference back in May. This is done in conjunction with our partner, NETHINKS. While the registration page is in German, the course will be taught by me and David Hustace in English: www.nethinks.com/opennms-schulung Hope to see you there. -T _______________________________________________________________________ Tarus Balog, OpenNMS Maintainer Main: +1 919 533 0160 The OpenNMS Group, Inc. Fax: +1 773 345 3645 Email: tarus&lt; at &gt;opennms.org URL: http://www.opennms.org PGP Key Fingerprint: 8945 8521 9771 FEC9 5481 512B FECA 11D2 FD82 B45C ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ 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 </pre> Tarus Balog 2011-08-15T13:08:54 This Week in OpenNMS: Testing and Bugging (Not Necessarily in That Order) http://comments.gmane.org/gmane.network.opennms.announce/243 <pre>It's time again for This Week in OpenNMS. In the last week we did some testing and bugfixing in preparation for 1.10. IPv6 Testing I spent the first half of the week testing IPv6, making sure that the packaging is ready and that you can have a system with only an IPv4 or IPv6 stack (but not both) and have everything still come up correctly. Also, if you need to enforce the availability (or not) of either stack, some options have been added to $OPENNMS_HOME/etc/opennms.properties to take care of that. |# By default, OpenNMS will start up if either ICMPv4 *or* ICMPv6 are # available and initialize properly. If you wish to force IPv4 or IPv6 # explicitly, set one or both of these properties. # #org.opennms.netmgt.icmp.requireV4=true #org.opennms.netmgt.icmp.requireV6=true| Smoke Tests We've had pretty good unit test coverage in general, but we've been lacking a few things, namely, UI testing, and a "smoke test" which makes sure that OpenNMS snapshots come up properly, don't have nasty exceptions, and other similar things. Our intern Philip was back this summer helping us out with a few things, and he's been working on the smoke test infrastructure for the last few weeks. I spent a bit of time putting together scripts on the server side to let us bring up a snapshot and run the smoke tests against it, from Bamboo. As of this week, the smoke tests &lt;http://bamboo.internal.opennms.com:8085/browse/OPENNMS-SMOKE&gt; are not only running, but green. (Yay!) Tomorrow is Philip's last day, and we've heard he's going to try again to beat the Andy's Big-A Challenge &lt;http://www.andysburgers.net/big-a-challenge&gt; again this year. Last year, it didn't work out so well. I swear, this is not a hazing thing, he volunteered. Anyways, wish him luck. ;) Other Code Cleanups Alejandro is wrapping up making sure that there is a Provisiond detector for everything that has a Capsd plugin. Seth and I have both been working on cleaning up miscellaneous bugs and other stuff in preparation for 1.10. Donald has finished moving all of our Ext-JS &lt;http://www.sencha.com/&gt; code to use GWT &lt;http://code.google.com/webtoolkit/&gt; instead, which has given us a number of spiffy controls. I also spent some time profiling OpenNMS, and cleaning up some easy-to-fix-stuff, including working on moving the data collection configuration parsing to JAXB and changing that code to optimize usage of string data some. Data collection should use less memory now, and be a little faster. Project Updates * 1.8: Current Release is 1.8.12 (Black-capped Petrel) 1.8.12 &lt;http://www.opennms.org/documentation/ReleaseNotesStable.html#opennms-1.8.12&gt; is the current stable release, tagged 10 May, 2011. For a complete list of changes and updates, see the "New and Noteworthy" page on the OpenNMS wiki &lt;http://www.opennms.org/wiki/New_and_Noteworthy#New_in_OpenNMS_1.8.12&gt;. As always, it is recommended that you back up your database before upgrading. * 1.9: Current release is 1.9.8 (Pulalu) 1.9.8 is the current unstable release, tagged 10 May, 2011. This release is not recommended for production use, but for developers and users who want to try out the very latest features. For a list of changes and updates, see the "New and Noteworthy" page on the OpenNMS wiki &lt;http://www.opennms.org/wiki/New_and_Noteworthy#New_in_OpenNMS_1.9.8&gt;. Issues Resolved * [NMS-1121 &lt;http://issues.opennms.org/browse/NMS-1121&gt;] -- threshd.log shows wrong nodeId in certain circumstances * [NMS-1174 &lt;http://issues.opennms.org/browse/NMS-1174&gt;] -- SNMP collection on NAT'd interfaces produces ifIndex of -100 * [NMS-1316 &lt;http://issues.opennms.org/browse/NMS-1316&gt;] -- service not being marked up after interfaceUp event. * [NMS-4038 &lt;http://issues.opennms.org/browse/NMS-4038&gt;] -- translated events are displayed like the original event * [NMS-4856 &lt;http://issues.opennms.org/browse/NMS-4856&gt;] -- MSExchangeDetectorClient is too verbose on exceptions * [NMS-4859 &lt;http://issues.opennms.org/browse/NMS-4859&gt;] -- OpenNMS doesn't start 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 &lt;mailto:ranger&lt; at &gt;opennms.com&gt;. </pre> Benjamin Reed 2011-08-08T21:58:43 Search Engine Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.network.opennms.announce