Zhang >*
2016-11-28 11:23
收件人
"OpenStack Development Mailing List (not for usage questions)" <
openstack-dev@lists.openstack.org>, "dong.wenj...@zte.com.cn" <
dong.wenj...@zte.com.cn>
抄送
"Hefetz, Idan (Nokia - IL)" , "
zhang.yuj...@zte.com.cn&qu
Hi, Alexey
My comments inline.
On Mon, Nov 28, 2016 at 1:52 AM Weyl, Alexey (Nokia - IL) <
alexey.w...@nokia.com> wrote:
> Hi Dong,
>
>
>
> I can think of 2 solutions for this problem:
>
> 1. We can talk with the AODH developers and check if they can add
> additional data for the aodh noti
, November 25, 2016 2:28 AM
To: Weyl, Alexey (Nokia - IL)
Cc: Hefetz, Idan (Nokia - IL); Afek, Ifat (Nokia - IL);
openstack-dev@lists.openstack.org; zhang.yuj...@zte.com.cn
Subject: 答复: RE: RE: [openstack-dev] [vitrage] about aodh alarm notification
EmThe solution goes back to my first question
); Afek, Ifat (Nokia - IL);
openstack-dev@lists.openstack.org; zhang.yuj...@zte.com.cn
Subject: 答复: RE: [openstack-dev] [vitrage] about aodh alarm notification
Hi Weyl Alexey,
Another question:
If we received the alarm.creation notification with the 'ok' state, we filter
it and don'
, Alexey (Nokia - IL); Hefetz, Idan (Nokia -
IL); zhang.yuj...@zte.com.cn
Cc: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [vitrage] about aodh alarm notification
Hi Vitrages,
Currently there are four aodh alarm notifications we need to handle:
'alarm.creation', '
Hi Vitrages,
Currently there are four aodh alarm notifications we need to handle:
'alarm.creation', 'alarm.rule_change', 'alarm.state_transition',
'alarm.deletion'
Only the alarm.creation notification carries the alarm detail info.
So we need to cache the alarm info.
When we receive other notif
