08:00:27 #startmeeting vitrage 08:00:28 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 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:31 The meeting name has been set to 'vitrage' 08:00:35 Hi :-) 08:00:44 hi 08:01:43 Hi guys. 08:02:48 hi 08:03:40 Today’s agenda: 08:03:46 • Ocata Release 08:04:01 • Status and Updates 08:04:06 • Pike Design sessions 08:04:11 • Boston CFP 08:04:16 #topic Ocata Release 08:04:24 This week we need to release python-vitrageclient, and then to add it to the global-requirements 08:04:31 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 Once python-vitrageclient is released, I will request to add it to the global-requirements 08:05:03 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 This week is also the PTLs nomination week. I plan to announce my candidacy later today. 08:05:39 The full Ocata schedule can be found here: 08:05:44 #link https://releases.openstack.org/ocata/schedule.html 08:05:50 Any comments regarding the release dates? 08:06:19 nope 08:06:25 #topic Status and Updates 08:06:47 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 #link https://blueprints.launchpad.net/vitrage/+spec/support-inspector-sb-api 08:07:03 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 Who’s next? 08:07:25 I'll update . 08:08:01 I prepared a Vitrage Lab via webinar for yesterday for anyone that wishes to contribute to Vitrage. 08:08:24 Prepared about 15 Devstacks with Vitrage 08:08:52 People joined the webinar and saw the preliminary presentation. 08:10:10 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 It even had an easy instructions set for how to prepare templates for deduced alarms and RCA . 08:11:24 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 I don't see any new contributors coming from this webinar 08:12:05 doffek: It was only yesterday, let’s wait ;-) 08:12:15 None of them participated in the lab. 08:12:32 And I think the presentation part is also very important. I understand why you were disappointed, but it still might help 08:12:45 Was the session recorded? 08:12:58 Because if it was, we could publish it 08:13:16 Don't think so, but in any case, the purpose was to show potential contributors how easy it is to contribute. 08:13:26 I think there is a lot of value to it for a contributor that likes to start working with Vitrage 08:13:36 I konw… 08:13:41 In any case, that's my update. 08:14:09 doffek: thanks! and BTW, I noticed you suggested a lab for Boston. I think it’s a great idea 08:14:43 I will update 08:15:16 we has some problems in the gate, and finally resolved them yesterday because some novaclient api was changed 08:15:46 In addition I am working on the "not" operator for the templates 08:15:52 alexey_weyl: Thanks for fixing it! I just don’t understand how come no other project was affected. Strange… 08:16:13 this will give a much bigger language to describe our language and our use cases 08:16:36 The ‘not’ is very important. It was blocking some of our use cases 08:16:52 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 BTW, once you are done, don’t forget to update also the documentation 08:17:02 maybe other projects knew of this change? 08:17:29 alexey_weyl: Right, that’s a good example 08:17:53 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 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 What is the interface parameter? 08:18:20 Now, another update is the vitrage-aodh integration 08:19:46 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 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 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 that's it for now 08:23:58 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 Anyone else wants to updated? 08:24:42 update 08:25:31 #topic Pike Design Sessions 08:25:43 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 The design session etherpad: 08:26:13 #link https://etherpad.openstack.org/p/vitrage-pike-design-sessions 08:26:31 Any comments about it? 08:28:01 #topic Boston CFP 08:28:13 Boston CFP is now open, and we already listed some ideas in our etherpad 08:28:20 #link https://www.openstack.org/summit/boston-2017/call-for-presentations/ 08:28:25 #link https://etherpad.openstack.org/p/vitrage-boston-session-proposals 08:28:32 Feel free to add more ideas. The deadline for submitting is February 6. 08:29:08 Any proposal you would like to discuss? 08:31:02 So I guess we are done. See you next week :-) 08:31:11 bye 08:31:12 bye 08:31:37 #endmeeting