15:02:03 #startmeeting monasca 15:02:04 Meeting started Wed Jan 16 15:02:03 2019 UTC and is due to finish in 60 minutes. The chair is witek. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:02:07 The meeting name has been set to 'monasca' 15:02:24 hello, sorry for the delay 15:02:31 had connection problems 15:02:33 Hello 15:02:38 hi Dobroslaw 15:03:20 agenda as usual here: 15:03:25 https://etherpad.openstack.org/p/monasca-team-meeting-agenda 15:03:37 just one point today 15:03:53 #topic Python 3.7 support in kafka_lib 15:03:59 I added it 15:04:07 thanks Dobroslaw 15:04:14 What to write to it? 15:04:48 As a response, I don't think we want any updates to this libs 15:05:10 so that is the incubated copy of old version of python-kafka client 15:05:21 Yes 15:05:25 and we want to migrate away from it and deprecate it 15:05:37 or rather remove it completely 15:05:59 Yep 15:06:00 so yes, I agree we should probably not be updating that code 15:06:08 OK 15:06:21 btw. is Python 3.6 working with this code? 15:06:33 Don't know... 15:06:59 I've noticed the Zuul job names have not been updated in monasca-common repo 15:07:14 Hmmm, it should because running this in docker with 3.5 is working 15:07:20 and so the tempest tests had not run for this change 15:07:35 cool, thanks 15:08:39 will you comment on the change? 15:08:47 Yes 15:08:53 cool 15:09:33 #topic OpenStack Summit CFP 15:10:13 who is planning to attend the next Summit + PTG in Denver? 15:10:33 hi joadavis :) 15:11:05 hello 15:11:15 who is planning to attend the next Summit + PTG in Denver? 15:11:42 and/or submit a talk/workshop? 15:11:57 anyone from Fujitsu? 15:12:09 I'll probably connect over the internet 15:12:27 Don't know about others 15:12:50 I haven't discussed it with anyone yet, but I'd like to go 15:12:57 please ask in the team, the deadline for proposals is next week 15:13:46 Ifat from Vitrage has suggested a joined talk and/or workshop on our integration work 15:14:25 workshop should be easy, we have some material both for Monasca and Vitrage already 15:14:52 for the presentation it would be nice to have an interesting use case 15:15:23 if you have any ideas please let me know 15:16:10 the most common example in my mind is an alarm based on cpu usage to spin up a new vm when past a certain level 15:16:28 though there may be a flashier use case we could use 15:19:19 #topic open stage 15:19:34 are there any other topics for today? 15:20:01 One thing 15:20:08 yes please 15:20:15 Adrian is working on coverage 15:20:28 for API I assume 15:20:42 What to do with dead code not used by anything 15:20:49 Probably remove 15:21:10 yes, as part of refactoring 15:21:22 And what to do with code useful for developers but not for deployment 15:21:23 but would not add it to the coverage change :)\ 15:21:31 we likely should deprecate it if following process. but if we can prove it is unused we can remove 15:21:50 Should we "hide" it from coverage@ 15:22:02 ? 15:22:04 what do you mean in detail? 15:22:10 do you have some example? 15:22:31 Sorry, I'm on phone now and don't have anything to show... 15:22:57 He was talking today something about repl 15:23:25 For debugging 15:23:27 I think we could start with submitting the change and ask questions in review 15:23:33 OK 15:23:50 I have very little time for reviews this week 15:24:03 but want to improve next week 15:24:09 I also am limited, but should make more time soon 15:25:05 I think change for notification with moving plugins is blocked by merge conflict 15:25:18 I've seen that one 15:25:29 dougsz: is not there today 15:25:47 should not be difficult I guess 15:27:05 I think if someone has some spare cycles, can try to solve the conflicts and push the patch 15:27:29 I will look into this tomorrow 15:27:42 that'd be great 15:29:00 anything else? 15:29:32 if not I'll be wrapping up 15:29:40 thank you Dobroslaw 15:29:44 thanks joadavis 15:29:58 see you next week 15:30:04 Thx 15:30:04 thanks 15:30:06 #endmeeting