08:00:27 <ifat_afek> #startmeeting vitrage
08:00:28 <openstack> Meeting started Wed Mar  7 08:00:27 2018 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:00:29 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:00:32 <openstack> The meeting name has been set to 'vitrage'
08:00:33 <ifat_afek> Hi :-)
08:00:37 <eyalb> \o/
08:00:47 <annarez> Hi!
08:02:23 <ifat_afek> Agenda:
08:02:30 <ifat_afek> •	Status and updates
08:02:36 <ifat_afek> •	Open Discussion
08:02:40 <ifat_afek> #topic Status and updates
08:02:47 <ifat_afek> Queens was released with the following Vitrage versions:
08:02:51 <ifat_afek> vitrage 2.2.0
08:02:55 <ifat_afek> python-vitrageclient 2.0.0
08:02:59 <ifat_afek> vitrage-dashboard 1.4.2
08:03:07 <ifat_afek> I finally managed to release vitrage-tempest-plugin version 1.0.0 (the tempest-plugins are independent of the releases).
08:03:18 <ifat_afek> Last week we had the Rocky PTG discussions. The etherpad is here:
08:03:23 <ifat_afek> #link https://etherpad.openstack.org/p/vitrage-ptg-rocky
08:03:33 <ifat_afek> My updates: I started working on the merge-resource design. I’m still in the phase of thinking over the high level design.
08:03:39 <ifat_afek> That’s it for me. Any other updates?
08:04:09 <eyalb> vitrage-tempest-plugin was tagged 1.0.0
08:04:41 <eyalb> I am checking a way to make sure queens vitrage will use vitrage-tempest-plugin 1.0.0 in gate
08:05:09 <eyalb> at the moment I have a hack to fix it
08:05:19 <eyalb> but i am not sure it will work
08:05:20 <Liat> Hi
08:05:29 <eyalb> thats it
08:05:29 <annarez> eyalb what is it using now?
08:05:39 <eyalb> the master version
08:07:39 <ifat_afek> And the problem is that the master tempest no longer fits the Queens code, so the tempest fails for stable/queens
08:07:55 <ifat_afek> Anyone else wants to update?
08:09:04 <Liat> Idan_kinori  started working on data source for k8s Najjar started with the prometheus
08:10:06 <ifat_afek> Thanks
08:10:11 <ifat_afek> Any other updates?
08:11:08 <peipei> Hi, I'll update.
08:11:29 <peipei> I've been working on the blueprints: alarm-merge/proactive-rca/bidirectional-deduce.
08:11:48 <peipei> Details of how to implement proactive-rca/bidirectional-deduce will be summited sooner.
08:12:19 <peipei> But details about alarm-merge will be summitted after agreement on whether to merge monitored alarms and how to do it.
08:13:29 <ifat_afek> I’m now thinking about merge resource, and I’m trying to think also whether it is related to the merge alarm blueprint
08:13:46 <ifat_afek> If the use cases are similar, maybe we could find a solution that works for both cases
08:13:50 <ifat_afek> But I’m not sure about it yet
08:14:11 <ifat_afek> I’ll try to come with something today or tomorrow, so we can progress
08:14:39 <ifat_afek> Regarding the proactive-rca and hte bidirectional-deduce, I think the concept is fine and only some details are missing
08:14:45 <ifat_afek> So it’s not a problem
08:15:07 <peipei> Ok, maybe we can find  out a common solution.
08:16:07 <ifat_afek> I’ll let you know once I have a high level design for the merge resource, so we can think if it’s the same
08:16:52 <ifat_afek> Any other updates?
08:18:13 <ifat_afek> #topic Open Discussion
08:18:38 <ifat_afek> I can mention StoryBoard migration again, but it’s getting boring… I hope to handle it by next week
08:18:45 <ifat_afek> Any other issue you would like to discuss?
08:20:11 <ifat_afek> Bye, see you next week
08:20:23 <peipei> Bye
08:20:24 <annarez> bye :)
08:20:24 <eyalb> bye
08:20:28 <ifat_afek> #endmeeting