08:00:27 <ifat_afek> #startmeeting vitrage
08:00:28 <openstack> Meeting started Wed Jan 25 08:00:27 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:00:29 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:00:31 <openstack> The meeting name has been set to 'vitrage'
08:00:35 <ifat_afek> Hi :-)
08:00:44 <eyalb> hi
08:01:43 <doffek> Hi guys.
08:02:48 <alexey_weyl> hi
08:03:40 <ifat_afek> Today’s agenda:
08:03:46 <ifat_afek> •	Ocata Release
08:04:01 <ifat_afek> •	Status and Updates
08:04:06 <ifat_afek> •	Pike Design sessions
08:04:11 <ifat_afek> •	Boston CFP
08:04:16 <ifat_afek> #topic Ocata Release
08:04:24 <ifat_afek> This week we need to release python-vitrageclient, and then to add it to the global-requirements
08:04:31 <ifat_afek> Unfortunately, our gate is broken for a few days (thanks Alexey_weyl and idan_hefetz for fixing it!), so it was delayed. I will request to release python-vitrageclient today
08:04:39 <ifat_afek> Once python-vitrageclient is released, I will request to add it to the global-requirements
08:05:03 <ifat_afek> Note that we can continue developing the vitrage and vitrage-dashboard projects for Ocata until February 16th (but we’ll probably stop a little earlier to make sure everything is stable)
08:05:14 <ifat_afek> This week is also the PTLs nomination week. I plan to announce my candidacy later today.
08:05:39 <ifat_afek> The full Ocata schedule can be found here:
08:05:44 <ifat_afek> #link https://releases.openstack.org/ocata/schedule.html
08:05:50 <ifat_afek> Any comments regarding the release dates?
08:06:19 <eyalb> nope
08:06:25 <ifat_afek> #topic Status and Updates
08:06:47 <ifat_afek> My updates: I’m done with the blueprint of adding a new API for post event to Vitrage, to be used by Doctor datasource (but not only).
08:06:56 <ifat_afek> #link https://blueprints.launchpad.net/vitrage/+spec/support-inspector-sb-api
08:07:03 <ifat_afek> Next thing, I plan to modify Doctor’s test script so that it will test Vitrage in a similar way to the Congress test.
08:07:11 <ifat_afek> Who’s next?
08:07:25 <doffek> I'll update .
08:08:01 <doffek> I prepared a Vitrage Lab via webinar for yesterday for anyone that wishes to contribute to Vitrage.
08:08:24 <doffek> Prepared about 15 Devstacks with Vitrage
08:08:52 <doffek> People joined the webinar and saw the preliminary presentation.
08:10:10 <doffek> There was a set of instructions as  part of the lab, that, when run, step by step allowed the lab participants to learn how Vitrage looks, how it works, how to run CLI commands, how to add additional datasources,
08:10:43 <doffek> It even had an easy instructions set for how to prepare templates for deduced alarms and RCA .
08:11:24 <doffek> But no one seemed to actually do the lab. That's a miss from my point of view. It was a lab webinar, not a presentation one.
08:11:41 <doffek> I don't see any new contributors coming from this webinar
08:12:05 <ifat_afek> doffek: It was only yesterday, let’s wait ;-)
08:12:15 <doffek> None of them participated in the lab.
08:12:32 <ifat_afek> And I think the presentation part is also very important. I understand why you were disappointed, but it still might help
08:12:45 <ifat_afek> Was the session recorded?
08:12:58 <ifat_afek> Because if it was, we could publish it
08:13:16 <doffek> Don't think so, but in any case, the purpose was to show potential contributors how easy it is to contribute.
08:13:26 <ifat_afek> I think there is a lot of value to it for a contributor that likes to start working with Vitrage
08:13:36 <ifat_afek> I konw…
08:13:41 <doffek> In any case, that's my update.
08:14:09 <ifat_afek> doffek: thanks! and BTW, I noticed you suggested a lab for Boston. I think it’s a great idea
08:14:43 <alexey_weyl> I will update
08:15:16 <alexey_weyl> we has some problems in the gate, and finally resolved them yesterday because some novaclient api was changed
08:15:46 <alexey_weyl> In addition I am working on the "not" operator for the templates
08:15:52 <ifat_afek> alexey_weyl: Thanks for fixing it! I just don’t understand how come no other project was affected. Strange…
08:16:13 <alexey_weyl> this will give a much bigger language to describe our language and our use cases
08:16:36 <ifat_afek> The ‘not’ is very important. It was blocking some of our use cases
08:16:52 <alexey_weyl> for example if we have HA between two switches, thus if one will fall then we won't have to raise alarms on some vms due to that
08:17:01 <ifat_afek> BTW, once you are done, don’t forget to update also the documentation
08:17:02 <nofarsch> maybe other projects knew of this change?
08:17:29 <ifat_afek> alexey_weyl: Right, that’s a good example
08:17:53 <ifat_afek> nofarsch: I must admit that I don’t follow all of nova emails. But I don’t believe I’m the only one who missed it
08:17:55 <alexey_weyl> We haven't seen that other projects encountered the same problem, most probably due to the fact that they didn't use the interface parameter for the novaclient
08:18:14 <ifat_afek> What is the interface parameter?
08:18:20 <alexey_weyl> Now, another update is the vitrage-aodh integration
08:19:46 <alexey_weyl> After the aodh team has agreed to our changes of adding a new alarm (in austin and barcelona) with another field called metadata/userdata that will contain some internal information about the alarm
08:20:56 <alexey_weyl> they are now rethinking that decision, because they say that aodh isn't an alarm manager for all alarms but is more a system that is alarm engine evaluator
08:22:55 <alexey_weyl> at the moment we are trying to figure out exactly what can't be done in that area with the aodh team, but if some other vitrage users have something to say about that, please do so, because I think if there will more voices that say that this value is needed then it may make them rethink about that
08:23:01 <alexey_weyl> that's it for now
08:23:58 <ifat_afek> Personally I was quite surprised that they started hesitating, because I felt that we already discussed it. We should continue the discussions in the ML until soneone is convinced :-)
08:24:40 <ifat_afek> Anyone else wants to updated?
08:24:42 <ifat_afek> update
08:25:31 <ifat_afek> #topic Pike Design Sessions
08:25:43 <ifat_afek> We will hold Pike Design Sessions in Israel, on March 6th-7th. You are all invited to participate and to suggest topics for the discussions
08:25:57 <ifat_afek> The design session etherpad:
08:26:13 <ifat_afek> #link https://etherpad.openstack.org/p/vitrage-pike-design-sessions
08:26:31 <ifat_afek> Any comments about it?
08:28:01 <ifat_afek> #topic Boston CFP
08:28:13 <ifat_afek> Boston CFP is now open, and we already listed some ideas in our etherpad
08:28:20 <ifat_afek> #link https://www.openstack.org/summit/boston-2017/call-for-presentations/
08:28:25 <ifat_afek> #link https://etherpad.openstack.org/p/vitrage-boston-session-proposals
08:28:32 <ifat_afek> Feel free to add more ideas. The deadline for submitting is February 6.
08:29:08 <ifat_afek> Any proposal you would like to discuss?
08:31:02 <ifat_afek> So I guess we are done. See you next week :-)
08:31:11 <eyalb> bye
08:31:12 <idan_hefetz> bye
08:31:37 <ifat_afek> #endmeeting