08:49:03 #startmeeting ptl_sync 08:49:04 Meeting started Tue Dec 9 08:49:03 2014 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:49:05 We can 08:49:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:49:09 The meeting name has been set to 'ptl_sync' 08:49:09 Thanks! 08:49:12 #topic Trove 08:49:28 So.. next week we have kilo-1 08:49:48 So I spent some time getting https://bugs.launchpad.net/trove/+milestone/kilo-1 in shape. 08:49:48 The goal being to tag sometimes between the 16th and the 18th 08:50:11 so on thos days, as soon as you're happy with the sahpe of master we can push the tag 08:50:21 Yes. Working towards getting all the BPs that are on track reviewed and through. 08:50:29 Soundsgood 08:50:39 just send me a SHA and I'll make it happen 08:50:49 https://launchpad.net/trove/+milestone/kilo-1 08:51:10 7 in-progress blueprints to get in 08:51:22 and 12 bugfixes still targeted 08:51:32 next week we'll refine that list to cover true milestone blockers 08:51:43 but the current list sounds reasonable to me 08:52:00 Most of them are pretty close. 08:52:44 Will sync with you on them again next week to check what we need to move out (if any). 08:52:50 agreed 08:52:59 No questions from me, you look in good shape 08:53:25 Sounds good. That's pretty much all I had. 08:53:50 Thanks for being flexible with the timing. 08:54:05 no pb! 08:54:10 talk to you next week 08:54:47 Thank you — see you later at the x-project meeting. 08:55:46 o/ 09:00:17 asalkeld: o/ 09:00:21 hi ttx 09:00:26 #topic Heat 09:00:40 #link https://launchpad.net/heat/+milestone/kilo-1 09:00:53 asalkeld: same comment, kilo-1 is next week, so the idea is to tag sometimes between the 16th and the 18th 09:01:00 ok 09:01:11 i might need to move one or two bp to k2 09:01:13 On those days, as soon as you're happy with the shape of master you send me a SHA and we can push the tag 09:01:26 ok ttx sounds 09:01:29 good 09:01:35 (and defer the missed Bps to k2) 09:01:51 sounds easy ;) 09:01:55 it is easy 09:02:05 especially since the milestone itself is not that important 09:02:20 ok, yeah just intermediate 09:02:51 the goal is just to avoid picking the wrong SHA, like if you wait for the last patch in a series implementing a feature, better wait a few more minutes :) 09:03:07 sure, makes sense 09:03:10 . 09:03:20 https://blueprints.launchpad.net/heat/+spec/cinder-custom-constraints has no priority ? 09:03:31 ttx, checking 09:04:01 (is implemented already) 09:04:31 and yes, depending how complex they are, decouple-nested lazy-load-outputs and multi-region-support might need to get pushed 09:04:32 yeah, it was a very small bp 09:04:51 decouple-nested - is looking big 09:04:59 needs heaps of test code rework 09:04:59 keep them in as long as you sincerely think they are likely to get in 09:05:08 ok 09:05:10 but defer them if you think they won't 09:05:28 sure, makes sense 09:05:43 Next week we'll refine again to only list milestone blockers 09:05:52 so that we know what we are waiting on 09:06:05 ok 09:06:47 Do you need to merge anything more on the topic of env-nested-usability ? 09:07:02 i just marked it done 09:07:21 hah! 09:07:25 alright then 09:07:37 questions on your side ? 09:07:46 no, all good 09:07:48 thanks 09:07:56 alright, have a good week! 09:08:01 you too 09:08:20 mikal: are you standing in for john, or should we just skip this week ? 09:09:02 I am hot spare John 09:09:14 Not that we've managed to overlap beforehand to brief 09:09:21 But I am here for your release questioning needs 09:09:23 let's try :) 09:09:26 Also, I have questions about your bot 09:09:26 #topic Nova 09:09:47 ok let's start with the bot question 09:10:06 Ok, so I approved four BPs Friday last week as part of our meeting 09:10:11 I assigned a milestone etc 09:10:17 did you set a priority ? 09:10:21 And then your bot removed the milestone and slapped my wrist 09:10:27 Obviously I've missed a step 09:10:30 Ahhh, probably not? 09:10:38 https://blueprints.launchpad.net/nova/+spec/hyperv-serial-ports is an example 09:10:39 So the problem is... anybody can set a milestone. 09:10:50 but only drivers can set a priority 09:11:00 so we use the milestone+priority comboi to mean "approve" 09:11:16 Fair enough 09:11:20 and slap the wrists of anyone who dares to set milestone without priority 09:11:22 I will retry with priorities set then 09:11:45 it's an ugly workaround for Launchpad weird permission model around milestone targets 09:12:40 I understand it can be surprising, that's why it's opt in and I explain it to people before they accept or reject it 09:12:41 Ok, all fixed 09:12:43 So all is well 09:12:53 sorry about the "slap" 09:12:53 Yeah, I think its because John has always done this for me 09:13:00 I was just trying to help out while he was distracted 09:13:05 Its all good, fixed now 09:13:12 Next topic! 09:13:18 https://launchpad.net/nova/+milestone/kilo-1 09:13:31 We'll tag kilo-1 between the 16th and 18th next week 09:13:39 Yep 09:13:42 so the list if probably a bit optimistic at this point 09:13:45 A lot of that is going to get bumped I think 09:13:48 Which is pretty normal 09:14:11 it's good to refine it so that it represents your best guess as to what should make it 09:14:18 We've also said that we will impose a spec approval deadline of kilo-1 as well 09:14:21 but I expect John will do it 09:14:22 So I need to remind people of that 09:14:48 There are a few "unknown" status there that are probably not in good shape for next week 09:14:49 I think if its not in "needs code review" or "implemented" its probably safe to bump 09:14:53 But I will leave that to John 09:15:05 yeah, usually at this point, not proposed = not in 09:15:28 so I would remove at least 10 09:15:44 There's only 5 things in k-2 as well 09:15:55 So being a bit more realistic there would be good 09:16:05 and in the unlikely case they make it, we can put them back in k1 09:16:13 So, are things moved manually? 09:16:16 Or is there a script for that? 09:16:24 * mikal wonders if I should do some of it for John 09:16:53 I don't have a script for that. I could make one. But to be fair, only Nova has the volume of specs that makes such a "defer" script needed :) 09:17:07 Heh, fair enough 09:17:19 * mikal will move all the ones in "unknown" or "not started" as a first pass 09:17:27 well, horizon has an habit of targeting hundreds of bugs 09:17:43 I may already have that script somewhere let me check 09:18:22 hmm, no 09:18:24 Its ok, I can just grind through 09:18:26 Its only about ten 09:18:48 last thing is https://bugs.launchpad.net/nova/+bug/1266262 09:18:52 targeted to k1 but no assignee 09:18:58 probably unlikely to make it 09:19:12 * mikal looks 09:19:41 but may be worth finding someone 09:19:53 Sean Dague might have an opinion there 09:19:55 I can ping him 09:19:56 If you plan to try finding someone, you can keep it in 09:20:09 we can clean up next week with "last minute blockers" 09:20:10 Let's keep it for now 09:20:15 Works for me 09:20:43 vmware-vsan-support might be completed with https://review.openstack.org/#/c/74300/ 09:21:08 * mikal looks 09:21:10 quiesced-image-snapshots-with-qemu-guest-agent might have been completed with https://review.openstack.org/#/c/72038/ 09:21:28 How are you deciding which ones to call out like this? 09:21:42 and hyper-v-smbfs-volume-support might have been completed with https://review.openstack.org/#/c/129235/ 09:21:51 http://status.openstack.org/release/ 09:21:57 I'm using this ^ 09:22:06 shows merged reviews attached to blueprints. 09:22:30 When one in-progress BP only shows merged stuff, I check the review to see if it looks like it's multipart of single-review 09:22:41 or* 09:23:02 Ok, well I shall ask people about those as well then 09:23:21 In those cases those are recent merged, so might just be completed 09:24:20 Cool 09:24:26 What else do we need to cover tonight? 09:24:26 Alright, I think we are good..; questions on your side ? 09:24:32 Nup, I think I am good 09:24:38 thx for stepping in! 09:24:43 No problem! 09:24:49 Cool, see you at the TC thing then! 12:56:47 ttx, hello, /me ready when you are 12:57:25 SergeyLukjanov: will do eglynn first 12:57:43 fwiw schedule is now at https://wiki.openstack.org/wiki/Release_Cycle_Management/1:1_Syncs 12:57:46 ttx, yeah, just defining that I'm online :) 12:58:19 eglynn: eady when you are 12:58:21 +r 12:58:24 hey 12:58:30 #topic Ceilometer 12:58:33 #link https://launchpad.net/ceilometer/+milestone/kilo-1 12:59:02 I bumped the instance-restart BP to k2 due to lack of traction on the code reviews 12:59:07 eglynn: we'll tag and publish kilo-1 next week, seomteimes between the 16th and 18th -- just give me a SHA when you're happy with the state of master 12:59:15 cool 12:59:32 eglynn: those last 5 are still on track for k1 ? 12:59:39 only slight concern is declarative-http-tests since we've seen no code yet 12:59:55 ok, defer it early if you learn more 13:00:01 I'll have a 1:1 with cdent later on today and make a call on whether it's still realistic 13:00:12 otherwise the rest are all on target 13:00:14 next week we'll refien the list to only contain milestone blockers 13:00:28 cool 13:00:58 OK, looks all good and reasonable 13:01:12 questions on your side ? 13:01:27 nope all good ... I'll start populating the kilo-2 roster by EoW 13:01:35 ack 13:01:39 have a great day then 13:01:52 SergeyLukjanov: ready? 13:01:54 you too ... thanks for your time! :) 13:02:11 This is becoming too easy 13:11:57 ttx: ready when you are 13:12:21 dhellmann: ok, let's do it now 13:12:26 #topic Oslo 13:12:49 dhellmann: so next week we'll tag the incubator at some point and park kilo-1 over 13:12:55 mark* 13:12:56 k 13:13:18 Just let me know of a time/SHA that seems appropriate, sometimes between the 16th and the 18th 13:13:38 https://launchpad.net/oslo/+milestone/kilo-1 13:13:39 ok 13:14:04 Are those two still in progress ? I think tooz is mostly done now, was renmaed 13:14:17 yeah, we need to update the review team settings in gerrit but that's it 13:14:24 I'll get jd to do that today 13:14:27 ok 13:14:42 oh, and probably the launchpad settings, too 13:14:45 what about the other one, graduate oslo.context ? 13:15:07 dims is making good progress on that 13:15:17 the code is ready, there are just a few release management things to do 13:15:34 I think we can finish both by next week 13:15:38 ack 13:16:02 In other news, I reworked spec2bp to address your remarks, hopefully 13:16:12 it's now oslo-projectgroup-aware 13:16:37 ok, I'll take a look at the latest version 13:16:53 and lets you specify the path to the spec when it's nonstandard and not stored in the UTL bp field 13:16:56 URL* 13:17:35 cool 13:17:36 that's all I had I think -- questions on your side ? 13:18:04 I added some stuff to the oslo-specs repo last week to refuse specs that don't have matching blueprints in launchpad 13:18:20 so those names should always match now :-) 13:18:48 oh, interesting. We could mention it at the specs cross-project meeting today 13:18:53 sure 13:19:02 I could put it in oslosphinx, to make it easier to share 13:19:09 turn it on/off with some options 13:19:30 OK, anything else ? 13:19:38 nothing from me 13:19:53 dhellmann: ok then, talk to you later! 13:19:54 ttx, sorry, internet issue 13:20:00 ttx: thanks! 13:20:05 SergeyLukjanov: is it better now ? 13:20:12 ttx, I hope so 13:20:23 #topic Sahara 13:20:39 SergeyLukjanov: so, same drill, k1 next week, tag between Tue and Thu 13:20:51 ack 13:20:55 #link https://launchpad.net/sahara/+milestone/kilo-1 13:21:20 * SergeyLukjanov going to cleanup plans before the 1-1 meeting next week 13:21:30 indirect-vm-access still likely to make it ? 13:21:34 sounds like we have a few features that should be moved to k2 13:21:47 ttx, I think so, the spec was just approved 13:22:19 ttx, moving to "needs code review" 13:22:25 ok 13:22:46 so we'll revisit the list next week to lmimit to last-minute milestone blockers 13:22:55 ttx, yeah 13:23:00 On the bugs side, would be good to refine the list at this point too 13:23:09 Not enough assignees to make it 13:24:36 ttx, yup, agree, will cleanup the list 13:25:02 any reason why you use publish-to-pypi for sahara proper ? 13:25:24 ttx, hm, I'm looking now 13:25:35 ttx, actually I don't remember any objectives for it 13:25:51 ttx, no py3X support, but it's like in all other projects :) 13:26:16 ok, I'll propose a fix for it 13:26:21 ttx, thanks 13:26:44 hmm, what else... 13:26:56 ttx, oh, one moment 13:27:24 ttx, what's the issue of using publish-to-pypi? 13:27:37 we only publish to pypi the libraries 13:28:01 server code is signed/published to LP and tarballs.o.o 13:28:22 ttx, okay, so, probably we should remove it from pypi 13:28:29 so it's more a consistency thing 13:28:43 thso that people don't start complaining about https://pypi.python.org/pypi/nova being stale 13:28:44 ttx, we've been publishing sahara to pypi starting from the first release 13:28:57 yes, was a convenient way to inherit the tarball jobs :) 13:29:38 SergeyLukjanov: ok, that's all I had -- questions ? 13:29:46 nope, thank you! 13:30:17 cheers 14:14:19 ttx: Just FYI, I'm in Utah this week for Neutron, I am planning to be at our 1:1, but if you're around now, I'm available now as well. 14:14:55 For 10 minutes at least :) 14:15:07 Otherwise, I'll catch you in 50 minutes 14:15:54 mestery: o/ 14:15:57 We can do it now 14:16:01 Perfect! 14:16:03 Thanks! 14:16:07 #topic Neutron 14:16:22 So we'll tag k1 next week, sometimes between the &6th and the 18th 14:16:27 err 16th 14:16:40 :) 14:16:44 Excellent! 14:16:44 just let me know when you're happy with the state of master 14:16:51 YEs, we're at the sprint 14:16:56 breaking services out this week 14:17:03 I assume we'll tag those repositories too? 14:17:08 It will be new for all of us 14:17:13 so that's a good question 14:17:23 Yes 14:17:31 we can tag them alright. The question is more, what release model will apply to them 14:17:44 is it more library like ? 14:17:59 i.e. semver versioning, publish to pypi 14:18:05 Yes, that's about right. They still depend on Neutron itself. 14:18:06 or more companion tarballs 14:18:08 Yes 14:18:16 Let me think about this though 14:18:21 I will figure it out today and let you know 14:18:44 we need to check which jenkins jobs will apply to those, that's part of the split 14:19:03 Yes, it's on our list of things to do today. 14:19:07 And we need the co-gating jobs setup too, which will happen today as well 14:19:22 From my perspective both options are on the table, we can certainly upload multiple tarballs in the "k1" milestone page on LP 14:19:22 We have the new repos up with code, and reviews out to get them passing basic tests 14:19:28 OK, cool 14:19:36 and share versioning 14:19:52 Excellent 14:19:56 I think it boils down to how tightly integrated thsoe will be with neutron 14:20:18 if they need synced releae, let's just share versioning and release all as components 14:20:38 if the link between them is more loose... you could use a semver contract 14:20:41 My gut feeling says lets do it that way for Kilo, post-Kilo we can think about separating them even more 14:20:59 ok 14:21:18 just keep me posted so that I can do a few checks in advance 14:21:37 Ack, will do sir 14:21:48 mestery: from a launchpad perspective, are those all tracked in same project, or different projects ? 14:22:18 Same project, we're sharing both LP and neutron-specs for these 14:22:31 ok, then it makes sense to share release 14:22:34 Cool 14:22:57 it's just a production artifact that they are released in separate tarballs instead of one 14:23:02 at least for kilo. 14:23:21 Yes, makes sense 14:23:45 so yes, we'll tag them all, and should have -tarball jobs lined up to pick them up 14:23:58 I'll check that my release scripts can handle that 14:24:03 thanks! 14:24:12 #action ttx to check that release scripts can handle the multi-tarball neutron split case 14:24:35 https://launchpad.net/neutron/+milestone/kilo-1 14:24:59 4 specs still in progress, all likely to make it by next week ? 14:25:07 My guess is we land 4 of those, maybe 5, but next week. 14:25:12 Sorry 14:25:19 2 of the 4 in progress, maybe 3 14:25:26 Total of 4-5 14:25:33 Also 14:25:37 The split spec will be approved and done in K1 too 14:25:45 OK, we'll refine the list next ween so that only last-minute milestone blockers are left 14:25:47 It's a formality we need to get done today 14:25:50 Cool 14:26:06 ok, maybe add it to k1 as "Blocked" ? 14:26:07 Yes, the sprint has been super useful this week with regards to getting coding done in person, thanks also to infra and QA over IRC! 14:26:11 Will do 14:26:36 OK, that's all the urgent stuff I had. Questions on your side ? 14:27:03 Nothing else, the split was the main thing on my mind now. 14:27:03 Thanks ttx! 14:27:20 alright, have a good sprint! 14:27:33 thanks! 14:45:10 ttx: +1 on the new spec2bp, thanks for making it work with oslo 14:46:15 Cool, will let it bake for others comment for a few daysthen will merge it 15:20:12 nikhil_k: around? 15:20:13 ttx: o/ 15:20:26 #topic Glance 15:20:46 nikhil_k: kilo-1 strikes next week 15:21:06 yeah! 15:21:15 that means we'll push a k1 tag sometimes between the 16th and the 18th, whenevr you're happy enough with the state of master to send me a SHA 15:21:34 https://launchpad.net/glance/+milestone/kilo-1 15:21:38 ok, sounds good 15:21:52 I see two "unknown" statuses there 15:22:01 ttx: they'r yet to be picked up 15:22:26 nikhil_k: still likely to make it before next week ? 15:22:37 ttx: had given them a chance to get in k1. may be we can push them to k2 early next week 15:22:46 it's a small chance 15:22:50 yes, we'll refine the list next week 15:23:03 so that it only includes the last-minute milestone blockers 15:23:56 cool, that works! 15:25:14 ttx: was that all for me? 15:25:40 sorry phone rang 15:25:51 ah k 15:26:00 but sounds all good 15:26:06 questions from you ? 15:26:18 had one smal one 15:26:24 shall take a bit more time next week as we finally cull the list :) 15:26:52 what to do with the stable/icehouse review requests? 15:27:39 nikhil_k: we'll set up the glance-stable-maint group tomorrow 15:27:49 ok nice 15:27:54 so you shall be able to approve those yourself, as long as you follow stable policy 15:28:04 ah cool 15:28:14 I'll keep you posted. We were waiting to get 2014.2.1 out of the way 15:28:25 gotcha 15:28:29 I booked tomorrow afternoon with fungi to set that up 15:28:36 ttx: how is that group getting formed? 15:28:46 starts with stable liaison 15:28:50 gotcha 15:28:54 let me check the proposed group 15:29:30 would be you and Erno 15:29:34 to start 15:29:45 ttx: ok and we've liberty to add people 15:29:55 there are a few who we would like to be in there 15:30:02 yes, the stable-maint-core group just needs to make sure they know stable policy before adding them 15:30:15 so once we lectured them, we can add them 15:30:43 sounds good! 15:31:10 reference: http://lists.openstack.org/pipermail/openstack-dev/2014-November/050390.html 15:31:33 nikhil_k: note that there is a glance-oriented topic at meeting today 15:31:49 osprofiler options naming 15:31:51 ttx: ah yes, I'd recommended that 15:32:00 will be there in the meeting 15:32:06 alright 15:32:10 nikhil_k: thx! 15:32:14 thingee: around? 15:32:15 thanks too! 15:32:16 ttx: o/ 15:32:20 #topic Cinder 15:32:29 So yeah, same warning... 15:32:35 kilo-1 strikes next week 15:32:38 that means we'll push a k1 tag sometimes between the 16th and the 18th, whenevr you're happy enough with the state of master to send me a SHA 15:33:15 questions on that process ? 15:33:15 ttx: a few of these are waiting for one more +2. I wasn't able to approve other merges since they were in bad shape for other reasons. 15:33:20 ttx: nope 15:33:26 https://launchpad.net/cinder/+milestone/kilo-1 15:33:44 cinder-drbd-volume-driver still likely to make it ? 15:33:59 yes, just spoke with the assignee to have code for me today 15:34:07 ok 15:34:40 We'll refine the list next week so that only last-minute milestone tag blockers are left 15:35:10 ttx: sure 15:35:12 on the bugs side, one of them is targeted but not assigned: https://bugs.launchpad.net/cinder/+bug/1383460 15:35:21 Still liekly to make it ? 15:35:38 I guess that's simple enough :) 15:35:47 ttx: That can be closed likely. sample config is gone. 15:35:52 ttx: I check it out 15:35:58 i'll* 15:36:04 ok, mark it invalid if that makes sense 15:36:38