Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of anshul.gangwar@citrix.com
 designates 203.166.19.134 as permitted sender)
From: Anshul Gangwar <anshul.gangwar@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Fri, 18 Jan 2013 10:51:32 +0530
Subject: Re: [Discuss] SNMP Alerts support in CloudStack
Thread-Topic: [Discuss] SNMP Alerts support in CloudStack
Thread-Index: Ac31O61Q4PexeZ+ySGiI1ep49uYXuA==
Message-ID: <50F8DBDC.6090703@citrix.com>
References: <50F4F82B.9050704@citrix.com>
 <CD1B2BBD.2C4BE%murali.reddy@citrix.com>
 <B1DF26ECC0458748AC97CECE2DA98D41012FA3B29F97@SJCPMAILBOX01.citrite.net>
 <50F7E033.2050503@citrix.com>
 <35F04D4C394874409D9BE4BF45AC5EA9010B286BF442@BANPMAILBOX01.citrite.net>
In-Reply-To: 
 <35F04D4C394874409D9BE4BF45AC5EA9010B286BF442@BANPMAILBOX01.citrite.net>
Accept-Language: en-US
Content-Language: en-US
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106
 Thunderbird/17.0.2
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

My implementation of log4j appender will require changes in
log4j-cloud.xml file and addition/modification of some LOG statements in
CloudStack. Which I suppose is not making it tightly coupled with CloudStac=
k.

Thanks,
Anshul


