OpenNMS 1.6.0 (Stable) Released似乎每年的10月以后我就会进入一个超级繁忙的状态，很长时间没有更新blog了，今天姑且转载一个OpenNMS的发布说明吧。
OpenNMS, the world's first enterprise-grade network management platform developed as 100% free and open software, has released version 1.6.0. This is a stable, production release that incorporates nearly three years of development.
以上算是OpenNMS的广告语大家看看就是，需要注意的是一个企业级的产品实施费用是从很低的门槛一直到企业级的花费的。和其他的企业级解决方案的实施没有区别，差异在于，一个不同的许可证类型，此为开源许可证是也。
The last production version, 1.2.0, was aimed to compete squarely with Hewlett-Packard's OpenView Network Node Manager product. This release builds upon that work to expand the reach of OpenNMS to other parts of the OpenView family as well as to provide an open source alternative to products such as Tivoli's Netcool.
以上是OpenNMS的精神所在：OpenNMS一直在叫嚣这和OpenView, NetCool较量；这足以说明了它的勇气，和发展方向，它的创始人Tarus从一个人单枪匹马开始，到现在有一般人inhouse开发这个产品，自己全世界出差，如果说没有实现和商业产品的抗衡的话，我个人觉得他起码实现了一个所有开源参与者的梦想“为需要自己的人工作，为自己工作”
OpenNMS 1.6.0 sports a redesigned user interface, a number of scalability improvements and increased integration with other products. OpenNMS now runs on Windows, in addition to most flavors of Linux, Solaris and Mac OS X.
上面说的是新版的用户界面重新设计了，目前我还没有时间安装，回头装好了一定上图片，新版的稳定性得到提高并增加了和其他产品的集成。现在OpenNMS也能在Windows上运行了，在我看这是早晚的是，它是个纯Java的应用，移植不是什么难事，不过我不推荐在windows上完开源的产品，有点不伦不类的感觉，而且从原生态的Linux环境中才哪呢个够获取开源的全部优势。
One of the major additions to the platform is the Alarms subsystem. OpenNMS can receive events from a number of sources, such as SNMP traps, syslog, TL/1, and custom scripts. A key can be configured for each event that will allow it to be turned into an alarm. Thus if a device is generating multiple, identical events, their number will be reduced into just a single alarm. This greatly reduces the amount of event "noise" that operators see.
上面说告警子系统现在是增强了。OpenNMS能收到像是snmp trap，syslog， TL/1和自定义脚本发来的告警事件。某种键值能被设置，让一个事件能被出发成一个警报。报警事件经过了压制和降噪处理，较少了重复报的数量。
In addition, automated actions can be performed on alarms. For example, events that signal problem resolution, or "up" alarms, can be matched with "down" alarms to automatically clear them. Event workflow can be built into the system by using these automations to manage the alarm list, thus freeing up the operators to focus on the most important issues.
另外，对于一个警报来说，可以和一个自动化的动作配合，例如某些up事件能去清除对应的down事件。
While OpenNMS contains a robust automated discovery system, when managing tens of thousands of nodes it is often preferred to allow an external system to determine what OpenNMS is to monitor. Thus OpenNMS 1.6.0 contains a new "model importer" feature that allows node, interface and service information to be imported directly into the system using data in an XML format. One company uses this method to manage over 70,000 devices with a single instance of OpenNMS.
同时OpenNMS现在的自动发现系统非常强大哦，档管理一万个节点的时候，OpenNMS往往倾向于使用一个外部的系统来决定什么是需要OpenNMS监控的。在1.6中包括这样一个新功能‘模型导入’，他能把xml格式的节点和端口数据自己导入到OpenNMS系统中。曾经一个公司用这个方法管理这7万个节点，都在一套OpenNMS系统内，好家伙~~也就是说这个功能有了之后，你就可以不用一个节点的去发现了，往往有些机器发现的那会正好不在线，那就漏掉很多的机器了。
Data collection saw many improvements as well. With the proper hardware, OpenNMS is able to collect over one million data points every five minutes. This data can be from SNMP (versions 1, 2c and 3), JMX, HTTP, or NSClient. The collected data can be exported via the web user interface. Reports showing the highest and lowest values for a particular set of data points (Top N Reports) can also be created, and 1.6.0 contains a vastly improved thresholding system. Thresholds can be generated on individual data points, combinations of data points, as well as a "relative change" such as when a value shows a sudden increase or decrease.
数据的采集方面也有很多增强。利用一个合适的硬件，OpenNMS能够每5分钟把超过一百万的数据采集点采集一遍，要是采集稳定的话，这还是比较快的了。被采集的数据点可以使来自 snmp v1,2,3, JMX, http, nsclient。 采集来的数据能通过web界面到处了。这还是不错的功能，能有可能做一些系统之外的自定义报表了。自带的报表功能能够定制TopN的报表。OpenNMS现在的阀值管理系统也得到了增强。能为某一个数据点设置，也能为一组数据采集点，同时有了对 "relative change"的管理，也就是某个数据忽高忽低的管理，也即是某些瞬间的异常增的很高或降的很低。
OpenNMS was originally designed for network service monitoring, and that functionality has been increased as well. New monitors for such things as Windows services are now available, as well as more advanced synthetic transactions. The Page Sequence Monitor was created to monitor a complete web-based transaction, while the Mail Transport Monitor determines the full round-trip availability of a mail service.
OpenNMS天生是监控网络的。新增了很多monitor，例如windows服务监控，模拟交易监控。页面序列监控器用了监控一些列的web交易处理行为，还能通过Mail Transport Monitor 来确定邮件服务的可用性。
Probably the biggest change was the development of distributed monitoring. Using a small Java webstart application installed on a remote system, OpenNMS is able to monitor service availability from the point of view of the remote system. Combined with the Page Sequence Monitor one can measure the user's experience when visiting a website from various remote locations.
最大的变更在这个版本中是‘分布式监控’，使用一个小的安装在远处的一个主机上的Java Webstat应用，opennms能过过这个监控服务点看到远程的系统上采集的数据。结合页面序列监控功能，它可以实现这样的功能：在南北方，网通电信的网络中找四个点安装这个程序后，模拟从不同网络位置监控某个web网站上一系列功能页面的可用性。这就是所谓的模拟交易管理，是Web应用管理方面中当下不可缺少的环节。
As OpenNMS was designed as a platform, there are numerous ways for external applications, both open and proprietary, to integrate with it. There is a new Trouble Ticketing API that allows for two-way communication between OpenNMS and a number of external ticketing systems such as Jira, Concursive (CentricCRM) and OTRS.
像opennms这样的平台，可以提供给开源或者商业外部系统的接口。通过这些api的双向接口，你可以把报警事件送到外部的工单管理系统(事件管理流程平台)中，例如 Jira, Concursive (CentricCRM) and OTRS.、
These are just a few of the new features available in 1.6.0. As always, OpenNMS is 100% free and open software. Please check it out and let us know what you think. We hope you enjoy using it as much as we enjoy creating it.
嗯，终于读完了整篇的发布说明，你能相信，它都发布了这么久了，我只有在周五晚上抽空仔细读完么。这周简直是太忙，天天加班，还有天天处理不完的状况。今天的一个教训就是“软件系统之间的集成不是简单能搞定的，需要小心，小心在小心”
I have Christopher T. Kuhn Blog's RSS feed in my blackberry. That's the way I following with OTRS project. Christoper do the best job to explain new features and updated s. I did not try out OTRS FAQ 1.5.3 yet, but it look great from Chrisopher's post.
