OpenNMS 1.2.7 Released

Tarus Balog <[email protected]>
Newsgroups gmane.network.opennms.announce
Message-ID <8679F8F3-8D68-4255-B04E-6E03D86A94CE__33971.8011011884$1141052670$gmane$org@opennms.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gang:

I am proud to announce the availability of OpenNMS 1.2.7.

OpenNMS 1.2.7 contains a number of new features and bug fixes. This  
is a release in the "stable" or production OpenNMS tree.

This release replaces 1.2.6. Some issues were discovered early in  
deployment concerning the new SNMPv1 and SNMPv2 configuration  
functionality that required code changes.

The biggest new feature is the ability to better manage the SNMP  
service by  separating it into SNMPv1 and SNMPv2 services. This was  
added in preparation for the SNNPv3 support coming in the next major  
release this summer.

In addition to the SNMP changes, we fixed a bug with SNMP data  
collection. If you are "select"ing from which interfaces to collect  
data, and the interface had an IP address that wasn't the primary  
SNMP interface address, the collection would be set back to "N" in  
some cases.

If you are using the JDBC monitor to test databases, there is a new  
JDBCStoredProcedure monitor that you can configure to run a stored  
procedure to better test how well the database is working.

There is a new look to the Availability Reports. Instead of the "bar  
graph" you can choose to use a "calendar" view. This has been in the  
development branch for some time, but it was fairly easy to port to  
production so we went ahead and did it.

There are some cosmetic improvements as well. The default stylesheet  
has been changed and the default colors for the default SNMP reports  
have also been moved to, what many think, is a nicer look. The old  
stylesheet and snmp-graph.properties file is available should you  
prefer OpenNMS "classic".

There are some modest WebUI speed enhancements. The "List Nodes" page  
now just returns nodes vs. nodes and interfaces, and the "Configure  
SNMP Data Collection per Interface" from a node's admin page should  
also be much faster.

We have a new Wiki as well at http://www.opennms.org. The official  
documentation can be found on this page:

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

The next stable release, 1.2.8, is scheduled for March 28th. It will  
(we hope) be the last release in the 1.2 branch, as we focus all of  
our efforts on getting the 1.3 branch in shape for a 1.4 release. It  
will include Tomcat5 support and a few bug fixes.

As always, remember that commercial support and services are  
available for OpenNMS from The OpenNMS Group (http:// 
www.opennms.com). We have been seeing some Wishlist activity as well,  
thanks for that (http://www.opennms.org/index.php/WishList).

If you use and enjoy OpenNMS, please consider sending us a postcard  
for the amazing Wall o' Cards (http://www.opennms.org/index.php/ 
WallOfCards).

- -T


- -----

Tarus Balog
The OpenNMS Group, Inc.
Main  : +1 919 545 2553   Fax:   +1 503-961-7746
Direct: +1 919 647 4749   Skype: tarusb
Key Fingerprint: 8945 8521 9771 FEC9 5481  512B FECA 11D2 FD82 B45C

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFEAxOd/soR0v2CtFwRAlT0AJ0Wk9uq8psNIjeJ4RuRaJ5wEEuz8wCfQkF/
lR3JDZqQxmLWyyDtzhrIirk=
=hPGR
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
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.