08:02:42 <ifat_afek> #startmeeting vitrage
08:02:42 <openstack> Meeting started Wed Nov  1 08:02:42 2017 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:02:43 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:02:45 <openstack> The meeting name has been set to 'vitrage'
08:02:46 <ifat_afek> Hi :-)
08:02:56 <idan_hefetz> Hi
08:02:58 <eyalb> (ό‿ὸ)ﾉ
08:04:57 <ifat_afek> Today’s agenda:
08:05:06 <ifat_afek> •	Status and Updates
08:05:12 <ifat_afek> •	Open Discussion
08:05:20 <ifat_afek> #topic Status and Updates
08:05:37 <ifat_afek> New releases were created for vitrage, based on stable/pike:
08:05:44 <ifat_afek> vitrage 1.8.2
08:05:54 <ifat_afek> python-vitrage client 1.4.0
08:06:16 <ifat_afek> The Sydney summit is next weeks. There will be two sessions about Vitrage:
08:06:23 <ifat_afek> #link https://www.openstack.org/summit/sydney-2017/summit-schedule/events/19508/advanced-fault-management-with-vitrage-and-mistral
08:06:29 <ifat_afek> #link https://www.openstack.org/summit/sydney-2017/summit-schedule/events/19473/vitrage-project-updates
08:06:49 <ifat_afek> I’m almost done preparing the Vitrage-Mistral demo. Now working on the presentations.
08:06:56 <ifat_afek> As part of preparing the demo, I found a few bugs:
08:07:10 <ifat_afek> 1.	UI (already fixed by Alon): in the entity graph when selecting a specific Heat stack, the alarm icons were changed to heat stack icons
08:07:23 <ifat_afek> 2. UI (already fixed by Alon): in the entity graph properties area, the name was missing, and the user could see the internal is_real_vitrage_id flag
08:07:40 <ifat_afek> 3. The UI shows placeholder entities. Not sure why. It seems like a new bug.
08:07:50 <ifat_afek> This bug has two parts actually – one is to change the API query, and the other is to identify why we have placeholder vertices (this is supposed to be a temporary situation).
08:08:04 <ifat_afek> It is related to neutron.port datasource. The transformer assumes that the port neighbor is always an instance, but apparently this is not the case.
08:08:12 <ifat_afek> 1.	Then, placeholder/dummy instances are created and stay in the graph.
08:08:34 <ifat_afek> The last “1” was a mistake
08:08:42 <ifat_afek> A more significant issue that I realized is that the integration with Mistral is lacking.
08:08:55 <ifat_afek> Currently, in the template file you can ask to execute a workflow with specific pre-defined parameters. But you can not pass a dynamic parameter, like the current instance.
08:09:22 <ifat_afek> I’ll create a blueprint for that, probably after I’m back from Sydney
08:09:25 <ifat_afek> That’s it for me
08:10:13 <annarez> I'll update
08:10:23 <annarez> I'm working on adjusting Vitrage to networkx 2.0 with backward compatibility to 1.1<networkx<2.0
08:10:48 <annarez> Apparently the networkx teem published very good documentation for the new version
08:11:25 <annarez> we have open bug on this https://bugs.launchpad.net/openstack-requirements/+bug/1718576
08:11:27 <openstack> Launchpad bug 1718576 in Solar "Handle networkx 2.0 update" [Undecided,In progress] - Assigned to Rajat Sharma (tajar29)
08:11:50 <annarez> that's it :)
08:12:30 <idan_hefetz> my update
08:12:39 <idan_hefetz> Parallel template evaluation is merged, default number of workers is currently 1, but we may wish to change this later on.
08:12:45 <idan_hefetz> To configure this, under [evaluator] add workers=x
08:13:06 <idan_hefetz> btw, thanks for the reviews :)
08:13:16 <ifat_afek> Thanks for the change ;-)
08:13:58 <idan_hefetz> I still have two issue to solve, and to add documentation
08:14:26 <idan_hefetz> that it
08:14:26 <idan_hefetz> that's it
08:15:49 <ifat_afek> Thanks. Anyone else?
08:18:22 <ifat_afek> BTW, I suggest that in the next meeting we go over the roadmap and tasks that we decided on in the PTG, and check the current status
08:18:29 <ifat_afek> #link https://etherpad.openstack.org/p/vitrage-ptg-queens
08:18:44 <nivolas> yes
08:19:02 <nivolas> i added support for regular expressions when defining entities in the templates
08:19:42 <nivolas> this fixed in issue with Zabbix alarams that had regular expressions implemented in them (as Zabbix has added support for regular expression)
08:21:41 <nivolas> thats it
08:21:56 <ifat_afek> Thanks
08:22:00 <ifat_afek> Any other updates?
08:23:29 <ifat_afek> #topic Open Discussion
08:23:49 <ifat_afek> Anything?
08:25:42 <ifat_afek> Then let’s close the meeting
08:25:46 <ifat_afek> Bye :-)
08:26:13 <annarez> bye
08:26:15 <nivolas> bye!
08:26:20 <ifat_afek> #endmeeting