Re: [openstack-dev] 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm

2016-10-20 Thread Afek, Ifat (Nokia - IL) 





On 20/10/2016, 20:14, "gordon chung"  wrote:

>
>On 20/10/16 01:01 PM, Afek, Ifat (Nokia - IL) wrote:
>> Well… long time ago I asked to add another notification topic to Aodh, and 
>> you said that you blocked it. If that’s not the case, everything is fine :-)
>> Like I said before, we planned on implementing it in Newton, but 
>> unfortunately it didn’t happen. I really hope to improve the Vitrage-Aodh 
>> integration in Ocata.
>>
>>
>>
>> Ifat.
>
>i see. i wasn't being critical about no work but i'll be honest, i don't 
>remember what this is about since i was looking at other stuff so if you 
>have a patch/ML to refresh my memory, that'd help.
>
>this is the only thread[1] i recall, and even then, i don't remember 
>much about it. :(
>
>[1] http://lists.openstack.org/pipermail/openstack-dev/2016-June/098074.html
>
>cheers,
>
>-- 
>gord

What I recall was a few months earlier, we had a chat on ceilometer IRC 
channel… not sure if I can find the exact date. 
Anyway, I guess it doesn’t matter now. If you think the change can be done, 
then great.

Ifat.


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm

2016-10-20 Thread gordon chung 

On 20/10/16 01:01 PM, Afek, Ifat (Nokia - IL) wrote:
> Well… long time ago I asked to add another notification topic to Aodh, and 
> you said that you blocked it. If that’s not the case, everything is fine :-)
> Like I said before, we planned on implementing it in Newton, but 
> unfortunately it didn’t happen. I really hope to improve the Vitrage-Aodh 
> integration in Ocata.
>
>
>
> Ifat.

i see. i wasn't being critical about no work but i'll be honest, i don't 
remember what this is about since i was looking at other stuff so if you 
have a patch/ML to refresh my memory, that'd help.

this is the only thread[1] i recall, and even then, i don't remember 
much about it. :(

[1] http://lists.openstack.org/pipermail/openstack-dev/2016-June/098074.html

cheers,

-- 
gord
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm

2016-10-20 Thread Afek, Ifat (Nokia - IL) 
Well… long time ago I asked to add another notification topic to Aodh, and you 
said that you blocked it. If that’s not the case, everything is fine :-)
Like I said before, we planned on implementing it in Newton, but unfortunately 
it didn’t happen. I really hope to improve the Vitrage-Aodh integration in 
Ocata.



Ifat.

On 20/10/2016, 16:09, "gordon chung"  wrote:

>um... what did i block? can you folks provide me some context here?
>
>the only thing i remember about the Vitrage session was that we agreed 
>the alarm notification framework already existed in Aodh and someone 
>just needed to step up and complete it. i don't think i saw any work on 
>it so i've honestly forgotten about it over the months.
>
>On 19/10/16 09:19 PM, dong.wenj...@zte.com.cn wrote:
>>
>> Hi Gordon Chung,
>>
>> Could you please tell me why adding another notification topic is not a
>> good choice? Thanks~
>>
>> BR,
>> dwj
>
>-- 
>gord
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm

2016-10-20 Thread gordon chung 
um... what did i block? can you folks provide me some context here?

the only thing i remember about the Vitrage session was that we agreed 
the alarm notification framework already existed in Aodh and someone 
just needed to step up and complete it. i don't think i saw any work on 
it so i've honestly forgotten about it over the months.

On 19/10/16 09:19 PM, dong.wenj...@zte.com.cn wrote:
>
> Hi Gordon Chung,
>
> Could you please tell me why adding another notification topic is not a
> good choice? Thanks~
>
> BR,
> dwj

-- 
gord
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm

2016-10-19 Thread dong . wenjuan 
Hi Gordon Chung,

Could you please tell me why adding another notification topic is not a 
good choice? Thanks~

BR,
dwj






"Afek, Ifat (Nokia - IL)"  
2016-10-19 16:20
请答复 给
"OpenStack Development Mailing List \(not for usage questions\)" 



收件人
"OpenStack Development Mailing List (not for usage questions)" 
, "g...@live.ca" 
抄送

主题
Re: [openstack-dev] [vitrage][aodh] about aodh notifier to create a event 
alarm








From: "dong.wenj...@zte.com.cn"
Date: Wednesday, 19 October 2016 at 11:01

The BP of aodh-message-bus-notifications[1] was blocked as Aodh message 
bus notification. 
As the discuession of Vitrage and Aodh in etherpad[2], only the Aodh 
alarm_deletion notification is missing.
I proposed a patch to add the Aodh alarm_deletion notification.[3]
Please help me to review this patch. 
Do the alarm.creation, alarm.state_transition and alarm.deletion satisfy 
the Vitrage requirement?
I'd like to help to implement the aodh-message-bus-notifications BP if 
there is nobody interest in it.

