09:00:56 #startmeeting ptl_sync 09:00:57 Meeting started Tue Nov 25 09:00:56 2014 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:00:58 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:01:00 The meeting name has been set to 'ptl_sync' 09:01:04 #topic Heat 09:01:17 #link https://launchpad.net/heat/+milestone/kilo-1 09:01:44 https://blueprints.launchpad.net/heat/+spec/lazy-load-outputs is marked "unknown" status -- should I consider that not started ? 09:02:07 ttx, i need to check on that one 09:02:21 i just noticed it myself 09:02:27 asalkeld: ok, just set status when you know it -- "Not started" is fine :) 09:02:38 it might be small 09:02:44 Otherwise status looks good in general 09:02:54 yeah, more action in k2 09:03:07 do you expect much more stuff to get done for k1 ? Any work pending a spec approval ? 09:03:27 i have 2 bp's with code ready 09:03:41 but trying to get people happy with it 09:03:52 either in fast or not 09:04:01 asalkeld: would it make sense to track them in the milestone as "Blocked" ? 09:04:21 at least people would know it's potentially coming ? 09:04:25 maybe, I have them as k2 09:04:30 just to be cautious 09:04:35 ah, ok 09:04:45 that's fione, you can move them if they are approved 09:04:51 cool 09:05:21 i would love a tool that would tell me what bp's i need to tweak 09:05:31 So I have spec2bp v2 here: https://review.openstack.org/#/c/108041/ 09:05:32 i might as the nova guys 09:05:58 still need to check with current users (dhellmann) if that's a welcome evolution 09:06:04 but you can keep an eye on it 09:06:10 thx 09:06:30 asalkeld: it doesn't prevent you from having to file the blueprint manually 09:06:37 but after that it aligns fiedl status 09:06:42 field* 09:06:59 that's fine, i wouldn't mind just a tool in our specs repo that i can run 09:07:17 that says x,y and z have just been approved 09:07:26 and need their status tweaking 09:07:32 ok 09:07:44 maybe i can come up with that 09:08:01 i'll dig into your code 09:08:12 did you have any question? 09:08:19 all good 09:08:29 alright then, have a good day! 09:08:32 and 2 mins to go! 09:08:35 you too 09:08:36 woohoo 09:11:05 mikal: shall we wait for John? 09:48:40 johnthetubaguy, mika: around now ? 09:51:41 ttx: I am 09:51:54 alright then, let's do this 09:51:57 #topic Nova 09:52:17 so meeting time, 9am UTC tuesday? 09:52:20 #link https://launchpad.net/nova/+milestone/kilo-1 09:52:29 9:10 UTC actually 09:52:33 yeah, its kicking out time I think 09:52:34 OK, cool 09:52:43 Heat goes at 9 09:52:45 not got that in my calendar yet 09:53:19 Looking at the kilo-1 page, there are a few unknown statuses to clarify, but otherwise looks good 09:53:39 yeah, the unknown usually means not started, but yeah 09:53:57 I am thinking we need to punt some stuff to kilo-2 soon/ 09:54:00 ? 09:54:15 yeah, as usual, the conversion rate is a bit slow 09:54:44 maybe after thanksgiving, you can kick out not started ones to k2 09:54:52 yeah, that seems reasonable 09:55:03 I mean, I am thinking everything that is not fully up for review 09:55:11 so we have a smaller list to concentrate on 09:55:17 it's easy to bring them back from k2 to k1 if a miuracle happens 09:55:25 yeah, very true 09:55:37 after thanksgiving it is 09:55:43 do you expect a lot more stuff to show up on the k1 list ? 09:56:20 well, maybe 09:56:28 there are lots of specs that are close 09:56:37 but I am adding them to k-2 by default at this point 09:56:51 but thats just storing up problems for later in a way 09:57:08 we spoke at the summit about all non-priority stuff needing to be merged by the end of kilo-2 09:57:20 so I need to start making that clear I guess 09:57:29 ok, makes sense 09:57:31 Also note that Nova doesn't have a stable branch liaison yet, so mikal is the liaison by default. Would be great for him to find someone to represent there 09:57:49 especially with a point release coming up soon 09:58:15 johnthetubaguy: maybe mention that at the next Nova meeting? 09:58:48 yeah, I will just keep raising were I can I guess 09:59:08 ah, I will try to remember to ask about the sable branch 09:59:19 not really sure who is active there 09:59:29 johnthetubaguy: let me check 09:59:54 padraig, vish and russell would be the more active stable people 10:00:09 and already part of stable-maint 10:00:16 so..; good candidates 10:00:37 thats a good list to ask, cool 10:00:47 johnthetubaguy: other questions ? topics for the cross-project meeting today? 10:01:03 ttx: I guess specs follow up stuff 10:01:18 specs follow up stuff ? 10:01:22 we have tried to make changes to the template to make it clearer about the specs process 10:01:35 from the cross project summit session, basically 10:01:51 oh, about converging multiple approaches ? 10:01:51 I need to review the wiki page we have, and I just haven't done that yet 10:01:56 yeah 10:02:10 right now we are trying to properly document the nova approach in kilo 10:02:19 is it ready for discussion, or would you rather solidify your approach and present it to the others 10:02:26 its a bit distributed, but we seem to be getting closer 10:02:35 I think we should solidify ideas first 10:02:43 its more that, its not forgotton 10:02:48 ideally you would set your process in stone and then present it for others to adopt and RFC on 10:03:03 OK, maybe a theme for next week meeting 10:03:13 rather than this week's 10:03:23 yeah, thats a good target, while the US folks are eating turkey, I might get time for that 10:03:54 johnthetubaguy: ok then, ttyl! 10:04:07 ttx: thank you, as always! 12:55:19 ttx, /me ready when you're 12:57:10 SergeyLukjanov: your time is 13:10utc so eglynn will go first 12:57:46 eglynn: o/ 12:57:54 ttx: hey, ready when you are 12:57:59 #topic Ceilometer 12:58:02 #link https://launchpad.net/ceilometer/+milestone/kilo-1 12:58:16 I've fleshed out the kilo-1 roster 12:58:26 Looks good. All 4 blocked are pending specs ? 12:58:35 yep, I've include some "blocked" BPs as discussed last week 12:58:50 I have spec2bp v2 here: https://review.openstack.org/#/c/108041/ which you might want to experiment with 12:58:53 only in the cases where I know some implementation work has been done 12:59:13 (e.g. a PoC or a patch already proposed, so likely to be landable for Dec 18th) 12:59:22 cool, I'll have a play with it 13:00:28 progress looks good 13:00:40 yep 13:00:41 you nominated a stable liaison (yourself) 13:00:47 so I have all the bases covered 13:00:55 anything you wanted to discuss ? 13:01:11 yep, I got no volunteer for stable-maint liaison (asked at a couple of meetings) 13:01:22 all other liaison positions covered though 13:01:30 nothing else on my end 13:01:43 alright then, talk to you later! 13:01:52 cool, thanks for your time :) 13:01:57 SergeyLukjanov: you can go now if you want 13:02:04 ttx, /me ready 13:02:07 #topic Sahara 13:02:17 ttx, I forget about +10 mins ;( 13:02:24 #link https://launchpad.net/sahara/+milestone/kilo-1 13:02:36 so, I've cleaned up the milestone page 13:02:44 nice progress. Exepcting a lot more to show up in that milestone before k1? 13:03:37 ttx, yup 13:04:05 ttx, I expect 2-3 more blueprints done in k1 13:04:22 remember you can track blueprints lacking spec approval but likely to make it by k1 with the "Blocked" status 13:04:22 ttx, in addition to the list if specs will be approved this week 13:04:42 ttx, yup, I think I'll add them to k1 to add more info 13:04:53 alright, that looks pretty sane 13:05:07 and... You're the stable branch liaison for sahara 13:05:16 ttx, exactly 13:05:31 so everything looks good. Any question on your side ? 13:06:18 I think nope, everything going very good, we have a lot of new contributors after the first integrated release 13:06:33 nice 13:06:41 ttx, and btw all other liaisons positions are covered now 13:07:00 so, nothing more from my 13:07:02 ttx, thx! 13:07:04 awesome. 13:07:06 SergeyLukjanov: thx! 13:07:23 dhellmann: we can go whenever you're available 13:07:32 ttx: ready 13:07:37 #topic Oslo 13:07:57 #link https://launchpad.net/oslo/+milestone/next-kilo 13:08:26 feels like a lot more is going on than apparent here 13:08:44 we have some specs up for review still where work has started, I think 13:08:56 oh, and see: 13:08:57 #link https://launchpad.net/oslo/+milestone/kilo-1 13:09:12 the stuff in the incubator is still targeted at the regular milestones 13:09:37 ah hm 13:09:59 I guess I can move those things to "next-kilo" as well 13:10:14 checking if we have another view that would work 13:10:45 hmm, no per-projectgroup series view 13:10:49 so probably not 13:10:57 we can still check two places if that makes more sense 13:10:59 I hate to put something like the namespace package change in next-kilo since we expect that to take quite a while. 13:11:22 let's give it a week or two and see how it goes? I'm OK with merging them if we decide we need to do that 13:11:24 I think oslo-incubator should keep kilo-X 13:11:28 ok 13:11:44 makes a lot more sense to be aligned with projects it's copy-pasted from/to 13:11:57 right 13:12:25 ok, you hjave a few "unknown" status that might be turned ito something more explicit, but otherwise looks good 13:12:28 into* 13:12:56 I'll work on updating those. I'm taking a sick day today, so it may be next week 13:13:06 ow 13:13:41 won't hold you away from bed then... just a couple things 13:13:56 https://review.openstack.org/#/c/136820/ -- that's the oslo-enabled autokick.py 13:14:04 nah, this is just an annoying cold, but it gives me an excuse to do some reading :-) 13:14:11 if I ran it on oslo now it would do: 13:14:42 (wait for it) 13:15:06 http://paste.openstack.org/show/138167/ 13:15:22 SETGOAL is just setting the series goal according to target milestone 13:15:37 CLEARGOAL is removing the series goal since there is no target milestone 13:15:50 why are some of them being cleared? do those have kilo set as the series but the spec isn't approved? 13:15:53 heh 13:16:08 ok, I guess that looks right 13:16:11 KICK would mean removing target milestone because no priority set, but you don't have one of those 13:16:36 I sort of like having the option of adding a series goal but we can keep up with those items through the specs I guess 13:16:58 yeah, the trick is, it can get confusing if you don't keep the two aligned 13:17:14 true 13:17:22 you can have blueprints showing up in series view but not in milestone views 13:17:28 (and the other way around, damn LP 13:17:29 ) 13:17:32 I don't think there's anything too destructive going on here, so you can run it on oslo when you're ready 13:17:47 OK, will upgrade the version I use in my cron and run it for oslo 13:17:56 yeah, having them in the series was a way I kept up with what we said we might do before we started using specs 13:17:58 second review is the new spec2bp 13:18:03 but specs give us that now 13:18:18 since you are one of the few to actually use v1, I'd like to have an opinion if it's better/worse 13:18:27 https://review.openstack.org/#/c/108041/ 13:18:39 the goal is to support blueprints for not-yet-approved specs 13:18:58 so most of the logic around starting from the approved spec falls down 13:19:06 and I rewrote it to take a blueprint as input 13:19:15 (since those need to be craeted separately anyway) 13:19:16 I was looking over that. I think in general it's good, but I'm worried about the specs repository name handling change. 13:19:35 I was adding review comments when you pinged me 13:19:41 I'll submit them.... 13:19:44 ok, just take your time 13:19:48 just a heads-up 13:19:53 ok 13:20:07 questions ? 13:20:52 no, I'll leave a couple of comments on that review but that's all I had today 13:21:04 alright then, get well soon 13:21:17 oh, sdague talked to you about the stable branch version caps, right? that's a topic for this afternoon? 13:21:22 yes 13:21:23 thanks 13:21:35 it's on the agenda for the meeting today 13:21:57 ok, good, he and I spoke yesterday and agree on what we need so if I can't make it this afternoon he will be representing both of us 13:22:13 ok 15:05:26 mestery: around? 15:05:34 ttx: o/. 15:05:37 #topic Neutron 15:05:50 #link https://launchpad.net/neutron/+milestone/kilo-1 15:06:07 Still feels very much partial to me 15:06:21 Yes, I agree, we're reviewing specs but it's still very thin 15:06:46 Also, did you see this: https://review.openstack.org/#/c/136514/ 15:06:59 Similar to Nova, I created a priorities spec for Neutron. Most of the things on that list are in review in neutron-specs 15:07:05 feel free to add "blocked" specs if you expect stuff to be approved and implemented in time for k1 15:07:25 Got it 15:07:35 like one of those priorities 15:07:55 Will do 15:07:59 * mestery makes a note to do that post-meeting with ttx 15:08:40 also if you know what's going on there you can update the "unknown" statuses 15:09:00 Yes, agreed. Are we also running your automatic pruning script now for neutron? I believe we are, just wanted to confirm. 15:09:07 yes 15:09:17 cool 15:09:35 Looks like Ihar voluntered to do stable branch liaison for neutron too 15:09:56 Yes, he's been doing a really good job there in fact! 15:10:04 I am very thankful for that. :) 15:10:19 we have arosen, markmcclain and garyk on the neutron-stable-maint future team at this point 15:10:37 I think all three of those folks are good to have there. 15:10:50 I may see if amotoki wants to join as well, he would be a good candidate there in addition. 15:10:55 I'll ask him. 15:11:24 ok, so for next week it would be good to beef up that k1 milestone if you expect other stuff to make it by Dec 18 15:11:31 I guess that's all I had 15:11:34 questions? 15:11:43 Same for me, I just wanted to highlight the priorities BP and that's it. 15:11:48 Nothing yet. 15:11:55 Thanks ttx! 15:12:00 no pb 15:12:15 * mestery is slowly ramping up more post fourth child birth. 15:12:16 #info priorities for kilo at: https://review.openstack.org/#/c/136514/ 15:12:21 It's taking longer than I thought :) 15:12:54 nikhil_k: ready when you are (if you are around) 15:15:26 ttx: o/ 15:16:31 #topic Glance 15:16:44 #link https://launchpad.net/glance/+milestone/kilo-1 15:17:55 * ttx checks why that undefined spec was not autokicked out of milestone 15:18:24 oh, the script is not really enabled for Glance yet 15:18:30 ttx: we want it in k1 though 15:18:35 ah ok 15:18:39 ok, then that's fine. 15:18:55 nikhil_k: just let me know if you want to switch to using that in the future 15:19:07 you should still probably set a priority for that undefined spec 15:19:20 sounds good 15:19:31 Are those the two things you expect to land before the k1 date ? 15:19:38 done 15:19:48 ttx: there are a couple more 15:19:50 https://review.openstack.org/#/c/124522/ 15:20:01 * nikhil_k will ask for a bp to be created 15:20:20 there was a mis-communication that spec auto creates bp post approval 15:20:23 yes, you can add a blueprint and set it to "Blocked" until the spec is approved 15:20:31 sure 15:20:42 there was one more communicated by another dev 15:20:42 no, BP needs to be manually created (LP has no API for creatign blueprints) 15:20:47 he's still working on details 15:20:55 then you can use a script of mine to update it if you want 15:21:06 noted 15:21:14 in progress at https://review.openstack.org/#/c/108041/ 15:21:31 but in all cases you need a blueprint up and manually created 15:21:58 ah cool 15:22:00 so for next week it would be great to see those blocked blueprints on the milestone map 15:22:15 ping me if you have any question on how to achieve that 15:22:39 Erno Kuvaja volunteered to be stable liaison for Glance, does that sound good to you ? 15:23:03 yeah, it was post communication from me 15:23:15 so you need me to send email or something to confirm that? 15:23:23 no no, it's fine 15:23:26 s/so/do/ 15:23:43 ok, I think that's all I had, status looks generally good. 15:23:49 Questions on your side ? 15:24:45 ttx: nothing this week :) 15:24:53 ok then, talk to you later! 15:24:54 holiday week :)) 15:25:00 yep 15:25:02 sounds good 15:25:07 thingee: ready when you are 15:25:43 ttx: o/ 15:25:54 #topic Cinder 15:26:05 #link https://launchpad.net/cinder/+milestone/kilo-1 15:26:15 got our first blueprint done! 15:26:19 yay 15:26:40 started doing specs for k-2 15:26:50 there are two specs without an assignee on that list... any chance some person (or group) actually signed up to do that one ? 15:27:02 we have about four drivers that are just about ready to be approved. We'll see if that'll be possible this week. 15:27:44 ah good catch. There are people for those already working on them 15:27:46 I'll fix that 15:28:18 cool, looks good (and ambitious) otherwise 15:28:49 Cinder did not formally designate a stable branch liaison yet, which means it falls back on you 15:28:50 I agree. For those drivers on the list that still have a 'not started' status right now, I'm a bit worried 15:29:06 yes, starting next week you could defer not started stuff to k2 15:29:27 Jay Bryant is on the stable-maint group, could be a good candidate 15:29:31 that would be jay bryant. What should I update to make that so? 15:29:38 oh heh 15:29:52 thingee: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Stable_Branch 15:30:15 I'll verify with him and update it 15:31:10 ok, that's all I had I think 15:31:21 questions at this point ? 15:31:25 the problem is we can't defer drivers to k-2. The group has already agreed to leave k-2 and k-3 for other things than new drivers :( 15:31:44 well, they should better get started then :) 15:31:53 otherwise you'll be 15:31:57 I'll reach out to them for good measure 15:32:01 ...soon in exception hell 15:32:13 :) 15:32:17 thanks ttx! 15:32:23 thingee: thx! 15:32:28 david-lyle: ready when you are 15:32:41 ttx: ready 15:32:44 #topic Horizon 15:32:50 #link https://launchpad.net/horizon/+milestone/kilo-1 15:33:14 So... a few undefined priorities, a few unassigned blueprints, and a few unknown statuses 15:33:32 Otherwise progress looks good 15:33:47 I need to filter the new arrivals 15:33:53 will work on that later today 15:34:03 ack 15:34:09 Horizon did not formally designate a stable branch liaison yet, which means it falls back on you 15:34:18 anyone that would make a great choice ? 15:34:32 We have Mathias Runge on the stable-maint list 15:34:39 mrunge is the first that comes to mind 15:34:50 yeah, same idea 15:34:52 you may want to handle it too :) 15:34:59 or not. 15:35:14 I'll see if he's interested 15:35:26 would be good to reach out to him. We plan to switch to new model in 10 days when 2014.2.1 is out 15:35:35 ack 15:36:04 ok, that's all I had at this early stage of the game. Questions on your side ? 15:36:33 no, I'm set 15:36:45 david-lyle: alright then. have a good day! 15:37:01 ttx: you too 16:46:53 ttx: good morning 16:47:28 #topic Swift 16:47:34 notmyname: hi! 16:48:16 what does the future hold for swift ? 16:48:43 hello 16:48:49 I have one big thing to chat with you about as an FYI 16:48:50 python-swiftclient 16:48:51 at the summit we talked about what's going on with swiftclient (we'd like to make big changes, but that's hard for compat reasons) 16:49:04 so what we agreed to at the summit was to focus new cSDK dev effort into openstack-sdk 16:49:09 https://etherpad.openstack.org/p/kilo-swift-swiftclient 16:49:16 see the bottom of that link 16:49:27 we'll keep developing CLI functionality in python-swiftclient 16:49:41 and of course we arent' throwing anything away or breaking anything for existing users 16:49:58 but we, as a dev group, want to focus new SDK feature dev work in openstack-sdk 16:50:27 ttx: what questions do you have? 16:50:36 so the big changes you want to make are more client library than CLI ? 16:50:57 the big change is where dev effort for new stuff is focused 16:51:00 and you'll use the existign python-swiftclient to handle compat ? 16:51:27 that's one possibility. I don't know the answer to that fully yet, since it's really early 16:51:40 ok 16:51:48 ie there's a lot of work that has to be done in openstack-sdk before that even becomes realistic 16:52:23 the "Matt's plan" and my notes at the bottom of the etherpad are pretty much where we're at right now 16:52:50 and so I wanted to make sure you know early what we're talking about and panning 16:53:02 so realize this isn't anything that is close to done yet ;-) 16:53:20 ok, all good 16:54:08 do you plan a new version before end of year ? Or more next year at this point ? 16:54:09 please let me know what questions or advice you have :-) 16:54:18 (on swift proper) 16:54:20 new version of swift? or SDK/CLI? 16:54:42 SDK/CLI is obviously a bit further away :) 16:54:45 right 16:55:17 not sure about swift release yet. probably, but honestly I haven't looked at that yet 16:55:25 most swift effort is focused around EC right now 16:55:58 notmyname: given that the end of year is really close now (if you count thanksgiving and the endof year holidays...) would be good to have a rough idea by next week ? 16:56:04 ya 16:56:13 like "definitely not in December", or "maybe in December" 16:56:18 unfortunately I've got to run now. I have an online meetup starting in 4 minutes 16:56:22 sure, no pb 16:56:24 all I had anyway 16:56:29 ya, I'll have a better answer net week :-) 16:56:33 thanks 16:56:44 morganfainberg: ready when you are 16:56:50 ttx o/ 16:56:56 #topic Keystone 16:57:24 #link https://launchpad.net/keystone/+milestone/kilo-1 16:57:39 Looks good to me. Expecting more to show up before k1 ? 16:57:54 i hope (if anything) just minor bugs that will get fixed along the way 16:58:00 but nothing major 16:58:18 I see Dolph volunteered to handle stable branch liaison stuff 16:58:21 yeah. 16:58:29 sounds good 16:58:37 makes my life easier :) 16:58:55 we'll keep you in the future keystone-stable-maint team though :P 16:59:00