08:00:16 #startmeeting vitrage 08:00:17 Meeting started Wed Feb 8 08:00:16 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:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:20 The meeting name has been set to 'vitrage' 08:00:24 Hi everyone :-) 08:01:24 Hi! 08:02:47 Shalom :) 08:03:09 Today’s agenda: 08:03:15 • Ocata Release 08:03:19 Hi, I have two meetings at the same time slot. Ping me if any input required from me 08:03:20 • Status and Updates 08:03:32 yujunz: no problem 08:03:52 last in the agenda: 08:03:53 • Pike Design sessions 08:04:47 #topic Ocata Release 08:04:55 Last week I tagged vitrage modules: 08:05:00 vitrage 1.5.0 08:05:05 python-vitrageclient 1.1.1 08:05:10 vitrage-dashboard 1.1.1 08:05:20 These are our current release candidates. Please don’t push anything to stable/ocata, unless it is an important bug fix. You can use the master branch for Pike development. 08:05:38 The final release date is at the end of next week, by March 16th. The full Ocata schedule can be found here: 08:05:43 #link https://releases.openstack.org/ocata/schedule.html 08:05:48 Any questions/comments? 08:06:33 #topic Status and Updates 08:06:41 Boston CFP is closed. The following etherpad contains the Vitrage proposals: 08:06:52 #link https://etherpad.openstack.org/p/vitrage-boston-session-proposals 08:07:02 Good luck to us all 08:07:15 My updates: I wrote two use cases for Doctor manual, trying to push them to their gerrit 08:07:26 Next I’ll update the test script so it will check Vitrage in addition to Congress. And then I’ll have to check it in a Newton devstack with Ocata Vitrage. 08:07:40 (Trying to do both things in parallel…) 08:07:48 Who else wants to update? 08:08:38 \o 08:09:00 I will update 08:09:25 vitrage was merged to the RDO project 08:09:35 so now we have rpms 08:09:44 :) 08:09:49 great news! 08:10:11 still need to resolve some issues regarding the dashboard in order for it be added to RDO also 08:10:29 RDO is short for ? 08:10:45 I am now working on the puppet module so it can be run in RDO also 08:11:13 acceptance test were added to the puppet-vitrage module 08:11:47 #link https://www.rdoproject.org/ 08:12:07 a repository for artifacts of openstack 08:12:23 Got it 08:13:19 there are still issues with the puppet-openstack-integration 08:13:39 which is another project to run tempest tests 08:13:46 once this is done 08:14:21 I will add the puppet also to RDO so tempest tests will run after an rpm creation 08:14:27 thats all 08:14:44 OK, my short update. 08:15:05 Preparing the trip to design session in Israel. 08:15:11 :-) 08:15:43 RDO is the RPM Distribution of OpenStack 08:15:46 I should fly to Tel Aviv right? 08:16:23 We have only one international airport in Israel ;-) Ben-Gurion 08:17:09 OK, I guess I need some information on how to get to the hotel. To be folloowed up in email 08:17:38 Sure, let’s discuss it in emails 08:17:41 Meanwhile, I'm reviewing Weiya's proposal on alarm deduction 08:17:51 #link https://review.openstack.org/#/c/423000 08:18:01 Yes, you asked us to discuss it in IRC 08:18:21 And I thought I’d better ask everyone to read it and think about it in advance, but forgot to do that 08:18:29 Because it’s a complicated issue 08:18:44 Weiya is not available today and I think we may need a pre-discussion in a small group before the design session 08:19:10 Sure, so let’s try to do it next week. Do you want to discuss via IRC or in another way? 08:19:13 Do you think it possible to arrange a conference call for it? ifat_afek 08:19:27 I think we may need a conference call 08:19:42 Sure. BTW, why is it important to discuss before the design session? 08:19:52 I just expect a long discussion here 08:20:48 Yes, just because it is long, I think discussion in a small group will be more efficient. 08:21:07 And we can share a more mature proposal on the design session 08:21:52 To get something clarified before Weiya goes detail in the design 08:22:14 To ensure we are going in the right direction 08:22:16 Ok. What is your availability next week? 08:22:34 I'll discuss with Weiya and reply to you in Email. Is that oK? 08:22:44 Ok 08:22:50 Thanks. 08:22:55 That's all from my side 08:23:03 Thanks 08:23:11 Anyone else wants to update? 08:24:02 My update is that I'm still working on vitrage ID. 08:24:10 Ok, thanks 08:24:16 Anyone else? 08:25:04 Moving to the next topic, which we actually started discussing 08:25:06 #topic Pike Design Sessions 08:25:17 We will hold Pike Design Sessions in Israel, on March 6th-9th 08:25:25 You are all invited to participate and to suggest topics for the discussions. The sessions will be mostly in the mornings, so ZTE colleagues from China can participate remotely. 08:25:30 The design session etherpad: 08:25:39 #link https://etherpad.openstack.org/p/vitrage-pike-design-sessions 08:25:45 Feel free to edit the agenda and suggest new topics for discussion. 08:26:49 Any other issue to you would like to discuss? 08:27:41 You mean the design session? 08:28:15 Or anything else 08:28:37 Though aodh team is not joining, I think it worth discussion on the generic alarm proposal 08:28:49 It seems no conclusion yet, is it? 08:29:39 I think the conclusion is, at least my conclusion is, that Aodh do not see themselves as an alarm manager, and are not interested in the generic alarm feature 08:29:49 But we can discuss it, why not 08:30:17 We can think of alternative solutions for an Aodh-Vitrage integration. Since this is a non-trivial topic, I agree that it is worth a discussio 08:30:36 Agree 08:31:43 There is requirement of alarm management from vitrage and aodh may offer only part of it. So we need to fill the gaps in some way. That is my understanding of this topic. 08:32:06 Makes sense 08:33:22 Ok, anything else? 08:35:42 Goodbye then 08:35:49 bye 08:36:15 By Guys, Ifat, stay happy 08:36:28 danoffek: always :-) :-) 08:36:53 #endmeeting