This is more complex. Aodh has a mechanism for registering a URL to be 
notified when the state of a specific alarm is changed. 
Vitrage asked for something else - a notification whenever *any* alarm 
state is changed. In Vitrage we don’t want to register to each and every 
Aodh alarm separately, so we prefer to get the notifications for all 
changes on the message bus (as we do with other OpenStack projects). In 
addition, there is currently no notification about a newly created alarm, 
so even if we register a URL on each alarm we will not be able to register 
it on the new alarms. 

[dwj]:  If i understand correctly, Aodh already support a notification 
whenever *any* alarm state is changed.
  See 
https://github.com/openstack/aodh/blob/master/aodh/evaluator/__init__.py#L107
.
  We only need to config the vitrage_notifications topics in Aodh then 
Vitrage can get the notifications from Aodh.
  Let me know if i miss something. 

A few months ago I discussed it with Gordon Chung, and understood that he 
blocked the option to add another notification topic. 
Gordon?


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm

2016-10-19 Thread dong . wenjuan 
"Afek, Ifat (Nokia - IL)"  
2016-10-19 15:21
请答复 给
"OpenStack Development Mailing List \(not for usage questions\)" 



收件人
"OpenStack Development Mailing List (not for usage questions)" 

抄送

主题
Re: [openstack-dev] [vitrage][aodh] about aodh notifier to create a event 
alarm






From: "dong.wenj...@zte.com.cn"
Date: Wednesday, 19 October 2016 at 09:21

The BP of aodh-message-bus-notifications[1] was blocked as Aodh message 
bus notification. 
As the discuession of Vitrage and Aodh in etherpad[2], only the Aodh 
alarm_deletion notification is missing.
I proposed a patch to add the Aodh alarm_deletion notification.[3]
Please help me to review this patch. 
Do the alarm.creation, alarm.state_transition and alarm.deletion satisfy 
the Vitrage requirement?
I'd like to help to implement the aodh-message-bus-notifications BP if 
there is nobody interest in it.

This is more complex. Aodh has a mechanism for registering a URL to be 
notified when the state of a specific alarm is changed. 
Vitrage asked for something else - a notification whenever *any* alarm 
state is changed. In Vitrage we don’t want to register to each and every 
Aodh alarm separately, so we prefer to get the notifications for all 
changes on the message bus (as we do with other OpenStack projects). In 
addition, there is currently no notification about a newly created alarm, 
so even if we register a URL on each alarm we will not be able to register 
it on the new alarms. 

[dwj]:  If i understand correctly, Aodh already support a notification 
whenever *any* alarm state is changed.
  See 
https://github.com/openstack/aodh/blob/master/aodh/evaluator/__init__.py#L107
.
  We only need to config the vitrage_notifications topics in Aodh then 
Vitrage can get the notifications from Aodh.
  Let me know if i miss something.


About the Aodh custon alarm:
What about the alarm type as `prompt` or something else like this, which 
means the alarm 
is fired with no evaluation. And the metedata include the `source_id` 
means which source
the alarm is on? 

This is more or less what we had in mind. Be able to control the state 
change externally + add metadata to the alarm (resource_id and optimally 
other information).


[1]
https://blueprints.launchpad.net/vitrage/+spec/aodh-message-bus-notifications

[2]https://etherpad.openstack.org/p/newton-telemetry-vitrage
[3]https://review.openstack.org/#/c/387754/



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm

2016-10-19 Thread dong . wenjuan 
Hi All,

The BP of aodh-message-bus-notifications[1] was blocked as Aodh message 
bus notification. 
As the discuession of Vitrage and Aodh in etherpad[2], only the Aodh 
alarm_deletion notification is missing.
I proposed a patch to add the Aodh alarm_deletion notification.[3]
Please help me to review this patch.
Do the alarm.creation, alarm.state_transition and alarm.deletion satisfy 
the Vitrage requirement?
I'd like to help to implement the aodh-message-bus-notifications BP if 
there is nobody interest in it.


About the Aodh custon alarm:
What about the alarm type as `prompt` or something else like this, which 
means the alarm 
is fired with no evaluation. And the metedata include the `source_id` 
means which source
the alarm is on?
Let me know if you have some good ideas.
Thanks,


[1]https://blueprints.launchpad.net/vitrage/+spec/aodh-message-bus-notifications
[2]https://etherpad.openstack.org/p/newton-telemetry-vitrage
[3]https://review.openstack.org/#/c/387754/


BR,
dwj







"Afek, Ifat (Nokia - IL)"  
2016-10-13 17:31
请答复 给
"OpenStack Development Mailing List \(not for usage questions\)" 



收件人
"OpenStack Development Mailing List (not for usage questions)" 

抄送

主题
Re: [openstack-dev] [vitrage][aodh] about aodh notifier to create a event 
alarm






Hi dwj,

Thanks for bringing this up.