On 17/01/13 23:38, Ram Ganesh wrote:
> Anshul,
>
> If you implement your own SNMPlog4j appender then again it will not be ti=
ghtly coupled with CloudStack? Can you confirm that?
>
> Thanks,
> RamG
>
>> -----Original Message-----
>> From: Anshul Gangwar [mailto:anshul.gangwar@citrix.com]
>> Sent: 17 January 2013 16:58
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: [Discuss] SNMP Alerts support in CloudStack
>>
>> Alex,
>>
>> I have gone through the snmplog4jappender. As per my understanding
>> there
>> is no way to send traps to multiple SNMP Managers. One other thing
>> which
>> it is lacking is defining different OIDs for different kind of alerts.
>> Even in some way we are able to achieve above things using the library
>> then we have to make many changes in library. As per my understanding
>> it
>> will be better  to write our own SNMP log4j appender on similar lines
>> of
>> this library. That will be less tedious work then using this library.
>>
>> The default implementations( some implementations given in that
>> library)
>> of library is using incompatible license libraries.
>> Three default implemetations are
>> JoeSNMPTrapSender uses opennms library which has GPL License
>> http://www.opennms.org/wiki/Commercial_OpenNMS
>> WengsoftSNMPTrapSender uses library which has COPYRIGHT (c) 1999 by
>> WENG-SOFT Inc. Brosard QC CA
>> NetSnmpCommandLineTrapSender uses library which has
>> http://www.net-snmp.org/about/license.html license
>>
>>
>> Thanks,
>> Anshul
>>
>> On 16/01/13 02:32, Alex Huang wrote:
>>> In that case, why not just use snmplog4jappender?
>>>
>>> http://code.google.com/p/log4j-snmp-trap-appender/
>>>
>>> --Alex
>>>
>>>> -----Original Message-----
>>>> From: Murali Reddy [mailto:Murali.Reddy@citrix.com]
>>>> Sent: Tuesday, January 15, 2013 2:36 AM
>>>> To: cloudstack-dev@incubator.apache.org
>>>> Subject: Re: [Discuss] SNMP Alerts support in CloudStack
>>>>
>>>> On 15/01/13 12:03 PM, "Anshul Gangwar" <anshul.gangwar@citrix.com>
>>>> wrote:
>>>>
>>>>> My comments inline..
>>>>>
>>>>> On 14/01/13 22:52, Alex Huang wrote:
>>>>>> Anshul,
>>>>>>
>>>>>> I had assumed that if you were doing this based on Murali's event
>>>>>> framework, it would not be architected on an adapter in the alert
>>>>>> manager but as a subscriber to his event framework.  Has this been
>>>>>> discussed?  If so, why not subscribe to event framework?
>>>>> Murali,
>>>>> Can you reply for this.
>>>> Alex,
>>>>
>>>>   From what Anshul is proposing, I see that, requirements is to
>> generate a
>>>> SNMP trap for ALL of the alerts that CloudStack generates today, and
>> there
>>>> is no need for selectively subscribing to subset of alerts. Taking
>>>> dependency on the event framework would mean that this feature will
>>>> require a MOM broker for no additional benefit at least in this
>> context of
>>>> proposal. IMO, its seems good enough to just implement it as adapter
>> to
>>>> existing AlertManager and generate SNMP trap at source of alert
>> generation.
>>>>>> Also, I like to have the following asserted in the FS.
>>>>>>
>>>>>> - It is a separate project from CloudStack core
>>>>> Alex,
>>>>>
>>>>> I am developing this feature as plugin, so it will be separate
>> project
>>>> >from CloudStack core
>>>>>> - It only depends on cloud-utils and cloud-api jars for compile.
>>>>> I am making it sure that code does not use any class from other
>> jars
>>>>> apart from cloud-utils and cloud-api jars.
>>>>>
>>>>> I will update the FS with this info
>>>>>
>>>>>
>>>>>> Please confirm them.
>>>>>>
>>>>>> --Alex
>>>>> Thanks,
>>>>> Anshul
>>>>>>> -----Original Message-----
>>>>>>> From: Anshul Gangwar [mailto:anshul.gangwar@citrix.com]
>>>>>>> Sent: Friday, January 04, 2013 12:57 AM
>>>>>>> To: cloudstack-dev@incubator.apache.org
>>>>>>> Subject: Re: [Discuss] SNMP Alerts support in CloudStack
>>>>>>>
>>>>>>> I have created the initial draft of  FS here
>>>>>>>
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/FS+for+Integrati
>>>>>>> ng+CS+alerts+via+SNMP+to+external+management+system . I will
>>>> keep
>>>>>>> updating  the FS based on comments and suggestions.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Anshul
>>>>>>>
>>>>>>> On 02/01/13 12:21, Anshul Gangwar wrote:
>>>>>>>
>>>>>>> On 18/12/12 20:19, David Nalley wrote:
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Dec 18, 2012 at 6:12 AM, Anshul Gangwar
>>>>>>> <anshul.gangwar@citrix.com><mailto:anshul.gangwar@citrix.com>
>>>> wrote:
>>>>>>> Hi,
>>>>>>>            Currently CloudStack shows alerts on dashboard and can
>> send
>>>>>>> email
>>>>>>> alerts. With this feature it will be able to send SNMP alerts to
>>>>>>> configured external SNMP Managers.  Currently I am planning to
>> send
>>>>>>> SNMP
>>>>>>> traps for the alerts which are supported in CloudStack 4.0. I am
>>>>>>> planning to use snmp4j library available under Apache License to
>>>>>>> implement this feature.
>>>>>>>
>>>>>>>
>>>>>>> Fascinating - I am looking forward to seeing this!
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>             - Currently planning to support up to 20 SNMP managers
>>>>>>>
>>>>>>>
>>>>>>> This seems arbitrary. Why 20?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>             - Version 1 and 2 will be supported
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Why not v3 as well? SNMPv1 is practically deprecated, so why
>> bother
>>>>>>> with v1? v2 is a nice middle ground - v3 is where everyone wishes
>> to
>>>>>>> be if they could start from scratch.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>             - We need a unique SNMP OID for CloudStack. We need to
>>>>>>> register with
>>>>>>> IANA. Is there an established process in Apache to follow and get
>> one?
>>>>>>>
>>>>>>> I'll be happy to figure out how this gets done. - Actually some
>> quick
>>>>>>> googling shows that the ASF already has an enterprise OID - and
>> one of
>>>>>>> our mentors has documented that here:
>>>>>>> https://cwiki.apache.org/DIRxPMGT/oid-assignment-scheme.html
>>>>>>> I will follow up with Alex and see if we can get an assignment.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Hi David,
>>>>>>>         Is there any OID which I can use to start development.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> So your idea here seems like it is targeting just sending traps,
>> but
>>>>>>> I'm far more interested long-term in being able to query the SNMP
>>>>>>> daemon (and there likely will already be one on the host); so as
>> you
>>>>>>> are designing the MIB please do plan ahead for such things. The
>> page
>>>>>>> above is a good starting point around MIB design.
>>>>>>>
>>>>>>> If you need help around this, I am happy to lend what little I
>> know
>>>>>>> about the subject of SNMP, or connect you with experts in the
>> field.
>>>>>>> --David
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Anshul