09:00:47 <ifat_afek_> #startmeeting vitrage
09:00:48 <openstack> Meeting started Wed Feb  3 09:00:47 2016 UTC and is due to finish in 60 minutes.  The chair is ifat_afek_. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:00:49 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:00:51 <openstack> The meeting name has been set to 'vitrage'
09:01:03 <ifat_afek_> Hi everyone :-)
09:02:41 <omer_etrog> Hi
09:03:29 <elisha_r> hi all!
09:04:59 <idan_hefetz> hi
09:06:45 <mkoushnir> hi
09:07:24 <ifat_afek_> #topic Current status
09:07:50 <adi__> hi
09:08:04 <ifat_afek_> First update - we are going to present Vitrage in Doctor’s IRC meeting, next Tuesday
09:08:34 <ifat_afek_> Our plan is to show them what we already have in vitrage, and talk about all use cases we plan to finish by mitaka
09:08:58 <ifat_afek_> As for my updates, I started working on nagios synchronizer plugin
09:09:26 <ifat_afek_> Already managed to get nagios html, now working on parsing it
09:09:32 <lhartal> hi all :)
09:09:40 <danoffek> Hi !
09:09:55 <ifat_afek_> I know that alexey_weyl, who can’t attend the meeting today, started working on the static plugin
09:10:19 <ifat_afek_> This plugin is supposed to read the physical topology (e.g. switches) from configuration files
09:10:57 <nadav_yakar> hi
09:11:02 <ifat_afek_> Who else wants to update?
09:11:08 <lhartal> I want
09:11:24 <lhartal> Last week we went over Vitrage use cases and prioritize them
09:11:48 <lhartal> the main goal is to accomplish a demo with Deduced Alarm and RCA for the next Openstack summit in April
09:12:30 <lhartal> Also, I’m working now on template validator
09:13:17 <lhartal> When Vitrage load the templates files into Vitrage, we check if their syntax is correct
09:13:22 <emalin> hi
09:13:45 <lhartal> If the syntax is worng – we won’t load the template and an error will be write into the log file
09:13:47 <ifat_afek_> lhartal, thanks. regarding what you said - we also made sure that all blueprints for the next use cases are handled, and should be ready on time
09:15:00 <lhartal> yes offcourse
09:15:06 <ifat_afek_> lhartal: sounds good. clear error messages are really important
09:15:49 <elisha_r> So I'll continue where liat left off
09:16:10 <elisha_r> meant lhartal :)
09:16:24 <elisha_r> I'm working on the Vitrage Template Evaluator
09:17:13 <elisha_r> for mitaka we should be able to support simple conditions (using only "and" operators). support for "or" and "not"  will come next. The current design is taking those future steps into account
09:17:45 <ifat_afek_> elisha_r, lhartal: saw your design, looks good
09:17:54 <ifat_afek_> if anyone else wishes to review it, here is the link:
09:18:24 <elisha_r> lhartal and I are working closely together on this, and also with idan_hefetz who is taking the "subgraph matching" side
09:18:50 <ifat_afek_> #link https://review.openstack.org/#/c/272033/
09:19:03 <elisha_r> anyhow, that's my main update
09:20:07 <idan_hefetz> yea, the subgraph matching will be implemented in the graph driver, i will start my more in the comming days
09:20:22 <mkoushnir> hi again
09:21:09 <lhartal> I have one more issue..
09:21:24 <ifat_afek_> idan_hefetz: are you doing networkx-specific implementation?
09:21:35 <lhartal> we need to decide how to present states in Vitrage (not deduce state)
09:21:52 <ifat_afek_> lhartal: can you explain?
09:22:00 <lhartal> the problem is that we are received different states for different entities (nova host does not have the same states as Nagios alarm for example)
09:22:28 <danoffek> Hi again.
09:22:33 <ifat_afek_> lhartal: right... good point
09:22:53 <ifat_afek_> so I guess we should find a way to normalize them?
09:22:54 <idan_hefetz> Good question ifat_afek currently it will be a network-x impl but we are currently thinking how to also support other graph types
09:23:30 <lhartal> We need to think how to handle this problem, because there are tasks in the GUI which are blocked because of it
09:23:40 <danoffek> @elisha_r youstated "not" is not supported in the near release. It's in the blueprint example @ifat_afek_ sent nevertheless.
09:24:34 <ifat_afek_> danoffek: I think it's good that the blueprint contains all examples, so we know our design is final and ok. but in the implementation, we will do it in phases
09:24:43 <danoffek> OK
09:24:50 <lhartal> @ifat_afek: I think we should do that as part of the transforming process
09:25:13 <elisha_r> danoffek: the template structure and format should take into account all the use cases we hope to support. But most templates will not need more than the "and" operator so it's a good first milestone
09:25:28 <ifat_afek_> lhartal: you are right, we need to think about it. the sunburst UI should recognize one set of states, not all possibilities (ok, valid, running... all should be green)
09:26:29 <ifat_afek_> moving on... mkoushnir, do you have any updates?
09:27:24 <mkoushnir> I have a pre-run-vitrage test
09:28:42 <mkoushnir> This test execute the vitrage-graph and  vitrage-api from local devstack
09:29:35 <mkoushnir> Next step - get real graph with validation
09:30:19 <ifat_afek_> mkoushnir: great! so this test actually starts the processes, but doesn't call the api yet?
09:32:40 <mkoushnir> the first step or tempest runner - is env, next step - all tempest tests, include get graph and rest exist vitrage api's, Last step - e2e scenario tests
09:33:05 <ifat_afek_> mkoushnir: cool, good plan
09:33:14 <mkoushnir> thanks
09:33:14 <ifat_afek_> who else wants to update?
09:33:24 <omer_etrog> I will update
09:34:50 <omer_etrog> we had a meeting with UX expert and decide what we will do
09:36:09 <omer_etrog> we also add support for Alarms, already implemented in the Vitrage Dashboard
09:37:01 <elisha_r> omer_etrog: cool! great progress
09:37:06 <ifat_afek_> omer_etrog: cool!! so if I have nagios plugin working in a few days, we will see real nagios alarms
09:37:09 <omer_etrog> and you can all test the vitrage-dashboard in your devstack, check the vitrage-dashboard github readme
09:37:42 <omer_etrog> we still need to add support for localisation
09:38:34 <omer_etrog> thats all for now
09:38:45 <ifat_afek_> omer_etrog: we may be able to show some real progress next week :-) eyalb did not join the meeting today, but I believe that implementing the api on his side won't take too long
09:39:37 <ifat_afek_> and speaking of eyalb, I know that he started working on the rca api
09:39:43 <ifat_afek_> any other updates anyone?
09:39:59 <ifat_afek_> #topic Review action items
09:40:09 <ifat_afek_> • ifat_afek_ check aodh integration and update the blueprints
09:40:30 <ifat_afek_> I stopped working on it for now, as the nagios plugin is more important for our second use case. Once I have it done, I will go back to aodh
09:40:44 <ifat_afek_> • review our use cases, blueprints and priorities
09:40:48 <ifat_afek_> this is done
09:40:58 <ifat_afek_> #topic Next Steps
09:41:26 <ifat_afek_> I think we should try to show nagios alarms in horizon next week
09:41:58 <ifat_afek_> #topic Open Discussion
09:42:08 <ifat_afek_> anyone?
09:43:40 <lhartal> and we should decide what to do with the states issue
09:43:42 <ifat_afek_> so I guess we're done for today
09:43:48 <ifat_afek_> goodbye everybody
09:43:53 <elisha_r> bye
09:43:56 <omer_etrog> bye
09:43:58 <lhartal> bye
09:44:21 <ifat_afek_> #endmeeting