Aodh notifier plugin inside Vitrage is defined as a POC, and is disabled 
by default. We are aware that this integration is not working well, and 
its purpose was to demonstrate how it could work and start a discussion 
about other possible implementations. I know that in Austin there were 
discussions between Aodh and Vitrage teams, and a general agreement that 
Vitrage would suggest a design for Aodh custom alarm. Such an alarm could 
then be used by Vitrage instead of the event-alarm in a more natural way. 

Unfortunately, due to time limitations, we did not get to write the custom 
alarm blueprint in Aodh. It is still defined as a high priority in Vitrage 
roadmap, and I hope it will happen in Ocata. If you have some free time 
you are more than welcome to give a hand :-)

Best Regards,
Ifat.


From: "dong.wenj...@zte.com.cn"
Date: Thursday, 13 October 2016 at 04:20

Hi vitrages, 

In aodh notifier plugin, we receive a ACTIVATE_DEDUCED_ALARM_EVENT and 
then create a aodh event alarm.
The event alarm with a `event_rule`, it should be include `event_type` and 
`query` which Aodh used to evaluator
a alarm when it receives a specify event to filter with the query to fire 
a alarm. see [1]

But we create a event alarm only with `query` in `event_rule`.
The deduced alarm create with the `alarm` state so Aodh will skip to 
evaluator the fired alarm.
The `event_rule` seems no necessary in the request body, am I right?
Let me know if i miss something. :)

[1]
https://github.com/openstack/aodh/blob/master/doc/source/event-alarm.rst


BR, 
dwj 

董文娟   Wenjuan Dong 
控制器四部 / 无线产品   Controller Dept Ⅳ. / Wireless Product Operation
  


上海市浦东新区碧波路889号中兴通讯D3
D3, ZTE, No. 889, Bibo Rd.
T: +86 021 85922M: +86 13661996389
E: dong.wenj...@zte.com.cn
www.ztedevice.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm

2016-10-14 Thread Julien Danjou 
On Fri, Oct 14 2016, dong.wenj...@zte.com.cn wrote:

> Is there any record about the discussion between Aodh and Vitrage?

The notes are in the Etherpad:

  https://etherpad.openstack.org/p/newton-telemetry-vitrage
  
-- 
Julien Danjou
/* Free Software hacker
   https://julien.danjou.info */


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm

2016-10-13 Thread dong . wenjuan 
Hi Ifat，

Got it. Thanks for your reponse.
Is there any record about the discussion between Aodh and Vitrage?

BR,
dwj







"Afek, Ifat (Nokia - IL)"  
2016-10-13 17:31
请答复 给
"OpenStack Development Mailing List \(not for usage questions\)" 



收件人
"OpenStack Development Mailing List (not for usage questions)" 

抄送

主题
Re: [openstack-dev] [vitrage][aodh] about aodh notifier to create a event 
alarm






Hi dwj,

Thanks for bringing this up.

Aodh notifier plugin inside Vitrage is defined as a POC, and is disabled 
by default. We are aware that this integration is not working well, and 
its purpose was to demonstrate how it could work and start a discussion 
about other possible implementations. I know that in Austin there were 
discussions between Aodh and Vitrage teams, and a general agreement that 
Vitrage would suggest a design for Aodh custom alarm. Such an alarm could 
then be used by Vitrage instead of the event-alarm in a more natural way. 

Unfortunately, due to time limitations, we did not get to write the custom 
alarm blueprint in Aodh. It is still defined as a high priority in Vitrage 
roadmap, and I hope it will happen in Ocata. If you have some free time 
you are more than welcome to give a hand :-)

Best Regards,
Ifat.


From: "dong.wenj...@zte.com.cn"
Date: Thursday, 13 October 2016 at 04:20

Hi vitrages, 

In aodh notifier plugin, we receive a ACTIVATE_DEDUCED_ALARM_EVENT and 
then create a aodh event alarm.
The event alarm with a `event_rule`, it should be include `event_type` and 
`query` which Aodh used to evaluator
a alarm when it receives a specify event to filter with the query to fire 
a alarm. see [1]

But we create a event alarm only with `query` in `event_rule`.
The deduced alarm create with the `alarm` state so Aodh will skip to 
evaluator the fired alarm.
The `event_rule` seems no necessary in the request body, am I right?
Let me know if i miss something. :)

[1]
https://github.com/openstack/aodh/blob/master/doc/source/event-alarm.rst


BR, 
dwj 

董文娟   Wenjuan Dong 
控制器四部 / 无线产品   Controller Dept Ⅳ. / Wireless Product Operation
  


上海市浦东新区碧波路889号中兴通讯D3
D3, ZTE, No. 889, Bibo Rd.
T: +86 021 85922M: +86 13661996389
E: dong.wenj...@zte.com.cn
www.ztedevice.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[附件 "ATT1.gif" 被 董文娟00101742/user/zte_ltd 删除][附件 
"ATT2.gif" 被 董文娟00101742/user/zte_ltd 删除]

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev