08:03:04 #startmeeting vitrage 08:03:05 Meeting started Wed Apr 19 08:03:04 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:03:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:03:08 The meeting name has been set to 'vitrage' 08:03:08 Hi again :-) 08:03:11 ni hao 08:03:55 你好 :) 08:04:19 And I assume that’s Hi in English? :-) 08:04:26 Hi 08:05:10 Today’s agenda: 08:05:17 • Status and Updates 08:05:28 • Boston Summit 08:05:37 • Open Discussion 08:05:48 #topic Status and Updates 08:05:58 Some general updates: 08:06:04 Mitaka was declared EOL. 08:06:16 Vitrage was mentioned in OPNFV HA meeting last week, as part of the HA group architecture for supporting HA scenarios in NFV environments 08:06:28 #link https://gerrit.opnfv.org/gerrit/#/c/33475 08:06:39 My updates: 08:06:41 \o/ 08:06:53 I wrote down the Vitrage HA and alarm history vision, as we discussed. Will be happy to get more reviews 08:06:59 #link https://review.openstack.org/#/c/455065/ 08:07:06 That’s it for me 08:07:09 hey 08:07:12 Who’s next? 08:07:31 I'll go next 08:07:46 I've been working on refactoring some of the code for the Machine Learning component 08:08:03 I hope to get this done sometime next week, and then push it 08:08:35 hopefully things will go smoothly, but of course the real test will be once we run it for a while in a live deployment, and that will take time 08:09:05 Once this is in, I'll be running tests with synthetic data so we get a sense of performance 08:09:07 that's it 08:09:19 I'll go next 08:09:49 Busy preparing OPNFV plugfest next week. No activity recently 08:10:05 Will start working on entity equivalent next week 08:10:05 That's it 08:10:21 sounds good 08:10:33 let us know if you need any hel 08:10:40 *help 08:10:40 yujunz: Thanks. What are you presenting in the plugfest? (not relevant to this discussion, just curious) 08:10:57 QTIP benchmarking on different hardware 08:11:03 Cool 08:11:13 I'm not attending, but need to prepare it for the team 08:11:38 O 08:11:40 Ok 08:11:51 one small update 08:12:16 the rpm for the puppet was approved ad should be in the RDO repository 08:12:19 thats it 08:12:35 eyalb: Does it mean we are done? or there is still some work to do? 08:12:47 What is the package name? 08:13:02 puppet-vitrage :-) 08:13:16 there is always work to do 08:13:19 Does that mean we can install vitrage with it? 08:13:46 I need to check how to make the smoke tests run when an rpm is built 08:13:59 @yujunz yes 08:14:18 you could before now its is packaged as an rpm 08:14:33 Sounds good. How is the packaging done? I mean automatically by CI or manually? 08:14:44 So we can send Gergely instructions for rpm installations? or is it still too early? 08:14:55 yes automatically on every commit 08:15:00 (Gergely Catsary is working on Vitrage installation guide) 08:15:15 and also on a release 08:15:58 @ifat yes 08:16:03 Great 08:16:33 Every commit on vitrage or puppet-vitrage? 08:19:06 (testing) 08:20:10 My last question before dropping: Every commit on vitrage or puppet-vitrage? 08:20:14 In the meantime, I’ll update on behalf of danoffek that he is progressing with the Vitrage ID. He is having code reviews and fixes the tempests 08:20:21 every commit on vitrage updates the vitrage rpm and every commit on puppet-vitrage updates the puppet-vitrage rpm 08:21:06 I will update 08:21:29 I am working on the advanced use cases session for Boston. 08:21:56 Preparing it and making the use cases work. 08:22:40 While doing so, found some bugs in the evaluator and the subgraph matching and fixed them 08:23:01 I am going to push the fix of those bugs also to stable/ocata 08:23:16 Thats it for now 08:23:22 Great, thanks 08:23:33 So I guess it’s time to move to the Boston topic :-) 08:23:39 #topic Boston Summit 08:24:25 I think there is a problem with openstack bot :-( I don’t see that the topic changed 08:24:32 Anyway… 08:24:42 One forum session was accepted for Vitrage, and I was asked to unite our four proposals into one. 08:24:53 The united session is scheduled in an inconvenient time (right after the collectd session), and so far I failed to move it 08:24:59 #link https://www.openstack.org/summit/boston-2017/summit-schedule/events/18799/vitrage-usability-and-new-insights-where-do-we-go-next?BackURL=https%3A%2F%2Fwww.openstack.org%2Fsummit%2Fboston-2017%2Fsummit-schedule%2Fglobal-search%3Ft%3Dvitrage%23eventid%3D18799 08:25:07 (not sure why this link is so long…) 08:25:17 I’m still working on two presentations: the Vitrage Story and the Vitrage project updates. 08:25:28 Regarding the session with Intel, I got a presentation draft from Maryam Tahhan, need to go over it 08:25:40 I also started working on the demo configuration, and found some bugs 08:26:08 There seems to be a conflict between the static datasource and Nova instance datasource, when trying to reference an instance in the static file 08:26:10 Will check it 08:26:20 Anything else for Boston? 08:27:17 #topic Open Discussion 08:27:22 Any other issue to discuss? 08:27:35 I want to ask progress on use case repository 08:28:01 Right, I saw your mail and didn’t get to answer yet, sorry 08:28:33 We have a few use cases that are working in Nokia product. The problem is that they are specific to the Zabbix configuration that we have. We need to think of the best way to publish them 08:28:51 So far we have made no progress in this area, mainly because we are busy with Boston tasks 08:29:02 Sorry for that 08:29:08 Undertood. Thank you 08:29:53 This issue is still high on our list. But I’m not sure when we will start working on it 08:30:05 It’s not a lot of work, I guess 08:30:48 What was the case about? NFVI ? 08:32:28 But of course the use case repository can hold other use cases that are not NFVI 08:33:39 Anything else? 08:34:05 I lost the answer. What was before the "But" 08:34:18 Yes, I was disconnected.. 08:34:25 Yes. An example use case: if Zabbix reports a high CPU load on the host, we create deduced alarms on the instances that their performance is suboptimal 08:34:29 But of course the use case repository can hold other use cases that are not NFVI 08:34:35 That’s the full answer 08:34:35 I see, thanks 08:35:15 Any other issue? 08:36:05 No from my side 08:36:48 Ok. Bye everyone :-) 08:37:09 bye bye 08:37:14 bye 08:37:21 bye bye 08:37:28 #endmeeting 13:00:08 alex_xu: Error: Can't start another meeting, one is in progress. Use #endmeeting first. 13:00:23 #endmeeting