22:00:19 #startmeeting Solum Team Meeting 22:00:20 Meeting started Tue Oct 14 22:00:19 2014 UTC and is due to finish in 60 minutes. The chair is adrian_otto1. Information about MeetBot at http://wiki.debian.org/MeetBot. 22:00:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 22:00:23 The meeting name has been set to 'solum_team_meeting' 22:00:23 #link https://wiki.openstack.org/wiki/Meetings/Solum Our Agenda 22:00:29 #topic Roll Call 22:00:32 Adrian Otto 22:00:33 Ed Cranford 22:01:29 hi datsun180b 22:01:34 howdy 22:01:36 Dimitry Ushakov 22:02:10 o/ 22:04:13 hi dimtruck and PaulCzar 22:04:25 is Devdatta joining us today? 22:05:29 I think he's travelling home ? 22:05:37 ok, then let's begin 22:05:37 so he might join from there 22:05:44 #topic Announcements 22:05:50 upcoming meetings. 22:06:00 We have a bunch of Tuesdays with interesting things happening 22:06:10 next tuesday I will be out on vacation. 22:06:39 the Tuesday after that (Oct 28) I will be speaking at Zendcon 22:07:13 oh i'll be out next tuesday too 22:07:36 the Tuesday after that we are at the Paris summit (Election Day) 22:07:59 the Tuesday after that is Veterans day 22:10:29 Sorry, my internet connection was interrupted by local construction work here at my office. So, it might make sense to think about the upcoming schedule 22:10:50 which meetings to hold with an alternate chair, and which ones to skip (if any) 22:11:20 let's start with 2014-10-21. Is there a team member who would like to hold and chair that meeting? 22:12:06 anyone still with me? 22:12:11 just me! 22:12:13 I'm here 22:12:19 me too 22:12:22 ok, good, thanks guys. 22:12:40 i can do it 22:12:45 on 10-21 22:12:46 I already said I'm out next Tuesday 22:13:09 ok, any objections to dimtruck acting as chair on 2014-10-21? 22:13:17 I won't be available to attend or chair 22:13:28 #agreed dimtrruck will be our chair on 2014-10-21 22:13:32 yay! 22:13:41 ok, how about 2014-10-28 22:13:43 thanks dimtruck 22:13:48 that's the week before the Summit. 22:14:02 i nominate devdatta to run it 22:14:13 i'd second if he were here to accept it 22:14:31 well, we can just put that on our agenda for next week 22:14:51 and you can decide at that point whether to hold it or cancel it, and if we hold it who will run it. 22:15:04 I propose we skip the week of the Summit 22:15:23 i don't think anyone will disagree with you 22:15:27 and then regroup the week after that, ignoring the fact that it's a holiday for some. 22:15:49 ok, any other announcements from team members? 22:16:22 gil said he'd be 20 minutes late; i imagine this meeting might end before he gets here 22:16:30 #topic Review Action Items 22:16:33 he had two things that might count more as actions though 22:16:36 * adrian_otto1 adrian_otto to ask on ML if current Solum contributors would like to explore adjusting our meeting schedule, or keeping it the same. 22:16:45 Status: Incomplete 22:16:52 I will carry this forward on the agenda 22:17:02 #action adrian_otto to ask on ML if current Solum contributors would like to explore adjusting our meeting schedule, or keeping it the same. 22:17:22 we can revisit this topic in action item review on the 21st. 22:17:30 I will be on an airplane at that time 22:17:53 #topic Blueprint/Task Review 22:18:14 Does anyone have specific work items they would like to raise for team discussion 22:18:21 Yes, one from Gil: 22:18:24 #link https://review.openstack.org/#/c/126748/ 22:18:33 he's rebased his CAMP review on recent master 22:19:03 I need to rebase this again - https://review.openstack.org/#/c/102646/ 22:19:03 ok 22:19:22 I've been busy on other rax stuff and haven't had the time to test it thoroughly again 22:19:26 Oh and he also wanted me to ask about "devdatta was supposed to open a bug about the fact that the Accept header handling for json vs. yaml on the plan resources didn't comply with HTTP" 22:20:20 also need to find new owners for https://review.openstack.org/#/c/103937/ and https://review.openstack.org/#/c/119955 22:20:28 or abandon them 22:21:17 so I voted on Gil's patch 22:21:21 next is: https://review.openstack.org/102646 22:21:36 that's in merge conflict which will presumably clear once you rebase, right PaulCzar? 22:21:42 correct 22:21:53 ok, so we will defer to your action on that one 22:21:58 but its old enough probably need to do a thorough test through it 22:22:01 back 22:22:33 gpilz: you got half your +2s looks like 22:22:37 working on a deploy to our production solum environment tomorrow ... after that can spend time on it. 22:22:38 next is https://review.openstack.org/103937 22:22:50 seeking a new owner 22:23:22 any takers? 22:23:25 friendliness eh 22:23:43 PaulCzar: I suggest you put a comment on it putting it up for adoption 22:23:53 and if nobody picks it up, then I will abandon it for you 22:23:55 will do 22:24:07 as long as it doesn't get abandoned it won't go anywhere, and any of us can add new patches to it 22:24:14 taht's a new power that cores now have (since recent Gerrit upgrades) 22:24:34 I can own it (just had to read through it) 22:25:04 next is: https://review.openstack.org/119955 22:25:28 that one can probably be abandoned, there's not a lot of meat to it 22:25:53 yes, that sounds like the right approach to me. Any alternate views to hear on this topic? 22:26:36 ok, any further discussion on work items? 22:27:10 gil's here now but his other item was about our Accept handler 22:27:11 #topic Cutting Juno Release 22:27:33 datsun180b: that did not make it on the agenda, so we can hear that in Open Discussion 22:27:47 just doing what i promised 22:27:52 this is the time in the cycle where I tag a release 22:27:55 thanx 22:28:12 does anyone have a problem with tagging what we have in the repo right now? 22:28:41 I'll move for a #agreed to tag our release, and begin focus on Kilo 22:28:46 thoguhts? 22:28:47 weeeeell dimtruck and i are actively working on a bug with using shelve 22:29:05 namely that if you try it it will fail and you will cry 22:29:23 datsun180b: when would be a reasonable expectation to have a fix merged? 22:29:34 would it be about this time next week? 22:29:37 sooner or later? 22:29:37 oh easy 22:29:51 i'll have to ask him, i think it's already logged on LP 22:29:51 ok, so we can regroup on it when I return to work next wednesday 22:30:00 and we'll have the release cut prior to Paris 22:30:04 aaaaand my unit test fix works, shipping shortly 22:30:37 ok, I am also around tomorrow, but might be scheduled a bit tight to fit that in 22:30:49 anyone opposed to preparing our release on Oct 22? 22:31:22 ok, I'll mark my calendar accordingly 22:31:35 #topic October Elections 22:31:52 it's time to decide if we will hold an election 22:32:18 or set a deadline for challengers to file a statement of intent to run for election 22:32:39 for our PTL 22:33:01 thoughts on this? 22:33:09 Do you intend to run? 22:33:16 yes. 22:33:38 all righty 22:34:02 what about we hold an election the week before the summit, and require statement of intent the week before that 22:34:06 which is probably next week ? 22:34:13 if we repeat what we did last time, we just need to set an open period where candidacy emails will be recognized 22:34:23 and if no challengers emerge, then no election is required. 22:34:31 sounds good 22:35:34 ok, so we can have the open period until Oct 27 at UTC 0:00. 22:35:43 oh, actually 22:36:17 that shold probably be Oct 21, if there is a challenger, then campaign can be until Oct27, and election on Oct 28. 22:36:28 +1 ship it 22:36:32 agree 22:36:46 ok, any disagreement? 22:37:38 #action adrian_otto to email ML for open candidacy until Oct 21 UTC 0:00 for PTL challengers (consistent with rules form last election period) 22:38:12 and we can declare an election date if there are any challengers by the deadline 22:38:27 as our team meeting will follow the deadline on the same day 22:38:33 ok 22:38:37 #topic Open Discussion 22:38:47 Gil, you have something for us about Accept headers 22:38:52 yes 22:38:57 sorry to be so disorganized 22:39:06 np 22:39:28 there was a patch that made it possible to receive plan resources in either JSON or YAML 22:39:40 I don't have the change number on me 22:40:31 I was reviewing it with devdatta and noticed that the code didn't properly implement RFC 2116 22:40:53 devdatta made the case that we should let the patch go, and file a bug against it later 22:41:00 i'm trying to figure out where we are in that process 22:41:44 ok 22:41:54 so, I"m not aware of such a bug 22:42:00 but I can take a look 22:42:03 #link https://review.openstack.org/#/c/115685/3 and down that chain 22:42:13 any links to bugs in there? 22:42:32 #link https://launchpad.net/bugs/1331093 22:42:33 Launchpad bug 1331093 in solum "Plan API should return json/yaml as accept header specifies" [Critical,In progress] 22:42:45 so this hasn't been merged yet? 22:42:52 datsun180b: thanks! 22:42:53 looks like it's open 22:43:04 yep 22:43:16 ping Pierre for current status 22:43:20 okay 22:43:27 can I pick this up and finish it? 22:43:47 once you touch base with him, and offer, that is allowed 22:43:53 okay 22:43:54 thanks 22:43:57 our only concern should be not to interfere with his active work 22:44:16 based on the age of this, tht risk is pretty low 22:44:33 Any other business for today? 22:44:53 got that bugfix for shelve in 22:45:00 * datsun180b dusts hands off 22:45:03 whoot! 22:45:08 well done datsun180b 22:45:28 ok, let's wrap up 22:45:35 thanks everyone! 22:45:38 thanks everyone for attending 22:45:38 thanks! 22:45:46 #endmeeting