<div dir="ltr">I prefer 2.b from instinct.<div><br></div><div>Not sure it could be linked to the vitrage_id[1] evolution. If an uuid is created for the alarm, the implementation could be quite straightforward.<br><br>[1]: <a href="https://blueprints.launchpad.net/vitrage/+spec/standard-vitrage-id">https://blueprints.launchpad.net/vitrage/+spec/standard-vitrage-id</a></div><div><br><div class="gmail_quote"><div dir="ltr">On Tue, Jan 10, 2017 at 1:55 AM Afek, Ifat (Nokia - IL) <<a href="mailto:ifat.afek@nokia.com">ifat.afek@nokia.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" lang="EN-US" link="blue" vlink="purple" class="gmail_msg">
<div class="m_6388905390047508922WordSection1 gmail_msg">
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Hi Yujun,<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">I understand the use case now, thanks for the detailed explanation.
<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Supporting this use case will require some development in Vitrage. Let me try to list down the requirements and options that we have.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="m_6388905390047508922MsoListParagraphCxSpFirst gmail_msg">
<u class="gmail_msg"></u><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><span class="gmail_msg">1.<span style="font:7.0pt "Times New Roman"" class="gmail_msg">
</span></span></span><u class="gmail_msg"></u><span dir="LTR" class="gmail_msg"></span><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Requirement: Raise ‘suspect’ deduced alarms in Vitrage.
<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="m_6388905390047508922MsoListParagraphCxSpMiddle gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Implementation: Quite straight forward. There is no way to set ‘suspect’ property in Vitrage right now, but it should be easy to add this option.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="m_6388905390047508922MsoListParagraphCxSpMiddle gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="m_6388905390047508922MsoListParagraphCxSpMiddle gmail_msg">
<u class="gmail_msg"></u><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><span class="gmail_msg">2.<span style="font:7.0pt "Times New Roman"" class="gmail_msg">
</span></span></span><u class="gmail_msg"></u><span dir="LTR" class="gmail_msg"></span><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Requirement: Change a ‘suspect’ alarm of type ‘vitrage’ to a ‘real’ alarm of type ‘nagios’.
<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="m_6388905390047508922MsoListParagraphCxSpMiddle gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Implementation: There are a few alternatives how to achieve this goal<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="m_6388905390047508922MsoListParagraphCxSpMiddle gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="m_6388905390047508922MsoListParagraphCxSpMiddle gmail_msg" style="margin-left:72.0pt">
<u class="gmail_msg"></u><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><span class="gmail_msg">a.<span style="font:7.0pt "Times New Roman"" class="gmail_msg">
</span></span></span><u class="gmail_msg"></u><span dir="LTR" class="gmail_msg"></span><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Delete the ‘suspect’ alarm and create the ‘real’ alarm. This will require supporting ‘not’ condition in the templates. An example scenario:<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="m_6388905390047508922MsoListParagraphCxSpMiddle gmail_msg" style="margin-left:72.0pt">
<span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">condition: vm_alarm and not nagios_alarm:<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="m_6388905390047508922MsoListParagraphCxSpMiddle gmail_msg" style="margin-left:72.0pt">
<span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"> (action: create vitrage alarm)<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="m_6388905390047508922MsoListParagraphCxSpMiddle gmail_msg" style="margin-left:72.0pt">
<span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">condition: nagios_alarm and vitrage_alarm:<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="m_6388905390047508922MsoListParagraphCxSpMiddle gmail_msg" style="margin-left:72.0pt">
<span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"> (action: delete vitrage_alarm)<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="m_6388905390047508922MsoListParagraphCxSpMiddle gmail_msg" style="margin-left:72.0pt">
<span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="m_6388905390047508922MsoListParagraphCxSpMiddle gmail_msg" style="margin-left:72.0pt">
<u class="gmail_msg"></u><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><span class="gmail_msg">b.<span style="font:7.0pt "Times New Roman"" class="gmail_msg">
</span></span></span><u class="gmail_msg"></u><span dir="LTR" class="gmail_msg"></span><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Have both ‘suspect’ alarm and ‘real’ alarm, and create a ‘equivalent’ relationship between them. Configuring the template should be easy, however it won’t
look nice in the UI. In past discussions we mentioned an option to group some vertices together in the UI. If we have this option, we might want to group these two alarms together.
<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="m_6388905390047508922MsoListParagraphCxSpMiddle gmail_msg" style="margin-left:72.0pt">
<span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="m_6388905390047508922MsoListParagraphCxSpLast gmail_msg" style="margin-left:72.0pt">
<u class="gmail_msg"></u><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><span class="gmail_msg">c.<span style="font:7.0pt "Times New Roman"" class="gmail_msg">
</span></span></span><u class="gmail_msg"></u><span dir="LTR" class="gmail_msg"></span><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Merge the two alarms. This solution seems the most reasonable one at first, but it is not trivial. For example: suppose one alarm is defined as ‘critical’
and was raised at 10:01, and the other alarm was defined as ‘warning’ and was raised at 10:02. How will you combine the two? And what if the ‘critical’ alarm then goes down, will you know how to change the severity back to ‘warning’? in case of vitrage vs.
nagios we would like to prefer nagios; but let’s think of the more general case of two different monitors.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="m_6388905390047508922MsoListParagraph gmail_msg"><u class="gmail_msg"></u><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><span class="gmail_msg">3.<span style="font:7.0pt "Times New Roman"" class="gmail_msg">
</span></span></span><u class="gmail_msg"></u><span dir="LTR" class="gmail_msg"></span><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">In one of your emails you mentioned an option of having two ‘suspects’. Suppose vm_alarm is raised, will you raise two suspect vitrage alarms, e.g. host_alarm
and switch_alarm? And if you then receive host_alarm from nagios, would you like to delete the suspect switch_alarm, or keep it? If you would like to delete it, it will require supporting ‘not’ in the template condition.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Personally I would go for option 2b, but I will be happy to hear your thoughts about it.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Hope I helped, but I suspect I just made things more complicated ;-)
<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Ifat.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm" class="gmail_msg">
<p class="MsoNormal gmail_msg"><b class="gmail_msg"><span style="font-family:Calibri;color:black" class="gmail_msg">From: </span>
</b><span style="font-family:Calibri;color:black" class="gmail_msg">Yujun Zhang <<a href="mailto:zhangyujun%2Bzte@gmail.com" class="gmail_msg" target="_blank">zhangyujun+zte@gmail.com</a>></span></p></div></div></div><div bgcolor="white" lang="EN-US" link="blue" vlink="purple" class="gmail_msg"><div class="m_6388905390047508922WordSection1 gmail_msg"><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm" class="gmail_msg"><p class="MsoNormal gmail_msg"><span style="font-family:Calibri;color:black" class="gmail_msg"><br class="gmail_msg">
<b class="gmail_msg">Reply-To: </b>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" class="gmail_msg" target="_blank">openstack-dev@lists.openstack.org</a>><br class="gmail_msg">
</span></p></div></div></div><div bgcolor="white" lang="EN-US" link="blue" vlink="purple" class="gmail_msg"><div class="m_6388905390047508922WordSection1 gmail_msg"><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm" class="gmail_msg"><p class="MsoNormal gmail_msg"><span style="font-family:Calibri;color:black" class="gmail_msg"><b class="gmail_msg">Date: </b>Sunday, 8 January 2017 at 17:38</span></p></div></div></div><div bgcolor="white" lang="EN-US" link="blue" vlink="purple" class="gmail_msg"><div class="m_6388905390047508922WordSection1 gmail_msg"><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm" class="gmail_msg"><p class="MsoNormal gmail_msg"><span style="font-family:Calibri;color:black" class="gmail_msg"><br class="gmail_msg">
<b class="gmail_msg">To: </b>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" class="gmail_msg" target="_blank">openstack-dev@lists.openstack.org</a>><br class="gmail_msg">
<b class="gmail_msg">Cc: </b>"<a href="mailto:han.jing28@zte.com.cn" class="gmail_msg" target="_blank">han.jing28@zte.com.cn</a>" <<a href="mailto:han.jing28@zte.com.cn" class="gmail_msg" target="_blank">han.jing28@zte.com.cn</a>>, "<a href="mailto:wang.weiya@zte.com.cn" class="gmail_msg" target="_blank">wang.weiya@zte.com.cn</a>" <<a href="mailto:wang.weiya@zte.com.cn" class="gmail_msg" target="_blank">wang.weiya@zte.com.cn</a>>, "<a href="mailto:gong.yahui5@zte.com.cn" class="gmail_msg" target="_blank">gong.yahui5@zte.com.cn</a>" <<a href="mailto:gong.yahui5@zte.com.cn" class="gmail_msg" target="_blank">gong.yahui5@zte.com.cn</a>>, "<a href="mailto:jia.peiyuan@zte.com.cn" class="gmail_msg" target="_blank">jia.peiyuan@zte.com.cn</a>" <<a href="mailto:jia.peiyuan@zte.com.cn" class="gmail_msg" target="_blank">jia.peiyuan@zte.com.cn</a>>, "<a href="mailto:zhang.yujunz@zte.com.cn" class="gmail_msg" target="_blank">zhang.yujunz@zte.com.cn</a>" <<a href="mailto:zhang.yujunz@zte.com.cn" class="gmail_msg" target="_blank">zhang.yujunz@zte.com.cn</a>><br class="gmail_msg">
<b class="gmail_msg">Subject: </b>Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p></div></div></div><div bgcolor="white" lang="EN-US" link="blue" vlink="purple" class="gmail_msg"><div class="m_6388905390047508922WordSection1 gmail_msg"><div class="gmail_msg">
<p class="MsoNormal gmail_msg">Maybe I have missed something in the scenario template, but it seems you have understood my idea quite correctly :-)
<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></p>
</div>
</div></div></div><div bgcolor="white" lang="EN-US" link="blue" vlink="purple" class="gmail_msg"><div class="m_6388905390047508922WordSection1 gmail_msg"><div class="gmail_msg"><div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-bottom:12.0pt">See further explanation inline<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<div class="gmail_msg"></div></div></div></div></div><div bgcolor="white" lang="EN-US" link="blue" vlink="purple" class="gmail_msg"><div class="m_6388905390047508922WordSection1 gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg">
<div class="gmail_msg">
<p class="MsoNormal gmail_msg">On Sun, Jan 8, 2017 at 3:06 PM Afek, Ifat (Nokia - IL) <<a href="mailto:ifat.afek@nokia.com" class="gmail_msg" target="_blank">ifat.afek@nokia.com</a>> wrote:<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm" class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Hi Yujun,</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"> </span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Thanks for the explanation, but I still don’t fully understand.</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"> </span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Let me start with the current state:</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">1.</span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.0pt" class="gmail_msg">
</span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">introduce a flexible `metadata` dict in to ALARM entity</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="text-indent:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">[Ifat] Already exists. An alarm is represented as a vertex in the entity graph, with a dictionary of properties.</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
</div>
</blockquote>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"> <u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"> [yujunz] Can the alarm vertex be updated by scenario action? e.g. raise an alarm and set the property `suspect` to true.<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm" class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">2.</span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.0pt" class="gmail_msg">
</span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Allow generating update event[1] on metadata change</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">3.</span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.0pt" class="gmail_msg">
</span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Allow using ALARM metadata in scenario condition</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="text-indent:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">[Ifat] Already exists. You can define properties in the ‘entities’ section in Vitrage templates</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
</div>
</blockquote>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"> <u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg">[yujunz] How do I specify the condition if one specified alarm is 'suspicious', e.g. condition: host_alarm.suspect ?<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm" class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">4.</span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.0pt" class="gmail_msg">
</span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Allow setting ALARM metadata in scenario action</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"> </span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">If I understand correctly, you are suggesting that one scenario will add metadata to an existing alarm,
which will trigger an event, and as a result another scenario might be executed?</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
</div>
</blockquote>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"> <u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg">[yujunz] Exactly <u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm" class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Can you describe a use case where this behavior will help calculating the root cause?</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
</div>
</blockquote>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"> <u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg">[yujunz] Here's the simplified case derived from YinLiYin's example. Suppose we add a causal relationship from `host_alarm` to `instance_alarm`, i.e. host alarm will cause instance alarm. If an instance alarm is detected (but no host alarm).
It is "suspicious" that it may be caused by host alarm. The reason could be event delay or lost. Instead of waiting for snapshot service to update the host status, we want to run a diagnostic action to check it initiatively.<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg">In this case, we want to set the upstream (host) of a confirmed alarm (instance) to "suspect" and trigger an diagnostic action on this change.<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg">Hope that I have made the use case clear.<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></p>
</div>
</div></div></div></div></div><div bgcolor="white" lang="EN-US" link="blue" vlink="purple" class="gmail_msg"><div class="m_6388905390047508922WordSection1 gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm" class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Thanks,</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Ifat.</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"> </span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"> </span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm" class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><b class="gmail_msg"><span style="font-family:Calibri;color:black" class="gmail_msg">From: </span>
</b></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-family:Calibri;color:black" class="gmail_msg">Yujun Zhang <<a href="mailto:zhangyujun%2Bzte@gmail.com" class="gmail_msg" target="_blank">zhangyujun+zte@gmail.com</a>></span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
</div>
</div>
<div class="gmail_msg">
<div class="gmail_msg">
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm" class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span style="font-family:Calibri;color:black" class="gmail_msg"><br class="gmail_msg">
<span class="m_6388905390047508922gmailmsg gmail_msg"><b class="gmail_msg">Reply-To: </b>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" class="gmail_msg" target="_blank">openstack-dev@lists.openstack.org</a>></span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
</div>
</div>
<div class="gmail_msg">
<div class="gmail_msg">
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm" class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><b class="gmail_msg"><span style="font-family:Calibri;color:black" class="gmail_msg">Date: </span>
</b></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-family:Calibri;color:black" class="gmail_msg">Saturday, 7 January 2017 at 09:27</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
</div>
</div>
<div class="gmail_msg">
<div class="gmail_msg">
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm" class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span style="font-family:Calibri;color:black" class="gmail_msg"><br class="gmail_msg">
<span class="m_6388905390047508922gmailmsg gmail_msg"><b class="gmail_msg">To: </b>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" class="gmail_msg" target="_blank">openstack-dev@lists.openstack.org</a>></span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
</div>
</div>
<div class="gmail_msg">
<div class="gmail_msg">
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm" class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><b class="gmail_msg"><span style="font-family:Calibri;color:black" class="gmail_msg">Cc: </span>
</b></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-family:Calibri;color:black" class="gmail_msg">"<a href="mailto:han.jing28@zte.com.cn" class="gmail_msg" target="_blank">han.jing28@zte.com.cn</a>" <<a href="mailto:han.jing28@zte.com.cn" class="gmail_msg" target="_blank">han.jing28@zte.com.cn</a>>, "<a href="mailto:wang.weiya@zte.com.cn" class="gmail_msg" target="_blank">wang.weiya@zte.com.cn</a>"
<<a href="mailto:wang.weiya@zte.com.cn" class="gmail_msg" target="_blank">wang.weiya@zte.com.cn</a>>, "<a href="mailto:gong.yahui5@zte.com.cn" class="gmail_msg" target="_blank">gong.yahui5@zte.com.cn</a>" <<a href="mailto:gong.yahui5@zte.com.cn" class="gmail_msg" target="_blank">gong.yahui5@zte.com.cn</a>>, "<a href="mailto:jia.peiyuan@zte.com.cn" class="gmail_msg" target="_blank">jia.peiyuan@zte.com.cn</a>"
<<a href="mailto:jia.peiyuan@zte.com.cn" class="gmail_msg" target="_blank">jia.peiyuan@zte.com.cn</a>>, "<a href="mailto:zhang.yujunz@zte.com.cn" class="gmail_msg" target="_blank">zhang.yujunz@zte.com.cn</a>" <<a href="mailto:zhang.yujunz@zte.com.cn" class="gmail_msg" target="_blank">zhang.yujunz@zte.com.cn</a>></span></span><span style="font-family:Calibri;color:black" class="gmail_msg"><br class="gmail_msg">
<span class="m_6388905390047508922gmailmsg gmail_msg"><b class="gmail_msg">Subject: </b>Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
</div>
</div>
<div class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
The two questions raised by YinLiYin is actually one, i.e. <b class="gmail_msg">how to enrich the alarm properties
</b>that can be used as an condition in root cause deducing. <u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
Both 'suspect' or 'datasource' are additional information that may be referred as a condition in general fault model, a.k.a. scenario in vitrage.<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
It seems it could be done by<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
</div>
</div>
</div>
<div class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<ol start="1" type="1" class="gmail_msg">
<li class="MsoNormal gmail_msg">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:10.0pt" class="gmail_msg">introduce a flexible `metadata` dict in to ALARM entity</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></li></ol>
</div>
</div>
</div>
</div>
<div class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:72.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg">2.</span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.0pt" class="gmail_msg">
</span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:10.0pt" class="gmail_msg">Allow generating update event[1] on metadata change</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:72.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg">3.</span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.0pt" class="gmail_msg">
</span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:10.0pt" class="gmail_msg">Allow using ALARM metadata in scenario condition</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:72.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg">4.</span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.0pt" class="gmail_msg">
</span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:10.0pt" class="gmail_msg">Allow setting ALARM metadata in scenario action</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
</div>
</div>
</div>
<div class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
This will leave the flexibility to continuous development by defining a complex scenario template and keep the vitrage evaluator simple and generic.<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
My two cents.<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
[1]: <a href="http://docs.openstack.org/developer/vitrage/scenario-evaluator.html#concepts-and-guidelines" class="gmail_msg" target="_blank">http://docs.openstack.org/developer/vitrage/scenario-evaluator.html#concepts-and-guidelines</a> <u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
</div>
</div>
</div>
</blockquote></div></div></div></div></div><div bgcolor="white" lang="EN-US" link="blue" vlink="purple" class="gmail_msg"><div class="m_6388905390047508922WordSection1 gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
On Sat, Jan 7, 2017 at 2:23 AM Afek, Ifat (Nokia - IL) <<a href="mailto:ifat.afek@nokia.com" class="gmail_msg" target="_blank">ifat.afek@nokia.com</a>> wrote:<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<div class="gmail_msg">
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Hi YinLiYin,</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"> </span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">This is an interesting question. Let me divide my answer to two parts.</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"> </span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">First, the case that you described with Nagios and Vitrage. This problem depends on the specific Nagios tests that you configure in your system, as well as on the Vitrage templates that
you use. For example, you can use Nagios/Zabbix to monitor the physical layer, and Vitrage to raise deduced alarms on the virtual and application layers. This way you will never have duplicated alarms. If you want to use Nagios to monitor the other layers
as well, you can simply modify Vitrage templates so they don’t raise the deduced alarms that Nagios may generate, and use the templates to show RCA between different Nagios alarms.</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"> </span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Now let’s talk about the more general case. Vitrage can receive alarms from different monitors, including Nagios, Zabbix, collectd and Aodh. If you are using more than one monitor, it
is possible that the same alarm (maybe with a different name) will be raised twice. We need to create a mechanism to identify such cases and create a single alarm with the properties of both monitors. This has not been designed in details yet, so if you have
any suggestion we will be happy to hear them.</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"> </span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Best Regards,</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg">Ifat.</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"> </span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:11.0pt;font-family:Calibri" class="gmail_msg"> </span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm" class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:72.0pt">
<span class="m_6388905390047508922gmailmsg gmail_msg"><b class="gmail_msg"><span style="font-family:Calibri;color:black" class="gmail_msg">From: </span>
</b></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-family:Calibri;color:black" class="gmail_msg">"<a href="mailto:yinliyin@zte.com.cn" class="gmail_msg" target="_blank">yinliyin@zte.com.cn</a>" <<a href="mailto:yinliyin@zte.com.cn" class="gmail_msg" target="_blank">yinliyin@zte.com.cn</a>></span></span><span style="font-family:Calibri;color:black" class="gmail_msg"><br class="gmail_msg">
<span class="m_6388905390047508922m1242506880783174039gmailmsg gmail_msg"><b class="gmail_msg">Reply-To: </b>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" class="gmail_msg" target="_blank">openstack-dev@lists.openstack.org</a>></span><br class="gmail_msg">
<span class="m_6388905390047508922m1242506880783174039gmailmsg gmail_msg"><b class="gmail_msg">Date: </b>Friday, 6 January 2017 at 03:27</span><br class="gmail_msg">
<span class="m_6388905390047508922m1242506880783174039gmailmsg gmail_msg"><b class="gmail_msg">To: </b>"<a href="mailto:openstack-dev@lists.openstack.org" class="gmail_msg" target="_blank">openstack-dev@lists.openstack.org</a>" <<a href="mailto:openstack-dev@lists.openstack.org" class="gmail_msg" target="_blank">openstack-dev@lists.openstack.org</a>></span><br class="gmail_msg">
<span class="m_6388905390047508922m1242506880783174039gmailmsg gmail_msg"><b class="gmail_msg">Cc: </b>"<a href="mailto:gong.yahui5@zte.com.cn" class="gmail_msg" target="_blank">gong.yahui5@zte.com.cn</a>" <<a href="mailto:gong.yahui5@zte.com.cn" class="gmail_msg" target="_blank">gong.yahui5@zte.com.cn</a>>, "<a href="mailto:han.jing28@zte.com.cn" class="gmail_msg" target="_blank">han.jing28@zte.com.cn</a>"
<<a href="mailto:han.jing28@zte.com.cn" class="gmail_msg" target="_blank">han.jing28@zte.com.cn</a>>, "<a href="mailto:wang.weiya@zte.com.cn" class="gmail_msg" target="_blank">wang.weiya@zte.com.cn</a>" <<a href="mailto:wang.weiya@zte.com.cn" class="gmail_msg" target="_blank">wang.weiya@zte.com.cn</a>>, "<a href="mailto:jia.peiyuan@zte.com.cn" class="gmail_msg" target="_blank">jia.peiyuan@zte.com.cn</a>"
<<a href="mailto:jia.peiyuan@zte.com.cn" class="gmail_msg" target="_blank">jia.peiyuan@zte.com.cn</a>>, "<a href="mailto:zhang.yujunz@zte.com.cn" class="gmail_msg" target="_blank">zhang.yujunz@zte.com.cn</a>" <<a href="mailto:zhang.yujunz@zte.com.cn" class="gmail_msg" target="_blank">zhang.yujunz@zte.com.cn</a>></span><br class="gmail_msg">
<span class="m_6388905390047508922m1242506880783174039gmailmsg gmail_msg"><b class="gmail_msg">Subject: </b>[openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
</div>
</div>
</div></div></blockquote></div></div></div></div></div><div bgcolor="white" lang="EN-US" link="blue" vlink="purple" class="gmail_msg"><div class="m_6388905390047508922WordSection1 gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg">
<p class="m_6388905390047508922m1242506880783174039gmailmsg1 gmail_msg" style="margin-right:0cm;margin-bottom:0cm;margin-left:72.0pt;margin-bottom:.0001pt;line-height:15.0pt;background:white;box-sizing:border-box;min-height:14px;outline:none!important">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-family:宋体" class="gmail_msg">Hi all, </span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="m_6388905390047508922m1242506880783174039gmailmsg1 gmail_msg" style="margin-right:0cm;margin-bottom:0cm;margin-left:72.0pt;margin-bottom:.0001pt;line-height:15.0pt;background:white;box-sizing:border-box;min-height:14px;outline:none!important">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-family:宋体" class="gmail_msg"> Vitrage generate alarms acording to the templates. All the alarms raised by vitrage has the type "vitrage". Suppose Nagios has an alarm A. Alarm A is raised by vitrage evaluator according to the action
part of a scenario, type of alarm A is "vitrage". If Nagios reported alarm A latter, a new alarm A with type "Nagios" would be generator in the entity graph. There would be two vertices for the same alarm in the graph. And we have to define two alarm entities,
two relationships, two scenarios in the template file to make the alarm propagation procedure work.</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="m_6388905390047508922m1242506880783174039gmailmsg1 gmail_msg" style="margin-right:0cm;margin-bottom:0cm;margin-left:72.0pt;margin-bottom:.0001pt;line-height:15.0pt;background:white;box-sizing:border-box;min-height:14px;outline:none!important">
<span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-family:宋体" class="gmail_msg"> It is inconvenient to describe fault model of system with lot of alarms. How to solve this problem?</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div></div></div></div></div></blockquote></div></div></div></div></div><div bgcolor="white" lang="EN-US" link="blue" vlink="purple" class="gmail_msg"><div class="m_6388905390047508922WordSection1 gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg">
<p class="m_6388905390047508922m1242506880783174039gmailmsg1 gmail_msg" style="margin-left:72.0pt"><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:5.5pt;font-family:宋体" class="gmail_msg"> </span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="m_6388905390047508922m1242506880783174039gmailmsg1 gmail_msg" style="margin-left:72.0pt"><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:9.0pt;font-family:Calibri;color:#58595b" class="gmail_msg">殷力殷</span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:9.0pt;font-family:Times;color:#58595b" class="gmail_msg"> </span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-family:Arial;color:#58595b" class="gmail_msg">YinLiYin</span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="m_6388905390047508922m1242506880783174039gmailmsg1 gmail_msg" style="margin-left:72.0pt"><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:5.5pt" class="gmail_msg"> </span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="m_6388905390047508922m1242506880783174039gmailmsg1 gmail_msg" style="margin-left:72.0pt"> <u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<table class="m_6388905390047508922MsoNormalTable gmail_msg" border="0" cellpadding="0" width="594" style="width:445.5pt;margin-left:72.0pt">
<tbody class="gmail_msg">
<tr class="gmail_msg">
<td width="94" valign="top" style="width:70.5pt;padding:.75pt .75pt .75pt .75pt" class="gmail_msg">
<p class="MsoNormal gmail_msg"><span style="font-family:宋体;color:black" class="gmail_msg"><b class="gmail_msg">Error! Filename not specified.</b></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</td>
<td width="494" valign="top" style="width:370.5pt;padding:.75pt .75pt .75pt .75pt" class="gmail_msg">
<p class="MsoNormal gmail_msg" style="word-break:break-all">
<span style="font-family:宋体;color:black" class="gmail_msg"><b class="gmail_msg">Error! Filename not specified.</b><br class="gmail_msg">
</span></p></td></tr></tbody></table></div></div></div></div></div></div></blockquote></div></div></div></div></div><div bgcolor="white" lang="EN-US" link="blue" vlink="purple" class="gmail_msg"><div class="m_6388905390047508922WordSection1 gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><table class="m_6388905390047508922MsoNormalTable gmail_msg" border="0" cellpadding="0" width="594" style="width:445.5pt;margin-left:72.0pt"><tbody class="gmail_msg"><tr class="gmail_msg"><td width="494" valign="top" style="width:370.5pt;padding:.75pt .75pt .75pt .75pt" class="gmail_msg"><p class="MsoNormal gmail_msg" style="word-break:break-all"><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.5pt;font-family:宋体;color:#58595b" class="gmail_msg">上海市浦东新区碧波路</span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.5pt;font-family:Times;color:#58595b" class="gmail_msg">889</span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.5pt;font-family:宋体;color:#58595b" class="gmail_msg">号中兴研发大楼</span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.5pt;font-family:Times;color:#58595b" class="gmail_msg">D502 </span></span><span style="font-size:7.5pt;font-family:Times;color:#58595b" class="gmail_msg"><br class="gmail_msg">
</span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.5pt;font-family:Arial;color:#58595b" class="gmail_msg">D502, ZTE Corporation R&D Center, 889# Bibo Road,
</span></span><span style="font-size:7.5pt;font-family:Arial;color:#58595b" class="gmail_msg"><br class="gmail_msg">
<span class="m_6388905390047508922m1242506880783174039m5609626365442085205signedit gmail_msg">Zhangjiang Hi-tech Park, Shanghai, P.R.China, 201203</span><span class="m_6388905390047508922m1242506880783174039gmailmsg gmail_msg"> </span><br class="gmail_msg">
</span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.5pt;font-family:Arial;color:#008fd4" class="gmail_msg">T</span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.5pt;font-family:Arial;color:#58595b" class="gmail_msg">:
<a href="tel:+86%2021%206889%206229" class="gmail_msg" target="_blank">+86 21 68896229</a></span></span><span style="font-size:7.5pt;font-family:Arial;color:#58595b" class="gmail_msg"><br class="gmail_msg">
</span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.5pt;font-family:Arial;color:#008fd4" class="gmail_msg">M</span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.5pt;font-family:Arial;color:#58595b" class="gmail_msg">:
<a href="tel:+86%20136%204189%205907" class="gmail_msg" target="_blank">+86 13641895907</a> </span>
</span><span style="font-size:7.5pt;font-family:Arial;color:#58595b" class="gmail_msg"><br class="gmail_msg">
</span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.5pt;font-family:Arial;color:#008fd4" class="gmail_msg">E</span></span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.5pt;font-family:Arial;color:#58595b" class="gmail_msg">:
<a href="mailto:yinliyin@zte.com.cn" class="gmail_msg" target="_blank">yinliyin@zte.com.cn</a></span></span><span style="font-size:7.5pt;font-family:Arial;color:#58595b" class="gmail_msg"><br class="gmail_msg">
</span><span class="m_6388905390047508922gmailmsg gmail_msg"><span style="font-size:7.5pt;font-family:Arial;color:#008fd4" class="gmail_msg"><a href="http://www.zte.com.cn/" class="gmail_msg" target="_blank">www.zte.com.cn</a></span></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p></td></tr></tbody></table></div></div></div></div></div></div></blockquote></div></div></div></div></div><div bgcolor="white" lang="EN-US" link="blue" vlink="purple" class="gmail_msg"><div class="m_6388905390047508922WordSection1 gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-left:36.0pt">
__________________________________________________________________________<br class="gmail_msg">
OpenStack Development Mailing List (not for usage questions)<br class="gmail_msg">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" class="gmail_msg" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="gmail_msg">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="gmail_msg" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div></div></blockquote></div></div></div></div></div><div bgcolor="white" lang="EN-US" link="blue" vlink="purple" class="gmail_msg"><div class="m_6388905390047508922WordSection1 gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm" class="gmail_msg">
<p class="MsoNormal gmail_msg">__________________________________________________________________________<br class="gmail_msg">
OpenStack Development Mailing List (not for usage questions)<br class="gmail_msg">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" class="gmail_msg" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="gmail_msg">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="gmail_msg" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</blockquote></div></div></div></div></div>
__________________________________________________________________________<br class="gmail_msg">
OpenStack Development Mailing List (not for usage questions)<br class="gmail_msg">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" class="gmail_msg" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="gmail_msg">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="gmail_msg">
</blockquote></div></div></div>