Re: [opennms-discuss] OpenNMS 1.3.7 Released

"Fred Skrotzki" <[email protected]>
Newsgroups gmane.network.opennms.announce
Message-ID <C724F72B8D424748A91EC1FF4782A8741C7294__5962.40441450409$1189869593$gmane$org@mail1.textwise.com>
SO SWEET....

We've been running smokeping as a separate tool along with OpenNMS for
two years as it provides great diagnostic information on path
performance and packet loss when we start having issues.  We are so glad
it has become integrated now I have one set of screens to login to and
use.  A feature request I asked for with smokeping about two months ago
was to see if it is possible to somehow integrate mtr functionality so
that when loss occurs (repeated loss mostly) we can locate where in a
path the issue might be.

The removal of tomcat is also a nice move. 

Great work..

I'm off to wipe out and rebuild our internal monitoring system and test
it all out.  Assuming things are good we'll be rolling it out to our
production system in 7 days.

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
Tarus Balog
Sent: Friday, September 14, 2007 1:27 PM
To: [email protected]
Cc: General OpenNMS Discussion
Subject: [opennms-discuss] OpenNMS 1.3.7 Released

Gang:

OpenNMS 1.3.7 has been released.

Performance is an order of magnitude better than 1.3.6. We've also added
a new monitor called StrafePing. This is a port of Tobi Oeticker's
Smokeping application which provides a graphical view of ICMP latency by
sending out 20 pings every 5 minutes and measuring the time it takes to
return. The median value is graphed and the deviations show up as grey
"smoke". This monitor is also useful if you would like to get alerted
when an interface starts dropping packets. It can be configured to be
marked as "down" when less than 20 packets are returned.

Check out: http://www.opennms.org/index.php/StrafePing

We have also become a silver sponsor on Tobi's Smokeping page in
recognition of his work.

http://oss.oetiker.ch/smokeping/sponsors.en.html

We also removed the need for tomcat, so no more struggling with that app
(unless you want to, as it is still supported). OpenNMS comes bundled
with the jetty servlet container. It runs on port 8980 instead of 8080,
so be aware of that.

In addition to our CentricCRM Trouble Ticketing plugin:

http://www.opennms.org/index.php/CentricCRM_Trouble_Ticket_Plugin

there is now one for Jira:

http://www.opennms.org/index.php/Jira_Trouble_Ticket_Plugin

In order to make upgrades easier, there are yum and apt based
repositories to make it easier to stay up to date.

See: http://www.opennms.org/index.php/QuickStart

Note: if you are still on 1.2.9 this is still not the time to upgrade,
although we are getting close.

We had been planning on calling the next stable release OpenNMS 2.0.  
The 2.0 release is very important to us, and it involves not only new
code but better documentation, more power in the GUI, and greater ease
in distribution. But there is so much good stuff in the 1.3 branch we
didn't want to wait until 2.0 is complete to release another stable, so
we have come up with the following plan:

1.3.7 - released today. This represents a very stable development
release.

1.3.8 - End of October. This will be the feature complete candidate for
the next stable release. This will also include the work that was
started at our Developer's Conference, Dev-Jam, back in August.

1.7.90 - End of November. Rather than go to 2.0, we're going to 1.8.  
This is the release candidate, and should contain bug fixes for 1.3.8
but no or few new features.

1.8.0 - End of December. This will be the next production release, and
we hope to offer it to you as a holiday present for the end of a very
successful 2007.

As usual, I hope you enjoy OpenNMS. If you need commercial support for
it, please check out the OpenNMS Group homepage:

http://www.opennms.com

or if you a just feeling generous, there's the Amazon wishlist:

http://www.opennms.org/index.php/WishList

and as always we love getting postcards:

http://www.opennms.org/index.php/WallOfCards

-T

_______________________________________________________________________
Tarus Balog, OpenNMS Maintainer             Main:   +1 919 533 0160
The OpenNMS Group, Inc.                     Fax:    +1 503 961 7746
Skype: tarusb                               Direct: +1 919 647 4749
Email: [email protected]                    URL: http://www.opennms.org
PGP Key Fingerprint: 8945 8521 9771 FEC9 5481  512B FECA 11D2 FD82 B45C



------------------------------------------------------------------------
-
This SF.net email is sponsored by: Microsoft Defy all challenges.
Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

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

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.