09:22:35 #startmeeting ptl_sync 09:22:36 Meeting started Tue Feb 10 09:22:35 2015 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:22:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:22:38 :) 09:22:40 The meeting name has been set to 'ptl_sync' 09:22:43 #topic Nova 09:22:56 #link https://launchpad.net/nova/+milestone/kilo-3 09:23:17 That list, I assume, represents the "priorities" + the accepted FFEs ? 09:23:36 Yeah, bit messy right now, I should start pinging folks for code 09:23:59 Yeah, that's the plan, no ffe yet though 09:24:29 Looking at deadlines again... for Nova you're in non-priority feature freeze already 09:24:56 And you'll have the general FF at kilo-3 09:25:04 Yes, we set a deadline for ffe requests of Thursday 09:25:05 Feature proposal freeze on March 5 ? 09:25:32 (i.e. code for all those k3 things must be proposed by then) 09:25:32 Yes, I think we should just match the general dates there 09:25:58 OK, how is the FFE process doing ? Lots of them as I expected.. 2 months freeze is just too long for most people 09:26:30 Cells will be close to the wire on that, others should be close, but I should advertise that date more 09:27:06 Ar eth "medium" in the k34 list priority stuff, or FFEd stuff ? 09:27:12 So the plan is we will have a drivers meeting to decide if any should get in, we hope not 09:27:21 err, I mean the "mediums" in the k3 list 09:28:10 Mediums are all priority items, I should check the priorities again 09:28:17 ok 09:28:30 No hurry, just refine the list as you go 09:28:58 I won't get involved in FFEs until we reach the general Feature Freeze and they start affecting the stability of the end release 09:29:10 so I'll let you run through them 09:29:51 That's about all I had. I propose we skip 1:1s next week 09:29:51 OK cool, that sounds the efficient way, we will get you to bless any final ffe this time, sorry about last time! 09:30:02 Makes sense 09:30:14 anything else on your mind? 09:30:26 Thanks for keeping us on track though, it really helps! 09:30:40 Nothing more from me really 09:30:44 Oh, we'll discuss novanet2neutron status at the cross-project meeting today. You might want to ensure some nova people are present 09:31:13 Ah, we have jogo and anyeta that cover that 09:31:23 cool 09:31:30 I will try ping them later 09:31:39 OK, have a good train ride 09:31:46 I pinged anteaya already 09:31:47 Thanks:) 09:31:52 Cool 09:32:05 * ttx grabs coffee 09:32:05 Tunnel soon, so just in time! 09:32:06 * anteaya has been pinged 13:00:12 eglynn: ohai 13:00:19 ttx: hola! 13:00:21 #topic Ceilometer 13:00:37 #link https://launchpad.net/ceilometer/+milestone/kilo-3 13:00:55 That "unknown in the list is actually "not started" I suppose ? 13:01:08 yes, I'll update that 13:01:24 ok, otherwise looks good 13:01:56 As far as deadlines go, I just have Feature Freeze for ceilometer on March 19 like veryone else 13:02:17 Do you plan to enforce FeatureProposalFreeze (feature code must be proposed) on March 5 ? 13:02:27 we spoke about a FPF two week prior to that 13:02:32 yep, exactly 13:02:35 ok, that corresponds 13:03:02 Any other deadlien I missed ? 13:03:09 nope that's it 13:03:24 BTW I put in provisional numbers for summit sessions in https://docs.google.com/spreadsheets/d/14pryalH3rVVQGHdyE3QeeZ3eDrs_1KfqfykxSTvrfyI/edit#gid=610965958 13:03:33 cool thx 13:03:37 I'll discuss at team meeting on Thurs before finalizing 13:03:50 I don't really need a final number 13:04:04 a-ha, k, just a general indication? 13:04:09 it's more to work on the room layout to fuzzy-match the requests 13:04:23 since I have to decide on room layout very soon 13:04:35 k 13:04:45 Final allocations we can't really do until we know which project teams we'll have 13:04:56 I propose we skip 1:1s next week 13:05:05 since this is early in k3 period 13:05:06 cool with me 13:05:19 alright then, that's all I had 13:05:25 one very general question for you ... 13:05:29 more TC-level in fact 13:05:37 sure, ask 13:06:02 when do you expect to start accepting "applications" for stackforge projects to be big-tented? 13:06:16 That's actually something we'll discuss today 13:06:27 The criteria is up so we could accepot them now 13:06:38 a-ha, cool 13:06:41 just want to check if that is ok with other members 13:06:52 The goal being to process them before the L design summit 13:06:58 so that we can give those teams room 13:07:14 (reason I ask is that jd is thinking of taking gnocchi down that route) 13:07:42 I almready have the security group (OSSG) wanting its own offciial team recognized 13:07:49 so they asked too 13:07:56 coolness 13:08:12 alright, have a good week! 13:08:22 you too, thanks for your time! 13:08:25 SergeyLukjanov: ready when you are 13:11:02 ttx: I'm around, if SergeyLukjanov isn't ready 13:11:08 #topic Oslo 13:11:12 dhellmann: ok, let's do that 13:11:16 oops, soory, I'm here 13:11:23 will wait 13:11:29 SergeyLukjanov: too late :) 13:11:35 #link https://launchpad.net/oslo/+milestone/kilo-3 13:11:37 sorry to steal your spot SergeyLukjanov 13:12:23 dhellmann, that's ok :) 13:12:31 So that would be 4 graduations still planned before end of kilo ? 13:12:47 + some extra features in oslo.cache but worked in the incubator 13:12:50 versionedobject and policy are definite 13:13:03 debtcollector, too 13:13:21 I haven't seen any progress at all on the reports one, so I'll have to check with solly about that 13:13:41 #link https://launchpad.net/oslo/+milestone/next-kilo 13:14:06 I don't see major features there, which is probably a good thing 13:14:45 yeah, most of the work in the libs at this point is around bugs 13:14:45 dhellmann: looking at the release schedule, I don't see anything specific for Oslo 13:14:57 do you mean like freeze dates? 13:15:01 that means FF on kilo-3 (March 19) 13:15:03 yes 13:15:21 Do you plan somethign like FeatureProposalFreeze two weeks before ? 13:15:21 ok, I talked to the team about using 12 Mar instead, to give us a week 13:15:27 just 1 week, but yeah 13:15:44 So.... feature freeze on Mar 12 ? 13:15:55 I think it's safe to assume that we'll do that each cycle -- freeze 1 week before everyone else 13:15:56 yes 13:16:03 ok adding 13:16:40 done 13:16:45 #link https://wiki.openstack.org/wiki/Kilo_Release_Schedule 13:17:11 Do you plan to enforce a feature proposal freeze one or two weks before that ? 13:17:40 (deadline for feature code to be proposed for review) 13:17:41 probably, although we didn't discuss that specifically 13:17:52 ok, the general one is on March 5 13:17:55 just so you know 13:18:02 let's keep the same date for now 13:18:26 In other news I propose we skip 1:1s next week 13:18:30 if the feature is small, it might make it, otherwise it wouldn't make it in time anyway so it would freeze naturally 13:18:41 ok 13:18:46 anything on your mind ? 13:19:10 this thing with stable requirements management is pretty far out of hand 13:19:37 dhellmann: yeah, I wanted to circle back with you on that 13:19:48 I think jogo and mtreinish worked out most of what to do, and oslo is no longer running the stable tests so we're not blocked any more, but we need to find an owner for requirements management 13:19:55 all of the people doing it are part time 13:20:16 dhellmann: yeah 13:20:28 and by "not blocked" for Oslo, I mean we can land patches but not release anything -- we had 4+ releases planned for this week 13:20:35 and we do have projects waiting for them 13:20:35 dhellmann: We could also do a virtual sprint to align all the stars 13:20:54 it would be a good idea to at least hold a meeting of some sort 13:21:05 because sometimes it feels like it's just we are not focused on the same plan at the same time 13:21:18 oh, you meant that figuratively, yeah a sprint is a good idea, too 13:21:45 We all seem to have one piece of the puzzle 13:22:32 when you say "an owner for requirements management" what would that person do ? 13:22:41 every time we think we have it figured out, another aspect comes up 13:22:53 maybe I just mean an owner for solving the current problem we have 13:23:21 but I know I've been reluctant to approve new requirements because they are triggering so many issues, so keeping an eye on reviews would be good, too 13:23:46 It feels like we need to solve the issue once and for all, and then we can live happily ever after 13:23:59 I expect stable branch chamions to spend more time on requireemnts and less tiem unwedging the gate 13:24:01 at least until the next big issue :-) 13:24:14 once we cap things 13:24:53 I'm pretty sure they would prefer watching stable requirements caps than working out which event broke the stable gate 13:25:07 yeah, I know one or two have been involved in this, but I'm surprised there hasn't been more of a concerted effort from the primary stable team on this. I'm worried we think we have more support there than we do. 13:25:40 maybe it's a matter of understanding the problem -- I don't have a lot of insight into the stable maint stuff this cycle, aside from these requirements-related issues 13:25:56 A champion is supposed to drum the beat to get more support, rather than do all the work themselves. One issue is that recently they have been stumped in fixing things 13:26:30 So it feels like they thought they would be able to handle it.. but then it broke faster than they could solve it 13:26:45 that sounds about right 13:26:47 especially since those are not experts in QA/gate/tempest 13:27:09 anyway, topic for discussion tonight at the cross-project meeting 13:27:22 ++ 13:28:04 SergeyLukjanov: still around ? 13:28:09 yup 13:28:24 thanks, ttx 13:29:01 #topic Sahara 13:29:02 #topic Sahara 13:29:10 #topic https://launchpad.net/sahara/+milestone/kilo-3 13:29:20 #undo 13:29:21 Removing item from minutes: 13:29:23 #link https://launchpad.net/sahara/+milestone/kilo-3 13:29:30 oops, sorry 13:29:36 it's not a topic, heh 13:29:40 k3 page looks good 13:29:50 add-lib-subset-cm-api locked on spec approval... 13:30:58 Looking at deadlines... any specific thing for you ? 13:31:08 FF on Mar 19, FPF on Mar 5 like everyone else ? 13:31:20 hm 13:31:29 yup, I think it's ok for us too 13:31:45 (was counting number of weeks before it) 13:32:22 alright. All sounds good and aligned. 13:32:24 the deadlines are ok for us 13:32:28 We'll skip 1:&s next week 13:32:32 1:1s 13:32:36 okay, ack 13:32:45 SergeyLukjanov: anything on your mind ? 13:32:54 nope, i'm all set 13:34:28 SergeyLukjanov: alright, have a good day! 13:34:45 ttx, thx, you too 14:39:18 ttx: I'm here early if you've time for sync. Have a quite a few items today 14:44:22 nikhil_k: sure, let me do a biobreak and i'll be there for you in 2min 14:44:31 sure :) 14:44:32 thanks 14:47:00 #topic Glance 14:47:04 nikhil_k: o/ 14:47:08 o/ 14:47:11 #link https://launchpad.net/glance/+milestone/kilo-3 14:47:29 https://blueprints.launchpad.net/glance/+spec/catalog-index-service is unprioritized 14:47:45 Otherwise looks good 14:47:52 done 14:48:16 Taskflow integration landed just after k2 right 14:48:21 yes 14:48:46 Any specific deadline in k3 apart from feature freeze on March 19 ? 14:49:02 Planning to enforce a Feature Proposal Freeze on March 5 as well ? 14:49:28 ttx: not yet, I will have to confirm that to you next week. Sorry 14:49:44 ok 14:50:09 Although next week I planned to skip 1:1s. So just send me an email instead and i'll update https://wiki.openstack.org/wiki/Kilo_Release_Schedule 14:50:25 Thanks, that sounds good 14:50:34 All good to me; anything else you wanted to discuss ? 14:51:04 yes :) 14:51:18 I wanted to propose zhiyan for stable core maint 14:51:52 He has been a long standing consistent reviewer for glance and is interested in becoming the stable-core-maint for the same 14:52:18 ok, could you send an email to list with [stable] prefix suggesting him ? I'll reach out to check that he is aware of policy and then add him 14:52:31 ttx: Thanks, will do. 14:52:39 anything else ? 14:52:59 ttx: What can we do for situations like these https://review.openstack.org/#/c/154229/ ? 14:53:18 We would like to change the API (without bumping up the versions) 14:53:37 And, I _think_ no one is using it and it's fairly recent 14:53:57 If it's not "released" yet I think it's fair game to fix it 14:54:14 (though) It's a blunder really 14:54:22 maybe raise a small thread so that people are aware just in case 14:54:33 ttx: oh, like you mean as in kilo? 14:54:34 how long has this code been around? 14:54:36 ttx: surely 14:54:44 https://review.openstack.org/#/c/133874/ 14:54:47 Dec 18 14:55:03 yes, I thinkn it's fair game 14:55:16 ttx: There is no client support for this and they realized it after trying to add support there 14:56:34 ttx: also, Horizon would be a primary consumer and they are very likely not using it as glanceclient does not support it yet 14:56:53 I will start email thread but just wanted it to be out there 14:57:01 pretty disappointing 14:57:16 well, shit happens 14:57:24 heh 14:57:35 anything else ? 14:58:03 I think we may have a bit heavy handed k3 14:58:19 I've not added a few spec to the list 14:58:40 Generally asking if things can wait until l1 is a good way to push back things preventively 14:58:46 and switch focus to reviews 14:59:07 makes sense 14:59:15 I think people would not want to wait 14:59:30 but, I would like to plan it with you better this time and keep this communicated with community 14:59:41 may be we will need FFE for 2-3 specs 14:59:52 (I mean that's a possibility) 15:00:08 ok 15:00:22 That was it from my end 15:00:37 alright, have a good day! 15:00:47 Have a good one, yourself! 15:00:57 Appreciate the time adjustment :) 15:01:14 np 15:30:25 thingee: o/ 15:30:31 ttx: hey! 15:30:37 #topic Cinder 15:30:52 #link https://launchpad.net/cinder/+milestone/kilo-3 15:30:55 Busy milestone 15:31:05 ttx: ok so I know this looks bad. I got some explaining to do. 15:31:19 The 3 'implemented' ones... were they fixed post-k2 ? 15:31:37 or was one of them actually completed in k2 and we missed it 15:31:39 nope. I checked last minute stuff before you tagged things 15:31:44 ok 15:31:53 that's why it took me a bit of time to give the ok 15:32:28 so I realized a lot of people just put up a patch that do driver updates of some new feature. We never really strictly tracked those before 15:32:44 I really wanted to start tracking those to understand how over subscribed we were. 15:33:03 the way it looks now it's doable if you only do reviews from now to FF :) 15:33:16 luckily I can say three were pretty close in k-2 and are done now. 15:33:26 and there are two more just about done as of last night. 15:33:35 So I like to be optimistic and think 26 here :) 15:33:59 ok 15:34:17 I have a few deadlines for you in k3 15:34:17 left to do anyways. I have removed some I wasn't sure were going to happen because I haven't seen code or contact from the assignee 15:34:19 Cinder spec approval deadline (Feb 15) 15:34:24 Cinder feature freeze (Mar 10) 15:34:36 those are correct 15:34:50 Do you plan any Feature Proposal Freeze ? The general one is March 5 so a bit close to your proposed ff 15:35:01 (FPF = code must be up for review) 15:35:42 Might need a bit more time with the code freeze 15:36:16 well, if you have a date I can add it to the schedule 15:36:19 so just let me know 15:36:28 march 2nd? I'll have to talk to the team 15:36:53 There was also some confusion about whether Cinder was frozen, on one ml thread 15:36:54 I always get the dates in agreement from people in our meeting. 15:37:11 my understading is that it's under non-priority feature freeze 15:37:17 ok, if it was sent yesterday, I was mostly on a plane all day so I'll reply. 15:37:26 thank goodness for gertty 15:37:33 heh 15:37:56 I plan to skip 1:1s next week 15:38:06 ok, I'll update my calendar accordingly 15:38:10 That's all I had -- anything on your side ? 15:38:28 Nope, I'm good! 15:38:55 thingee: cool, have a great day 15:39:02 david-lyle: ready when you are 15:39:04 you too 15:39:11 ttx: ready 15:39:11 even that is 15:39:14 evening* 15:39:16 #topic Horizon 15:39:27 #link https://launchpad.net/horizon/+milestone/kilo-3 15:39:46 A bit of cleanup might be necessary there 15:39:56 ttx: indeed 15:40:08 will start on that 15:40:08 In particular unassigned blueprints, "unknown" delivery and "undefined" priorities 15:40:24 no hurry for today, but would be good to fix it in the next 2 weeks 15:40:36 It also looks a bit long 15:40:40 ttx: it is 15:41:01 I have in mind some that aren't going to make it 15:41:05 will start dropping 15:41:16 as a comparison point, you got 9 implemented in k1 and k2 15:41:29 that was lower than normal 15:41:36 so even taking into account abusier milestone, I don't think you can get above 25 :) 15:41:49 we have some big ticket items have taken longer 15:42:11 really I have 4-5 highs that I want to land, the rest are opportunistic 15:42:33 ok, makes sense 15:42:53 I don't have any specific deadline noted for Horizon in k3 15:42:54 we don't really have a great system for that 15:43:01 so that means aligning with FF on March 19 15:43:13 Do you plan to enforce FPF on March 5 as well ? 15:43:24 yes 15:43:27 FPF = All feature code up for review 15:43:30 alright 15:43:45 I'll start publicizing that in Horizon 15:43:52 Last thing, I propose we skip 1:1s next week, not much to report early in milestones 15:44:01 sure, not a problem 15:44:15 alright, anything on your side ? 15:44:36 for L, horizon would like to formally move to specs, what do I need to do to start that process? 15:44:55 david-lyle: ask infra to create a repo 15:45:09 ok, will do 15:45:10 or propose it yourself, following the infra manual 15:45:22 ok, I can look at that too 15:45:32 then add the repo name to projects.yaml in governance and you shall be set 15:45:54 also I proposed an ATC exception https://review.openstack.org/#/c/154271/ 15:46:10 main UX contributor to Horizon for Kilo 15:46:23 would like to see him acknowledged 15:46:38 hopefully that can make it on the TC agenda 15:46:38 sure, will be on docket for next week meeting 15:46:43 perfect 15:46:44 thanks 15:46:58 neds to be up for a couple days before we can actually vote on it 15:47:02 needs* 15:47:10 no problem 15:47:21 anything else ? 15:47:27 I'm set 15:47:37 alright then. Have a good day ! 15:47:48 you too 15:47:50 thanks 16:43:50 notmyname: I suspect you're knee deep in your hackathon, we can skip this week 1:1s if that's more convenient for you 16:44:06 ttx: I'm here 16:44:09 I've got time 16:44:17 there's one thing to let you know of 16:44:22 ok, want to talk now ? 16:44:25 yup 16:44:26 #topic Swift 16:44:40 #info there is now a feature/crypto branch in Swift 16:44:50 did you see the scrollback from -infra yesterday? 16:45:12 if not I can sumarize 16:45:15 notmyname: hmm, not really, only the review that proposed a clarification in infra manual 16:45:33 right 16:45:41 that's basically it. https://review.openstack.org/#/c/154286/ 16:45:53 to coordinate things through the release manager 16:46:07 right converge names when appropriate 16:46:15 right 16:46:32 sounds good 16:46:36 but yesterday, since we're at the start of our hackathon/midcycle, we got the branch created so it wouldn't be a blocker 16:46:49 what type of work will land on the crypto branch exactly ? 16:46:52 that being said, do you know of exisitng feature/crypto branches in other projects? 16:46:57 no 16:47:12 this is for our on-disk encryption. specifically, http://specs.openstack.org/openstack/swift-specs/specs/in_progress/at_rest_encryption.html 16:47:20 ok, noted 16:47:28 thanks 16:47:39 #info crypto feature branch is to support Swift on-disk encryption 16:47:54 to confirm, I see that we've got about 2 months left until the RC for kilo. right? 16:48:03 early/mid april 16:48:57 yes 16:49:10 ok, thanks 16:49:26 that's all I've got for this week 16:49:30 Ideally you would have the finak Kilo swift RC sometimes between April 5 and April 20 16:49:45 ack 16:50:03 ok, only thing I had was the suggestion to skip 1:1s next week 16:50:16 ok 16:50:48 notmyname: have a good hack day! 16:50:52 thanks! 17:02:14 morganfainberg: around? 17:02:24 o/ 17:02:27 #topic Keystone 17:02:39 #link https://launchpad.net/keystone/+milestone/kilo-3 17:02:57 domain-config-ext is marked unknown, shall I set to "not started" ? 17:03:24 i haven't swept through k3 targets 17:03:28 you can or i can today 17:03:37 done 17:03:54 Looking at k3 deadlines 17:04:03 You're past spec proposal deadline 17:04:16 and you'll have the common FF on March 19 17:04:30 planning to enforce the feature proposal freeze on March 5 as well ? 17:04:56 (i.e. all feature code up for review) 17:05:42 yep. 17:06:03 alright. We'll skip 1:1 next week since that will be the soft belly of the milestone 17:06:14 so i'll need to change this time. 17:06:14 Nothing else from me 17:06:16 with you 17:06:28 i just got hit with a meeting w/ VP @ hp weekly at this time slot 17:06:37 sounds pretty awesome 17:06:46 yeah. my days have become... 17:06:49 meetings 17:06:58 would 10 mins earlier work for you ? 17:07:01 yeah 17:07:07 we could switch with notmyname 17:07:09 maybe 17:07:13 i'll have a hard stop at 9am pacific 17:07:24 i could move as early as 8:30 my time 17:07:29