08:00:30 #startmeeting vitrage 08:00:30 Meeting started Wed Dec 14 08:00:30 2016 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:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:33 The meeting name has been set to 'vitrage' 08:01:11 hi 08:01:15 Hi 08:01:19 o/ 08:01:36 hi 08:01:40 Hi everyone! 08:01:47 Hi guys 08:01:54 hi 08:02:08 hi 08:03:04 #topic Status and Updates 08:03:16 I created a Vitrage RoadMap page under our wiki page. I tried to list all activities we are currently involved in, as well as ones we wanted to do but might not be able to complete in Ocata 08:03:25 #link https://wiki.openstack.org/wiki/Vitrage/RoadMap 08:03:37 Feel free to look, edit, add… and also implement of course if you are free 08:04:14 Besides that, I started working on implementing Vitrage as a Doctor Inspector 08:04:34 The first task is to write tests for Vitrage as an inspector. To complete this task, I first need to write a Doctor datasource in Vitrage, that will implement Doctor SB API 08:04:45 #link https://gerrit.opnfv.org/gerrit/#/c/12179 08:04:57 I plan to write a blueprint and start the implementation in the coming days 08:05:29 The next task would be to add Vitrage installation to OPNFV Apex installer. But to complete this, we need to have Red Hat support 08:05:50 eyalb: any progress with this? 08:06:15 not much progress few more comments were added to the review 08:06:37 ok 08:06:48 Anyone wants to update? 08:07:12 hi 08:07:24 I will updat 08:07:56 we had some gate problems last week due to infra and heat changes, and we fixed them 08:08:18 In addition, I have wrote a blueprint for a custom alarm in Aodh 08:08:19 https://review.openstack.org/#/c/408060/ 08:08:36 I also sent an email to aodh about it 08:08:57 alexey_weyl: I’ve seen it, looks good 08:09:02 but at the moment I dont have any feedbacks from the aodh team 08:09:04 Did they review it alrady? 08:09:35 I will continue to talk with them about it and get their response 08:09:51 thats it 08:09:59 * yujunz reports that static datasource will be ready for review in a few days. 08:10:02 Ok. We need to get their approval, or at least their comments 08:10:25 yujunz: great, thanks 08:10:28 If somebody can help explain how to work with placeholder, it might be accelerated. 08:10:32 yujunz: great! we ware waiting for it 08:10:38 We keep following your changes :-) 08:10:49 no problem, i will explain 08:11:15 And please explain how you wrote the ‘*’ next to your name in *yujunz reports … 08:11:16 Thanks, I'll ask in mailing list 08:11:27 use /me 08:11:46 * ifat_afek thanks 08:11:51 ok, i will wait for your email to explain 08:12:08 * alexey_weyl NICEEEEEEEEEEEEEEE 08:12:16 * alexey_weyl :) 08:12:51 After that, I may continue work on datasource skeleton generator 08:12:58 ok, anyone else wants to update? 08:12:59 If there is no other high priority tasks 08:13:08 i will update 08:13:23 yujunz: sounds great 08:13:57 I actually plan to write a datasource these days, but I guess your skeleton won’t be ready yet 08:14:23 sounds great, I will try to think if there might be some more important issue to work on 08:14:47 Regarding the tasks, I just listed the important ones in the road map page, but of course you can work on whatever is important to you 08:15:16 I guess so, since I need more time to study how datasource works. 08:15:32 of course 08:15:46 yujunz: if you have any questions, just send an email and we will be glad to help you :) 08:16:17 Thank you in advance alexey_weyl and all vitragers 08:17:48 eyalb: you wanted to update? 08:17:55 yes 08:18:24 still working on the collectd datasource 08:18:52 i was able to write a python plugin that will send notifications on the bus to vitrage 08:19:02 now i need to write the vitrage side 08:19:05 thats all 08:19:16 eyalb: sounds great 08:19:19 thanks 08:19:46 anyone else wants to update? 08:21:08 or any other issue to discuss before I close the meeting? 08:21:14 By the way, how do we usually call ourselves? 08:21:21 Vitragers? 08:21:36 That sound nice :) 08:21:38 We never used this term :-) or any other 08:21:44 But I agree it sounds nice 08:21:58 So we can adopt it 08:22:04 Just try to find something to starting a new message in mailing list 08:22:29 That would be a good start indeed :-) 08:22:45 +1 08:23:20 Nope 08:23:40 danoffek: so suggest something else 08:23:58 It's a good start, let's take it to the next level 08:24:16 In doctor project it is easy, we call ourselves doctors :-) 08:24:29 :-) 08:24:32 In QTIP project, runners, since we run benchmarks 08:24:54 And the core module is called runner 08:24:55 Well, so does elisha_rosentzweig 08:24:55 that’s less obvious... 08:25:13 you mean he’s a doctor too 08:25:21 I wonder what Aodh does ;-) 08:25:22 In doctor, it's a good one. 08:26:13 So, the next idea would be "giraffes", but I wouldn't go with a shirt naming me "giraffe" 08:27:03 First we need to convince OpenStack illustrator to design a nicer giraffe than the previous one 08:27:23 And personally I prever Vitragers over Giraffes… 08:27:31 Or root cause digger => diggers 08:27:31 prefer 08:27:51 I root for this idea 08:27:55 Diggers is nicer 08:29:32 Ok, I guess we won’t reach a conclusion today… 08:29:56 yujunz: feel free to call us however you want in your mail :-) 08:30:15 OK 08:30:58 Any other issue to discuss? 08:32:56 Ok, let’s close the meeting 08:32:56 can we design our own giraffe? 08:33:07 nofarsch: Hi! 08:33:18 haha hi 08:33:40 if it takes a long time or there aren't any resources let's just design our own 08:34:04 Unfortunately we can’t. There is one illustrator that designed the mascots of all projects. I sent him an example of what we wanted our giraffe to look like, and he designed something else 08:34:20 I know, we've talked about it 08:34:47 did he respond? 08:34:52 It might be a good idea to ping the woman who organized it, and ask if our feedback was accepted 08:35:11 ok 08:35:12 I didn’t contact him (or her?) directly 08:35:26 and btw about the nickname, I suggest Root causers :P 08:35:34 But thanks for the reminder, we deserve a nice giraffe! 08:35:40 yes we do! 08:35:53 +1 to root causers 08:36:19 now you can close the meeting :) 08:36:24 root root for Nofar 08:36:26 +2 08:36:31 yay! 08:36:36 Ok, closing the meeting 08:36:43 See you next week 08:36:50 bye 08:36:56 bye 08:36:57 bye guys! see you soon 08:37:19 #endmeeting