09:02:18 #startmeeting ptl_sync 09:02:19 Meeting started Tue Mar 24 09:02:18 2015 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:02:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:02:22 #topic Heat 09:02:23 The meeting name has been set to 'ptl_sync' 09:02:32 #link https://launchpad.net/heat/+milestone/kilo-rc1 09:03:08 OK, so objective for today is to make sure all things here are blockers before we can do a RC1 09:03:08 * asalkeld updating a bp state 09:03:19 Let's start with blueprints first 09:03:33 ok 09:03:33 So you have two exceptions left 09:03:50 Did you have anything requested on-list left unadressed ? 09:04:05 or is it the complete set here ? 09:04:14 that's it 09:04:29 https://blueprints.launchpad.net/heat/+spec/convergence-push-data 09:04:39 that is very close 09:04:43 and one patch 09:04:45 https://review.openstack.org/#/c/161306/ ? 09:04:58 yip that's it 09:05:00 Cool, so that one whould be done by end of week 09:05:10 totally' 09:05:22 the mistral one is more work, but it's in contrib/ 09:05:26 #info convergence-push-data one patch away, to be completed before EOW 09:05:39 We still need it for RC1 though 09:05:53 so if it makes it great, and if not - I am not overly stressed 09:06:09 #info mistral-resources-for-heat is contrib/, not really blocking RC1 09:06:19 agree 09:06:52 Bugs now... Is this list the result of deferring previously-targeted work, or an analysis of all current issues reported ? 09:07:09 i.e. did you go through all bugs and target those ? 09:07:14 ttx: what i did was go through ALL High bugs 09:07:34 and either target for rc1, or move to lower priority 09:07:43 ok 09:07:48 so those could change 09:08:09 but i thought it was good to highlight high priortiy bugs 09:08:12 You need to have assignees on all of them, otherwise it's unlikely they will get done for RC1 in any reasonable timeframe 09:08:23 ok, i'll chase that 09:08:40 #info 26 bugs targeted 09:08:42 i should probably ditch some 09:08:58 yeah, it's a bit of a large list ,for a blockers list 09:09:08 ok, i'll get stuck in 09:09:18 You can use kilo-rc-potential as a tag to build an extra list of nice-to-have 09:09:31 and keep rc1 targeting as a blockers list 09:09:39 ok, good idea 09:09:58 That way we use the RC1 page as a timer... when all is completed we know we could do a RC1 09:10:09 but then people can pick and fix bugs from the rc-potential list too 09:10:18 aaa, like a backlog 09:10:39 will do 09:10:45 it's more of a "must-fix" vs. "should fix" thing 09:10:57 ok 09:11:04 If you deplete the must-fix list too quickly, we can add more "should-fix" to it, too :) 09:11:21 lets hope we get to hat 09:11:23 that 09:11:41 asalkeld: the game is usually more like... every week you remove half of the remaining ones from the blockers list 09:12:04 but ideally that would be must-fix and should-fix 09:12:07 either re-target or fix 09:12:22 thanks ttx 09:12:38 so yes, on the bugs side, please assign people, reduce it to real release blockers, and build a backlog list using the tag 09:12:55 We'll see how that number progresses next week and how fast we burn them down 09:13:10 asalkeld: have a nice day! 09:13:15 (or night) 09:13:17 you too ttx 09:13:22 johnthetubaguy: hi! 09:13:36 ttx: good morning 09:13:40 #topic Nova 09:13:46 #link https://launchpad.net/nova/+milestone/kilo-rc1 09:14:24 I'm admirative of that small list of BPs, but I suspect that's not including all the requests you had on the list 09:14:43 Is there any we should discuss the addition of ? Or you turned them all down already ? 09:14:54 * ttx admits not having parsed the FFE requests from the ML yet 09:15:06 hey, sorry, lots my IRC connection there 09:15:29 what's the last thing you had ? 09:15:59 I saw small list of BPs 09:16:03 and is there any others 09:16:09 then you mentioned the ML 09:16:17 johnthetubaguy: my question was, is that list the complete list of FFEs or should we discuss any addition ? 09:16:54 Can't find any on the ML actually, so I guess the "soft FF at k-2" worked 09:16:57 so I don't know of any others, we are basically not advertising that its possible to get an exception very well 09:17:17 yeah, it has slowed things down at least 09:17:24 I think the list is good for now, basically 09:17:30 https://blueprints.launchpad.net/nova/+spec/online-schema-changes 09:17:56 pending on https://review.openstack.org/#/c/154521/ ? 09:18:07 yes, thats the only patch for the BP basically 09:18:21 I need to talk to johannes about that one to check what his plans are 09:18:29 Looks like reviewing has stalled on this one 09:18:35 (lacking new patchset) 09:18:44 I know he is busy on other things, so I need to ask what could be moved 09:19:06 also feels like something you wouldn't want to merge at the last minute 09:19:14 I will push on that, its something we all want merged if possible 09:19:34 I'm fine with it, but it needs to land earlier rather than later 09:19:50 needs testing 09:19:52 its a parallel execution path that will be experimental, but yes, needs to land, ASAP 09:19:59 hmm 09:20:12 if it's really parallel and experimental, I guess it's not /that/ urgent 09:20:25 yeah, its basically like an alternative way to do migrations 09:20:29 I misinterpreted it 09:20:33 you can use it, or the old way, both work 09:20:44 (but then, it's not the first time you tell me about it, I just keep on forgetting) 09:20:46 (and they lock each other out) 09:20:59 no worries, its low ish risk, anways 09:21:10 the other one is very different... 09:21:19 https://blueprints.launchpad.net/nova/+spec/v3-api-policy 09:21:56 Right, this one seems like a collection of poatches that are easier to land individually, but loads of them 09:22:04 Also unclear if that can be "finished" 09:22:41 so… I think we might want to mark this complete, and stop the review on the other things today ish 09:22:55 mostly, as you say, not sure it will get finished 09:23:09 At the very minimum we need to set a deadline 09:23:25 Like : review and merge before Thursday, rest is deferred 09:23:45 I am good with that 09:24:04 I will try reach out and ask them to abandon the stuff thats not very close 09:24:06 That gives the people working on it a last chance to scramble on reviews 09:24:32 not sure how much it makes sense as partial work 09:24:57 Looks like a cleanup 09:25:09 yeah, some is just cleanup 09:25:13 enforce at API layer rather than DB 09:25:22 yeah, its moving checks 09:25:36 basically means the v3 policy will eventually all be easy to understand 09:25:58 but we are not there yet, even if we merge all the patches that are up 09:26:02 ok, let's give tyhem two more days and then call the partial work complete 09:26:02 as I understand it, anyways 09:26:19 That way we should be done with FFEs (except shit happens) at EOW 09:26:28 which is pretty good compared to previous occurences 09:26:56 yeah, sounds good 09:26:59 Then there is work to do on the RC bug list 09:27:15 ah, yes, I did ask folks to start looking for blockers 09:27:19 Did you do a pass on the critical/high issues yet ? Or is the current list the result of deferrals ? 09:27:35 I honestly haven't dug into that yet 09:27:50 For example, there is no point in keeping in the list work that was deferred successively since juno-2 09:27:57 agreed 09:28:14 except for the embarrassing one we want someone to fix, but we best find someone to fix it 09:28:24 I'd rather have realistic blockers, and keep unlikely fixes in the kilo-rc-potential list 09:29:13 embarassing one = https://bugs.launchpad.net/nova/+bug/1383465 09:29:14 Launchpad bug 1383465 in OpenStack Compute (nova) "[pci-passthrough] nova-compute fails to start" [Critical,In progress] - Assigned to Yongli He (yongli-he) 09:29:14 ? 09:29:23 yes, thats the one 09:29:26 I think we could unassign it 09:29:32 that would reflect better the situation 09:29:34 yeah, thats a good idea 09:29:38 I'll do it 09:30:09 ah, done it 09:30:26 the tag is kilo-rc-potential right? 09:30:42 so I guess everything targeted is a blocker, stuff with the tag could be a blocker 09:30:48 OK, so objectives for this week -- finalize both FFE, build a list of must-fix in rc1 and good-to-fix in kilo-rc-potential 09:31:22 gotcha 09:31:25 sounds good 09:31:33 that is alml, have a great week! 09:31:35 all* 09:31:51 cool, thanks, and you 13:00:04 ttx: ready when you are 13:00:17 #topic Ceilometer 13:00:31 #link https://launchpad.net/ceilometer/+milestone/kilo-rc1 13:01:00 So if I'm to trust that list you have no exception yet 13:01:17 yeap, so nothing critical as yet and obviously no FFEs 13:01:31 good all around 13:01:43 what date-ish did you have in mind for the rc1 tag? 13:01:44 Did you parse the bug list into a set of blockers ? 13:02:01 or are those carried-over from k3 ? 13:02:10 mostly carry-overs 13:02:28 So I'd say starting next week we can start tagging RC1s 13:02:44 you need to go through the bug list to make sure there are no leftovers 13:02:57 and then refine the list so that it's actually RC1 blockers there 13:03:12 then when the list is empty we can tag RC1 and carry on with our liberty lives 13:03:13 sure, cool 13:03:26 so next week a bit earlier than envisaged by https://wiki.openstack.org/wiki/Kilo_Release_Schedule ? 13:03:44 or just getting ahead for the project that we can? 13:03:45 The release schedule shows the likely dates 13:04:02 a-ha, k 13:04:04 RC1 is tagged when all known issues are fixed :) 13:04:15 all (significant) known issues 13:04:29 so we just need to be reasonably sure it's good 13:04:37 cool, got it 13:04:41 and parsing the bug list is the first step to gaining that confidence 13:05:02 cool, I'm on it :) 13:05:11 so by next week, we'll reduce the RC1 buglist to real blockers, you can move oithers to kilo-rc-potential to keep them somewhere 13:05:28 ("kilo-rc-potential" tag) 13:05:51 that's a good "nice-to-fix" list 13:06:08 cool, got it 13:06:25 That's all I had -- easy when no FFE :) 13:06:34 then post-RC1, only release-critical fixes, right? 13:06:51 post-RC1, we need some critical issue to open a new RC window 13:06:59 (so slight incentive there not to rush into rc1 earlier?) 13:07:07 then we can pile up a reasonable amount of other fix backports 13:07:19 eglynn: I wouldn't say that... 13:07:31 You need some significant bug to fix to make it worth the pain 13:07:44 but then you can collect bugs that are fixed in master and backport them easily 13:08:21 cool, got it 13:08:25 so, yes, no rush obviously, but "minor" bugfixes can get it in future RCs alright 13:08:37 especially if you're far from release date 13:09:10 the trick is to have at least one RC you can fall back to and release on common release date 13:09:28 cool, makes sense 13:09:41 alright, have a good week! 13:09:58 SergeyLukjanov: ready when you are 13:10:40 ttx, hi 13:10:43 ttx, I'm here 13:10:44 #topic Sahara 13:10:45 you too, thanks for your time! 13:10:50 #link https://launchpad.net/sahara/+milestone/kilo-rc1 13:10:57 I see 3 FFEs in your future 13:11:19 Is that the complete list at this point ? 13:11:23 ttx, correct, no new FFEs expected, current ones are pretty near to be done 13:11:32 ok, let's have a look 13:11:38 https://blueprints.launchpad.net/sahara/+spec/add-timeouts-for-polling 13:11:49 one more patch ? 13:12:00 1 CR left 13:12:01 yup 13:12:06 #info add-timeouts-for-polling -- one more patch, to be completed before EOW 13:12:31 https://blueprints.launchpad.net/sahara/+spec/default-templates 13:12:46 6 easy patches ? 13:13:14 ttx, yeah, we're now ensuring that stuff done in the same way for all plugins 13:13:20 #info default-templates -- 6 easy patches, probably complete by EOW 13:13:34 https://blueprints.launchpad.net/sahara/+spec/edp-job-types-endpoint 13:14:11 Is taht one or two more patches ? 13:14:14 ttx, 1 important CR left (MapR) 13:14:36 https://review.openstack.org/#/c/166494/ looks further away 13:14:42 ttx, few more patches preferred but we'll accept them only if done before EOW 13:14:55 ttx, it's preferred but optional 13:15:10 #info edp-job-types-endpoint -- one patch almost there, one optional patch, to be completed before EOW 13:15:22 OK, looks under control 13:15:41 ttx, yup, it's going as expected 13:15:52 20 bugs on the RC1 list, is that the result of a bug scrub, or just the carry-overs from previous milestones ? 13:16:02 ttx, no topics from my side for today's cross project 13:16:11 ttx, carry-overs 13:16:30 Would be good to do a bug scrub and target the release blockers instead 13:16:42 and move optional nice-to-haves to kilo-rc-potential tag 13:17:00 So that by next week we know how far from RC1 we actually are 13:17:11 ttx, ack, I'll ensure list cleaned up by EOW 13:17:24 ttx, there a lot of docs related bugs in the list 13:17:24 sounds good. Have a great week then 13:17:26 and test 13:17:37 ttx, thank you! you too 13:17:52 cheers! 14:25:22 mestery: I have a call at our usual time (last week before DST here), so if we can talk now, the better 14:25:44 ttx: I'm running the neutron meeting now, lets see if I can multi-task. Go! 14:25:54 #topic Neutron 14:26:09 #link https://launchpad.net/neutron/+milestone/kilo-rc1 14:26:27 So that is more FFEs that I'd like to have 14:26:38 YEs, we're discussing them now 14:26:38 the two IPAM ones I just moved out 14:26:40 We're working our way down the list 14:26:47 I guess meeting in an hour would have been better ;) 14:26:48 ok, maybe I should talk to you later then :) 14:26:50 as I'd have more info 14:26:56 yeah, I guess that makes more sense 14:26:59 Either later today or tomorrow? 14:27:01 Your choise 14:27:18 later today should be fine, will ping you 14:27:26 #undo 14:27:27 Removing item from minutes: 14:27:30 #undo 14:27:31 Removing item from minutes: 14:27:38 Thanks ttx! 14:27:40 oooh. Multiple undoi levels! 14:27:47 lol 14:28:02 wasn't sure that would work. Meetbot is already smarter than Word 95 14:28:38 nikhil_k: interested in going now ? 14:28:48 ttx: yes 14:28:50 hi 14:28:52 #topic Glance 14:29:03 #link https://launchpad.net/glance/+milestone/kilo-rc1 14:29:22 So I see two FFEs, is that the complete list you have ? 14:29:46 yes 14:30:17 Your email mentioned pass-targets-to-policy-enforcer, that was moved out, right? 14:30:35 ttx: yes, that is implemented 14:30:48 https://blueprints.launchpad.net/glance/+spec/pass-targets-to-policy-enforcer 14:30:56 oh, back in k3, nice 14:31:00 Let's look at those remaining ones 14:31:06 https://blueprints.launchpad.net/glance/+spec/artifact-repository 14:31:22 Is that waiting on https://review.openstack.org/#/q/topic:bp/artifact-repository,n,z ? 14:31:27 yes 14:31:54 How far is it ? Keeping such a large feature non-landed is concerning 14:32:23 and I don't see a lot of progress lately 14:32:40 I'm trying to get people to review it and review myself 14:33:04 It's been discussed and talked over for months so, I think we will go with it for now 14:33:14 I can update you more on Thursday 14:33:15 Right, I would prefer not to have the same discussion in one week 14:33:25 ok sure 14:33:30 So let's give it one more week. If it can't land then, it never will 14:33:47 ok, thanks for letting me know 14:34:00 #info artifact-repository a bit lagging, must land before next Tuesday or we'll defer 14:34:14 https://blueprints.launchpad.net/glance/+spec/catalog-index-service 14:34:41 That one also seems to be lagging -- feature is slightly less critical, but still 14:35:13 I'm inclined to give it the same rule 14:35:23 to be merged befor 14:35:28 e next Tuesday 14:35:32 (sure) 14:36:08 #info catalog-index-service a bit lagging too, must land before next Tuesday or we'll defer 14:36:32 Once that is covered we need to build the RC1 buglist 14:36:49 sounds good 14:36:54 i.e. you should parse bug lists and see what should be blocking release and RC1 14:37:14 all the nice-to-haves could be tracked using kilo-rc-potential instead 14:37:15 roger 14:37:20 so that we only have blockers in the RC1 list 14:37:34 so ideally we'd have that list at our sync next week 14:37:48 but you may be distracted by those FFEs in the mean time 14:37:55 (one of the reasons those are harmful) 14:38:02 do what you can :) 14:38:12 heh, thanks 14:38:31 nikhil_k: have a good and busy week :) 14:38:44 ttx: :) 14:38:53 ttx: have a nice one yourself! 14:38:59 david-lyle: interested in talking now ? 14:39:20 or we can do our usual time, my call should be over by then 14:49:23 ttx: ready, if now works 14:50:02 david-lyle: o/ 14:50:06 #topic Horizon 14:50:20 https://launchpad.net/horizon/+milestone/kilo-rc1 14:50:35 I see 3 FFEs, any more on the (heh) horizon ? 14:50:57 1 possible for SSO with Keystone, fairly small change 14:51:21 would be great to have but needs a little more work 14:52:01 link? 14:52:08 I can add it, and remove if we can't get it in shape 14:52:10 finding 14:52:18 yes, add it and we'll review it now 14:52:48 https://blueprints.launchpad.net/horizon/+spec/federated-identity 14:53:00 added in 14:53:11 keystone folks will be happy 14:53:13 how far is this one ? 14:53:29 patches are up, horizon side needs a couple of fixes 14:53:30 is that only those two patches ? 14:53:45 django_openstack_auth pieces needs another round too 14:53:47 yes 14:53:52 I'm fine with cutting some slack to horizon since you need to play catch-up with features all the time 14:54:17 ok, I'll work with keystone to get them finalized 14:54:26 Is that something you think could land before our next sync ? 14:54:36 I would hope so 14:54:43 especially the horizon side 14:54:55 #info federated-identity -- late feature catch-up, ideally would merge before Tuesday next week 14:54:59 just very small issues on that piece 14:55:05 https://blueprints.launchpad.net/horizon/+spec/django18 14:55:21 that is a testing in the gate issue 14:55:25 the patch is in Horizon 14:55:43 so at worst, global requirements doesn't include Django > 1.6 14:55:52 and people use it anyway 14:56:03 so we could consider this one complete, just badly tested until we get our s*t together ? 14:56:23 well it's misleading because we can't update global-requirements 14:56:26 but yeah 14:56:27 I'm inclined to consider it implemented and log a RC1 bug about testing 14:56:33 it could be a line in the release notes 14:56:46 which we could turn into a release note if we can't fix it, yes 14:56:53 let's do that 14:57:08 ok, I'll update and add bug 14:57:17 https://blueprints.launchpad.net/horizon/+spec/angularize-identity-tables 14:57:39 hmm, a bit unclear what that hinges on 14:57:48 that still has a little more work on getting the patch in order 14:57:58 lots of patches marked WIP in https://review.openstack.org/#/q/topic:bp/angularize-identity-tables,n,z 14:58:22 I'm inclined to give it one more week, do you think that's doable in that timeframe ? 14:58:59 I think so 14:59:27 Really only one patch, the others are small utilities and I just -2'd one that was attached incorrectly 15:00:08 #info angularize-identity-tables -- needs to be finalized before next week 15:00:17 https://blueprints.launchpad.net/horizon/+spec/fwaas-router-insertion 15:00:20 the WIP should be removed from the commit messate 15:00:38 late feature in neutron 15:00:53 ack, let's put it in the same bucket as the first one 15:00:53 amotoki is reviewing and I will as well 15:00:59 sure 15:01:06 #info fwaas-router-insertion -- late feature catch-up, ideally would merge before Tuesday next week 15:01:25 quick look at the buglist 15:01:36 I think most of those are carry-overs 15:01:49 would be good to refine it to a manageable list of blockers 15:02:04 even if that means tagging kilo-rc-potential all the nice-to-haves 15:02:11 yes, none of those are blockers at this point 15:02:21 I'll clean up the list 15:02:29 ack 15:02:36 david-lyle: thanks! need to run 15:02:47 thanks 15:40:15 thingee: o/ 15:40:29 Got time to sync now? 15:41:18 ttx: yes sorry. I joined the room and didn't notice weechat was lagging. Got dropped from the wifi :( 15:41:33 no pb, was on a call anyway :) 15:41:37 #topic Cinder 15:41:49 https://launchpad.net/cinder/+milestone/kilo-rc1 15:41:57 That's an easy one, no FFE so far 15:42:16 apart from the driver unremovals, did you have any FFE request ? 15:42:17 ttx: not much targeted yet. Started triaging yesterday to make sure nothing big is missing 15:42:26 nope 15:42:48 sounds all good to me 15:56:02 mestery: I'm around now if you are 15:56:12 ttx: Ack, lets get this party started! :) 15:56:17 #topic Neutron 15:56:26 #link https://launchpad.net/neutron/+milestone/kilo-rc1 15:56:34 so... 7 15:56:40 Down to 9 specs, 2 of which are vendor drivers 15:56:41 Yes 15:56:42 That's more reasonable, but let's see them in detail :) 15:56:43 effectively 7 15:56:48 OK, lets go! 15:56:54 https://blueprints.launchpad.net/neutron/+spec/subnet-allocation 15:57:08 That one we all agreed we need and can merge. 15:57:14 So we have two main core reviewers on it, I expect it to land by next week or so. 15:57:42 Lots of work needed still 15:57:50 OK, let's give it another week if it's a top prio 15:57:52 Yup, but I have been informed it's all doable 15:57:54 Cool 15:58:12 #info subnet-allocation -- should land before next 1:1, reconsider if not 15:58:23 https://blueprints.launchpad.net/neutron/+spec/hyper-v-ovs-agent 15:58:40 That one needs to be split into smaller patches, and if that happens we're confident it can merge by later this week. 15:58:43 It's all on the patch author now 15:58:59 It's low risk because it moves some code around and adds new Hyper-V specific code. 15:59:07 How about we drop it if that can't be merged in the coming week ? 15:59:12 WFM 15:59:22 with that many exceptions, I'm more worried with distraction than code impact tbh 15:59:32 Agreed 15:59:45 #info hyper-v-ovs-agent -- needs to fully land by next Tuesday 15:59:54 https://blueprints.launchpad.net/neutron/+spec/restructure-l3-agent 16:00:11 3 patches left, we're confident we can finish this one by Friday as well 16:00:31 Sorry, 4. 16:00:53 #info restructure-l3-agent -- 4 patches left, finalization of a partially merged feature. should land before next 1:1, reconsider if not 16:01:08 https://blueprints.launchpad.net/neutron/+spec/ipv6-router 16:01:29 We're waiting on a tempest functional job for this one, and it depends on a patch from the multiple-prefix one. 16:01:40 So this one is iffy, and again, if it doesn't land by Friday it should be out. 16:02:03 #info ipv6-router -- needs to fully land by next Tuesday 16:02:18 https://blueprints.launchpad.net/neutron/+spec/multiple-ipv6-prefixes 16:02:29 same bag? 16:02:38 Yup 16:02:52 #info multiple-ipv6-prefixes -- related to previous one, needs to fully land by next Tuesday 16:03:04 https://blueprints.launchpad.net/neutron/+spec/netscaler-lbass-v2-driver 16:03:24 That one needs a working CI, which it doesn't have. 16:03:27 how much time did you gave them 16:03:29 ? 16:03:31 We've given it and the radware one until Friday to merge. 16:03:54 #info netscaler-lbass-v2-driver -- needs CI up, must merge before EOW 16:04:03 https://blueprints.launchpad.net/neutron/+spec/radware-lbaas-driver 16:04:05 same I suspect 16:04:17 #info radware-lbaas-driver -- needs CI up, must merge before EOW 16:04:19 Yup 16:04:21 same 16:04:53 OK, if we stick to those deadlines we should be good. My only gripe is that none of them actually looks like it's very close 16:05:17 Means that it will be distracting, and despite the distraction we need to start focusing on bugs 16:05:18 I hear you, but I've been firm on kicking things out that don't make the deadlines. 16:05:28 I moved out pluggable IPAM to a room full of gripes today. 16:05:35 In particular we'll need a list of RC1 blockers for next week 16:05:38 Agreed 16:05:48 We've started moving bugs out of RC which are not blockers. 16:05:50 I have more work to do there. 16:05:54 you can move the wishlist stuff to a kilo-rc-potential tag to keep track of them if you need to 16:06:13 OK 16:06:16 also a bug scrub on the general bug list is helpful to catch previously-overlooked issues 16:06:18 those are plugin decomp tracking items 16:06:26 Good idea 16:06:30 just in case 16:06:53 and then keep an eye on recently-filed bugs, as people start testing the thing we say is mostly there :) 16:07:05 That is all I had 16:07:18 Same for me. 16:07:22 We're close ttx! :) 16:07:29 Just need to get the proverbial ball over the goal line. 16:07:31 ;) 16:07:32 once you refine the bug list, make sure you have assignees for each blocker 16:07:38 Ack 16:07:46 otherwise they tend not to get a lot of attention :) 16:07:54 alright then,n have a great and busy week :) 16:08:04 you can relax when RC1 is done :) 16:08:36 LOL 16:08:36 Yeah, no kidding! 16:08:49 And my son had tonsil surgery and ear tubes put in last week, so it's been nuts between that, the baby, and RC 16:08:54 * mestery needs to take a vacation 16:09:00 mestery: I can only relax once the summit is done, so... 16:09:13 ttx: :) 16:09:16 thanks ttx! 16:09:18 I entered "The Tunnel" 16:09:25 lol 16:09:33 there is light on the other side 16:09:42 I can feel it 16:09:50 Go towards the light! 16:13:58 ttx: around? 16:14:03 SlickNik: yes 16:14:09 we can talk now 16:14:41 Sounds good — forgot I needed to go to a doctor's appointment later, so this would be better. :) 16:14:46 #topic Trove 16:15:01 #link https://launchpad.net/trove/+milestone/kilo-rc1 16:15:15 I see two FFEs left 16:15:18 One of our FFE BPs is done 16:15:34 I sthat the full set you've been asked for ? 16:15:51 Yes, those two are all that's left and are pretty close. 16:15:54 https://blueprints.launchpad.net/trove/+spec/db2-plugin-for-trove 16:16:10 I think we need a deadline for that one, as it's a key feature 16:16:16 I've moved the others to liberty since they will not make it. 16:16:22 what would be reasonable ? Before next Tuesday ? 16:16:36 The deadline I'm telling folks is end of this week. 16:16:42 ok 16:16:56 #info db2-plugin-for-trove -- must land before EOW 16:17:03 https://blueprints.launchpad.net/trove/+spec/implement-vertica-cluster 16:17:22 Same thing with this one. 16:17:24 Looks about as far, same deadline ? 16:17:24 ok 16:17:40 #info implement-vertica-cluster -- must land before EOW 16:17:50 Good progress made — and I think it's got a good shot of landing before the end of the week. 16:18:01 Looking at the bug list now 16:18:18 So ideally that list would be the list of release blockers we need to solve before we can tag a RC1 16:18:31 nice-to-haves should move to using the kilo-rc-potential tag 16:18:37 so that you can find them 16:18:50 That list has some punts from kilo-3 but which are not release blockers 16:18:57 Let me go through them and clean that list up. 16:19:03 right, so you should refine it and make sure the remaining stuff are blockers 16:19:16 not necessarily now, but before next week 16:19:41 #action SlickNik to clean up RC1 bugs to make sure they are true release blockers 16:19:41 Doing a quick pass on Lcunhpad bugs to make sure you didn't overlook a critical issue is generally a good idea too 16:19:46 Sounds good. 16:20:02 that is all I had. Questions ? 16:20:05 Will do that as well. 16:20:30 No more questions from me. Thanks for your help! 16:20:34 np! 16:20:44 devananda: ping me when around 16:51:17 morganfainberg: ohai 16:51:42 \o 16:51:52 #topic Keystone 16:51:59 Lots of FFE requests. 16:52:03 #link https://launchpad.net/keystone/+milestone/kilo-rc1 16:52:12 Sec moving off phone to desktop. 16:52:14 yeah, but only one on the page so far 16:52:16 sure 16:52:30 ok 16:52:33 so let's start with that one 16:52:37 https://blueprints.launchpad.net/keystone/+spec/model-timestamps 16:52:56 * morganfainberg forgot to put the others on the rc-1 as blocked 16:52:56 is it one you support, or just some random person targeting it ? 16:53:10 that one i support, there is no API impact (or shouldn't be) 16:53:11 we'll add them as we go 16:53:32 how close is that ? 16:53:45 we can give it until end of week alright 16:53:46 it should be a minor refactor. needs a rebase and probably 1 patchset 16:54:02 more worried about distraction than impact tbh 16:54:04 i'm planning on handling the minor update [filter extra data before it hits the API] 16:54:15 it's the lowest priority though 16:54:27 lets just punt it till liberty 16:54:32 #info model-timestamps -- to be merged before next Tuesday 16:54:39 it can land right off the bat next cycle. 16:54:44 oh yes 16:54:46 #undo 16:54:47 Removing item from minutes: 16:55:02 leaves room for more interesting ones 16:55:10 yeah and we have a bunch :( 16:55:20 yes, you look like Nova now 16:55:26 so let's see... 16:55:51 I see a thread about domain configuration SQL support, fetching spec 16:56:08 Looks like https://blueprints.launchpad.net/keystone/+spec/domain-config-ext 16:56:10 the Domain SQL is a couple follow up patches that didn't land 16:56:12 yeah 16:56:19 rather than rush them we opted for FFE 16:56:30 it should be ~3 small-ish reviews 16:56:36 sounds good, finishing the work 16:56:36 most are heavily reviewed already 16:56:42 should not take more than a week, right 16:56:55 correct 16:57:04 #info domain-config-ext -- to be fully merged before Tuesday next week 16:57:05 should be merged this week if the exception is granted 16:57:19 * ttx adds 16:57:49 next up is idp-id-registration 16:58:01 https://blueprints.launchpad.net/keystone/+spec/idp-id-registration 16:58:04 this is ready to go. it was blocked by a critical bug 16:58:12 it should easily merge today or tomorrow 16:58:17 so should merge in the coming days ? ok 16:58:33 #info idp-id-registration -- to be completed before EOW 16:58:59 and by my count we have 2 big ones next. 16:59:23 next up is the reseller stuff 16:59:32 is that https://blueprints.launchpad.net/keystone/+spec/reseller ? 16:59:35 yeah 16:59:46 i'd really like to see this land in kilo. i think it's a tall order 17:00:05 For this one it depends more on the disruption it may create to existing code 17:00:20 so, the code in keystone will see a lot of disruption 17:00:23 it feels like it has wrecking potential 17:00:28 the code for anyone else should be zero 17:00:52 it shuffles a lot of things. it was a big priority this cycle to get in, but like everything else got slammed into k3 timeline 17:00:58 which meant things didn't land 17:01:13 how long do you think it can take ? 17:01:23 it could land next week EOW 17:01:28 if everyone core jumped on it 17:01:30 I'm worried we might introduce regressions we don't have time to spot 17:01:40 i think that is a concern 17:01:55 let's table it for the time being and see the other one 17:02:12 wrapped assertions? 17:02:20 hmm? 17:02:31 oh 17:02:32 yeah 17:02:33 is the last one about wrapped assertions? 17:02:35 SAML 17:02:43 was thinking code assertion not SAML assertion 17:02:48 trying to find the blueprint 17:03:15 it's not a BP 17:03:17 it's a bug 17:03:29 it should be converted to a BP: https://bugs.launchpad.net/keystone/+bug/1426128 17:03:30 Launchpad bug 1426128 in Keystone "Add ECP related bits to saml generation code" [Wishlist,In progress] - Assigned to Rodrigo Duarte (rodrigodsousa) 17:03:42 this is small in scope, but impacts API 17:04:03 I guess if it lands in the coming days harm is limited 17:04:07 yeah 17:04:12 is it ready to land ? 17:04:12 and it's totally isolated 17:04:15 very close 17:04:19 i'd say tuesday for sure 17:04:30 could you speed-create the BP for it ? 17:04:34 yeah 17:04:35 sec 17:04:39 so that we end up with the clean list 17:05:20 If you really want it, I'm inclined to give reseller a try, since everything else should be landed by next week 17:05:29 https://blueprints.launchpad.net/keystone/+spec/ecp-wrapped-saml-assertions 17:05:36 it's the only one that has potential to really overflow 17:05:51 ok, targeted to rc1 17:05:55 my biggest concern with reseller is that is it changing how domains are working 17:06:03 they become projects with a flag 17:06:13 the rest of reseller is fairly innocuous/isolated 17:06:15 #info ecp-wrapped-saml-assertions -- need to land before next Tuesday 17:06:40 morganfainberg: would it be a btter idea to land it early in liberty ? So that people can start play out with it if they want to ? 17:07:18 i think it's a wash if it lands now or then. we have a high demand for the features this cycle [lots of people asking for it], but the risk is higher 17:07:36 I think you laredy landed more thanb your share of Kilo features tbh 17:07:44 plenty of edge cases to test already 17:07:49 lets say liberty then. 17:07:51 and the sooner we get to that the better 17:07:56 it'll disappoint some folks. 17:08:07 * morganfainberg knew this was going to be the result tbh. 17:08:40 you can blame me. I'm very willing to cut Horizon some slack due to its position in the stack... Keystone, not so much 17:08:43 we also have a ton of bugs to triage through 17:08:58 uh. no. we share the blame here. i let everything wedge into k3 17:08:59 ;) 17:09:06 If it were a couple days away that would not be the same discussion 17:09:15 but we are talking end of next week here 17:09:19 next cycle i hope we make FF for keystone milestone-2 17:09:36 then we have a whole milestone for things to slip like this if needed 17:09:38 :P 17:09:44 yeah, nova-style 17:09:48 exactly 17:09:53 esp. with where Keystone is in the stack 17:10:26 all of these (i think) are also string-freeze exceptions 17:10:36 do i need to send messages to the i18n list? 17:10:49 or is FFE sufficient for that 17:10:54 at least one thread on the ML so that they are able to know, yes 17:11:01 can be a single post for all 17:11:04 ack 17:11:14 * ttx tries to update BP status 17:11:30 i expect to be bug triaging and punting bugs off RC that aren't important this week as well 17:11:34 I think I can set them all to Needs Review 17:11:41 I'll let you unblock the patches 17:11:55 yes, the next step is to refine the bug list so that it's actually blockers only 17:11:59 sounds good. i will make the ECP ones get commit updates 17:12:06 and keep the nice-to-haves using the kilo-rc-potential tag 17:12:12 yep. 17:12:15 so that we ahve a list to track starting next week 17:12:26 someone went a bit gung-ho and added every open bug to rc 17:12:29 i think. 17:12:30 :P 17:12:36 every recently opened bug that is 17:12:47 let them use the tag instead :) 17:12:56 i will be asking them to do that. 17:13:01 cause *bugs* 17:13:03 ;) 17:13:12 anyway next week should have FFEs done and bug list sane 17:13:17 also get someone assigned to that blueprint you just created 17:13:20 that is all! 17:13:46 done 17:13:51 assigned to stevemar 17:14:13 notmyname: sorry for the lateness 17:14:21 morganfainberg: have a good day, talk to you later! 17:14:29 looks liek you had import stuff to discuss :-) 17:15:00 not every day that keystone has more exception requests than Nova, Cinder and Neutron combined 17:15:08 haha 17:15:13 #topic Swift 17:15:14 wow 17:15:34 so in swift-landia, we're hard at work on our final push to getting an erasure code beta for kilo 17:15:48 how is that going ? Still on track ? 17:15:56 the patch chains being tracked are the starred patches on... 17:15:57 #link http://goo.gl/uRzLBX 17:16:01 our review dashboard 17:16:45 the plan is to finish up work on feature/ec this week and start the merge to master next week 17:17:38 there's a lot do to, so it's hard to say if it's "on track". but we'll definitely have a beta in kilo :-) 17:17:51 some beta at least :) 17:18:06 ok, so I expect we'll have more to discuss starting next week 17:18:17 about the merge process? 17:18:40 yeah, and the RC1 timing 17:18:57 we're still shooting for april 10 as a guideline 17:18:58 you have the merge process pretty much under control right 17:19:21 yes, I think that will be tedious, but not especially hard (the git logistics) 17:19:33 I'll need to work with -infra for the final merge 17:19:38 I don't expect to be useful there, but if you need me for anything, let me know 17:19:43 ok, thanks 17:19:49 anything else ? 17:19:55 during the merge process, we'll freeze master 17:20:03 to avoid conflicts causing delays 17:20:07 #info still shooting for april 10 as a guideline for swift rc1 17:20:28 that's pretty much everything right now: all EC, all the time 17:20:55 alright 17:20:59 I'll let you go back to that 17:21:05 have a good evening 17:21:18 nothing to discuss at cross-project meeting, so we'll skip it 17:21:23 one more hour back 17:21:32 ok 17:21:49 That concludes our syncs for today, thanks everyone 17:21:51 #endmeeting