19:09:02 #startmeeting openstackclient 19:09:03 Meeting started Thu Mar 17 19:09:02 2016 UTC and is due to finish in 60 minutes. The chair is stevemar. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:09:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:09:07 The meeting name has been set to 'openstackclient' 19:09:21 dtroyer, dhellmann, stevemar, terrylhowe, lhcheng, dstanek, rtheis, MeganR << ping for osc meeting 19:09:44 * dhellmann listens partially 19:10:37 i think osc is long overdue for a bug triage 19:11:02 but that's aside the point 19:11:15 let's do reviews / bugs / open discussion 19:11:26 * stevemar pokes rtheis 19:11:52 bug triage ... yes that would be good 19:12:16 sorry, I was drifting off to a review 19:12:19 rtheis: we could do it together at the summit, or maybe all go on hangouts and do it together 19:12:25 rtheis: it's all good :) 19:12:29 #topic reviews 19:12:38 rtheis: speaking of reviews, any you have in mind? 19:12:51 any i should put on my queue that are ready to go? 19:13:03 https://review.openstack.org/#/c/292541/ 19:13:19 ah yeah 19:13:24 i saw that earlier 19:13:32 i still want to create a basic osc plugin package 19:13:34 Trying to better understand OSC plugin for neutron stadium transition 19:13:57 it just works (TM) 19:14:20 what would the osc plugin package contain? 19:14:39 everything under common and tests/common 19:15:09 rtheis: i hadn't updated it in a year :( https://github.com/stevemart/osc-base 19:16:04 Idea is for plugins to include that in requirements.txt? 19:16:06 rtheis: a lot of projects/plugins ended up either calling osc.common.utils.find_resource or... copying and pasting the entire thing 19:16:28 yeah, include osc-base in requirements instead of full OSC 19:16:34 (for a plugin) 19:16:44 I've seen a mix of plugins including OSC in requirements, test-requirements or neither 19:16:45 so they don't pull in every single dependency we do 19:16:55 yeah, thats dangerous 19:17:04 what should be done today? 19:17:09 maybe dhellmann has some thoughts on that? 19:17:25 rtheis: i think plugins should be listing it in requirements 19:17:36 ok 19:17:37 but jeez that is a huge dependency 19:18:07 yes 19:18:10 sure is the simplest thing to do; it would confusing if osc was installed without something and someone tried to use it 19:18:34 I wrote a plugin a while back and that is what I did 19:18:41 thats the other side... all these plugins *need* osc to work 19:18:54 so... they should like osc as a dependency 19:19:00 yeah, listing osc in the requirements for a plugin makes sense 19:19:12 it also gives them a place to declare the version of osc they work with 19:20:01 dhellmann: yeah, i should send an email blast to all osc plugins telling them to do that 19:20:10 stevemar : ++ 19:20:33 #action stevemar to send mailing list blast to osc consumers 19:20:48 what... action didn't work.. damn 19:20:56 oh well :) 19:21:23 if folks go and use osc in requirments.txt then creating an osc_base package is pointless 19:21:46 rtheis: any other reviews? 19:21:53 nothing else 19:22:18 i think i had one... 19:22:31 we've got https://review.openstack.org/#/c/276350/ chalked up 19:22:51 apparently it needs a new KSA release to work 19:23:33 but we can't release that til after RC period happens 19:23:38 important stuff, but broken atm 19:24:01 terrylhowe: rtheis i think once that merges we'll have to do a major version bump 19:24:14 and warn everyone that things may not be backward compatible 19:24:32 probably a good idea stevemar 19:24:35 i'm wondering if we can rename our project at the same time :D 19:24:44 drop the python- 19:24:49 stevemar: seems like that patch set should have a release note then 19:24:58 rtheis: oh for sure 19:25:54 rtheis: hehe, thanks for the comment on the patch 19:26:00 yw 19:26:20 i think there is more to be removed, mordred had a similar patch 19:26:30 https://review.openstack.org/#/c/225318/1 19:28:23 anyone brave enough to tackle that patch? :) 19:29:21 not I :) 19:29:32 damn 19:29:41 #bugs 19:29:44 #topic bugs 19:29:48 https://review.openstack.org/#/c/276350/ would go in first ? 19:29:51 any major bugs to talk about? 19:29:57 then https://review.openstack.org/#/c/225318/ ? 19:30:06 rtheis: i believe the two are doing the same thing 19:30:27 ok 19:31:15 I don't have any major bugs to discuss 19:31:29 the bugs looks mostly OK 19:31:40 i somewhat regret going along with the bug per command 19:31:49 its creating a lot of bugs :) 19:31:51 yeah 19:32:08 the only reason I started that is so people could jump in and work on things 19:32:10 hopefully that should be wrapping up for network 19:32:18 but.. it's alright, everyone is kinda working on them, so it's cool 19:32:37 yeah, of all the problems to have it's one i can live with 19:32:50 #topic open discussion 19:32:57 anything else? 19:33:23 i think by now dtroyer has the info on the amount of workrooms/ fishbowls / meetups we'll have at the summit 19:33:36 and any other summit-y details 19:33:53 stevemar: do you know the schedule for those ? 19:34:11 rtheis: not yet, probably won't come out for another week or two 19:34:19 ok 19:34:22 i haven't been told anything for keystone yet 19:34:39 oh sheel is still working 19:34:47 that's not good, it's super late for him 19:34:56 he is trying to fill the gap for cinder commands 19:35:10 stevemar: hey 19:35:18 sheel: hey! 19:35:25 sheel: we have the openstackclient meeting at this time 19:35:36 yeah, looks of good stuff going in these days 19:35:37 sheel: it's super late for you :\ 19:35:44 * lots 19:35:53 stevemar: yeah 19:36:10 I don't have any other topics 19:36:12 sheel: did you have anything you wanted to chat about ? i don't want to keep you up unnecessarily 19:36:29 stevemar: I think no 19:36:40 stevemar: thanks 19:36:41 sheel: alright, i'll just review your patches :) 19:36:48 stevemar: thank you... 19:36:51 :) 19:36:51 np 19:37:07 terrylhowe: rtheis: anything else? 19:37:13 nope 19:37:20 we can cut this early and throw tomatoes at dtroyer for skipping 19:37:31 nothing here :) 19:37:57 alright, proceed with pelting our ptl with plump tomatoes 19:38:00 #endmeeting