On 04/29/2012 11:49 AM, Peter Nixon wrote: > Before I commit these to git, I was wondering if there is any > preferred naming convention. At present with have multiple files per > vendor under events (eg. Juniper.events, Juniper.mcast.events, > Junos.events, JunosV1.events) but only one file under datacollection.
Hrrm. I sort of prefer more files over modifying an existing one as it will make upgrades easier. That said, I still think we should logically group functionality for each collection/report group - so if there is a collection for, say, Cisco wireless access points, we should try to just have the one file. But collections for a Cisco PIX should get its own. My hope is to be able to modularize OpenNMS based on device type. One day we should be able to install configuration for each different device - say a module of packages for polling, datacolletion, events, notifications and graphs. Make sense? -T -- Tarus BALOG, Maintainer Main: +1 919 533 0160 The OpenNMS Group, Inc. Fax: +1 773 345 3645 Email: ta...@opennms.org URL: http://www.opennms.org PGP Key Fingerprint: 8945 8521 9771 FEC9 5481 512B FECA 11D2 FD82 B45C ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel
