09:02:56 <ttx> #startmeeting ptl_sync
09:02:57 <openstack> Meeting started Tue Jan  6 09:02:56 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:58 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:03:00 <ttx> #topic Heat
09:03:00 <openstack> The meeting name has been set to 'ptl_sync'
09:03:03 <asalkeld> happy holidays
09:03:20 <ttx> and happy new year!
09:03:31 <ttx> #link https://launchpad.net/heat/+milestone/kilo-2
09:03:54 <asalkeld> https://bugs.launchpad.net/bugs/1401317 - is a dup
09:04:04 <asalkeld> we just found that out
09:04:18 <ttx> I see only 4 blueprints there -- expecting more specs to be approved ?
09:04:38 <asalkeld> ttx: i well expect
09:04:51 <asalkeld> i think i need to do some admin
09:05:11 <asalkeld> make sure approved ones have the right settings
09:05:35 <asalkeld> been caught out by ttx's sharp eye
09:05:43 <ttx> yes, just add more BPs to match the work being done
09:06:01 <asalkeld> ok, will do
09:06:06 <ttx> less than one month to k2 :)
09:06:20 <asalkeld> yikes already
09:06:27 <asalkeld> pesky holidays
09:06:41 <ttx> so ideally the spec view for k2 should be nearly complete by next week
09:07:07 <asalkeld> ok, I'll sort that out
09:08:01 <ttx> We'll discuss log guidelines at the cross-project meeting tomorrow
09:08:08 <ttx> did you have questions ?
09:08:16 <asalkeld> all good from my side
09:08:58 <ttx> alright then, have a good catch-up week
09:09:12 <asalkeld> thx
09:19:06 <ttx> johnthetubaguy: o/
09:19:14 <johnthetubaguy> ttx: hi
09:19:17 <ttx> #topic Nova
09:19:30 <ttx> johnthetubaguy: did you enjoy the holiday season ?
09:19:54 <johnthetubaguy> ttx: I had a good break, hope you had a good one too?
09:20:30 <ttx> I did! Managed to stay mostly off for 12 days, which is my personal best
09:20:49 <ttx> #link https://launchpad.net/nova/+milestone/kilo-2
09:20:56 <johnthetubaguy> :)
09:20:58 <ttx> That *is* a busy list
09:21:06 <johnthetubaguy> yeah, its pure madness
09:21:25 <johnthetubaguy> slightly self inflicted, as we said juno-3 is for priority things only
09:21:36 <johnthetubaguy> (plus usual exception process)
09:21:40 <ttx> would it make more sense to start asking assignees if they expect their stuff to land in k2 or k3  ?
09:21:49 <ttx> oh, I se
09:21:49 <ttx> e
09:22:36 <johnthetubaguy> yeah, its an experiment, to have a six week Feature Freeze, as we got good at merging things last time
09:22:41 <ttx> I'll do a quick tour of the "unknown" status ones to turn them into STarted/Notstarted based on references posted
09:22:55 <johnthetubaguy> ttx: ah, superstar, that would be good
09:23:04 <ttx> If you could tour the unassigned ones and set a reasonable assignee for them?
09:23:14 <johnthetubaguy> ttx: sure
09:23:44 <johnthetubaguy> the needs code review stuff is the stuff I think has the most promise, its a shame its all low priority, well, almost
09:25:05 <ttx> hmm, actually I need to check if the linked stuff is not just the spec
09:25:10 * ttx redoes
09:27:54 <johnthetubaguy> oh, doh, good point
09:29:30 <ttx> ok done
09:29:57 * ttx crosschecks with http://status.openstack.org/release/
09:31:30 <johnthetubaguy> assignees should be sorted now too
09:31:47 <ttx> OK looks good
09:32:08 <johnthetubaguy> yeah, I need to send out an email about the dates and the current juno-3 plan
09:32:12 <ttx> Would be good to beat the drum to get the priority items started
09:32:16 <johnthetubaguy> but we were hoping to have a drivers or nova-meeting first
09:32:21 <johnthetubaguy> yes, very true
09:32:31 <ttx> otherwise looks good
09:33:01 <johnthetubaguy> the cells stuff is queued behind the testing working they are doing, its not forgotten, but yeah, there is stuff to do
09:33:02 <ttx> on a more personal note, I pushed the discussion on normalization of specs process at a recent cross-project meeting
09:33:22 <ttx> You can read the logs, but the overall feedback was that there wasn't much to standardize
09:33:27 * ttx fetches logs
09:33:32 <johnthetubaguy> yes, apologies I can't make those, it just doesn't work with stuff at home
09:33:50 <johnthetubaguy> OK, thats a perfectly fine outcome
09:33:56 <ttx> http://eavesdrop.openstack.org/meetings/crossproject/2014/crossproject.2014-12-09-21.03.log.html#l-12
09:34:10 <johnthetubaguy> The biggest changes were probably for us in Nova stopping forcing people to write docs up front
09:34:18 <ttx> since that was an action item from the "specs" cross-project session, let me know if you think there is more to do at this point
09:34:20 <johnthetubaguy> I was glad for that change to be made
09:35:21 <ttx> questions on your side ?
09:35:37 <johnthetubaguy> ttx: I still need to update the wiki page to include nova stuff, sorry, but that looks good I think
09:35:56 <ttx> ok then
09:36:03 <ttx> have a good day and a good week!
09:36:09 <johnthetubaguy> my aim was to make sure we didn't all go crazy, and it seems like we are mostly simlar, so thats cool
09:36:14 <johnthetubaguy> ttx: thanks, and you!
13:00:01 <eglynn-office> ttx: knock, knock, ready when you are ...
13:00:06 <ttx> eglynn: o/
13:00:10 <ttx> #topic Ceilometer
13:00:16 <eglynn-office> #link https://launchpad.net/ceilometer/+milestone/kilo-2
13:00:29 <ttx> eglynn: how was your holiday break?
13:00:51 <eglynn-office> good, good, and your's?
13:01:13 <ttx> was nice, managed to disconnect completely for 10+ days, which was pretty nice
13:01:21 <eglynn-office> coolness :)
13:01:29 <ttx> Those 5 "blocked" are pending spec approval, I gather ?
13:01:31 <eglynn-office> but, back to reality this week ...
13:01:44 <eglynn-office> yeah I've been populating the k2 roster with BPs blocked on specs reviews
13:01:54 <ttx> ++
13:01:56 <eglynn-office> we need to restart some conversations to get those over the line
13:02:09 <ttx> indeed, fels like restarting a cold engine
13:02:21 <eglynn-office> yeap, somewhat of a hiatus around the holidays, loses the momentum
13:02:54 <ttx> woul dbe good to unblock those asap as k2 hits in less than a month now :)
13:03:16 <eglynn-office> yeap, k2 first week in Feb
13:03:17 <ttx> No question on my side
13:03:33 <eglynn-office> so I'll push to get all those specs reviewslanded this week
13:03:39 <ttx> we'll discuss currently proposed openstack-specs at the cross-project meeting today
13:03:40 <eglynn-office> cool
13:03:58 <eglynn-office> nice
13:04:02 <ttx> eglynn: have a good restart week
13:04:13 <eglynn-office> you too, thanks for your time!
13:04:28 <ttx> dhellmann: we skip sergey today, so ping me when you're ready to go
13:07:35 <dhellmann> ttx: here
13:09:17 <ttx> dhellmann: o/
13:09:20 <ttx> #topic Oslo
13:09:36 <ttx> https://launchpad.net/oslo/+milestone/kilo-2
13:09:46 <ttx> and https://launchpad.net/oslo/+milestone/next-kilo
13:11:27 <dhellmann> we have several to retarget
13:11:49 <dhellmann> I'll do that for the ones I know about today, and I've asked for updates from everyone by our meeting monday
13:11:50 <ttx> yeah, probably a good idea to defer early those who won't be done by end of month anyway
13:12:29 <ttx> are all the unknowns in kilo-2 actually not started ? If yes I can update that for you
13:13:09 <dhellmann> yes, I think "not started" is more accurate for those
13:13:15 <ttx> ok, processing
13:14:26 <ttx> ok, no real question at this point, expecting we'll have a little bit more accurate picture by next week
13:15:26 <dhellmann> yeah, I'll get this cleaned up by then. I didn't want to push for answers over the holiday
13:15:54 <ttx> dhellmann: we'll be discussing log guidelines at the cross-project meeting today, to trigger reviews there
13:16:21 <ttx> because otherwise it won't ever reach critical mass
13:16:21 <dhellmann> ok, good -- that one has lingered too long
13:16:44 <ttx> we just need to give a "comment now or forever hold your peace" warning
13:17:15 * dhellmann nods
13:17:18 <ttx> I don't expect *every* PTL to vote on it anyway, they just need a fair warning
13:17:38 <ttx> so hopefully that should unclog the pipe there
13:17:44 <ttx> dhellmann: have a great week!
13:17:48 <ttx> talk to you later
13:17:55 <dhellmann> thanks, you too!
15:07:10 <ttx> mestery: ready when you are
15:07:13 <mestery> ttx: o/
15:07:28 <ttx> #topic Neutron
15:07:34 <ttx> #link https://launchpad.net/neutron/+milestone/kilo-2
15:07:59 <ttx> Those "blocked" are, I assume, waiting on spec approval
15:08:14 <mestery> No, they are approved, but have no code submitted yet. Should I use a different state there?
15:08:16 <ttx> Otherwise it's neat progress overall
15:08:25 <ttx> You should use Not started
15:08:31 <mestery> Ah, right, I'll correct that
15:08:37 <ttx> or if work started but no code submitted for review yet, you can use started
15:08:55 <mestery> ack
15:09:25 * mestery fixes those up quickly
15:10:52 <mestery> Done
15:11:11 <ttx> even better
15:11:16 <mestery> Heh
15:11:20 <ttx> that answers all questions I had
15:11:40 <mestery> Cool, I've been keeping everyone aware of the deadline for Kilo-2, and how quickly it's coming now that the holidays are done.
15:11:49 <ttx> We'll mention nova-net to neutron migration in the cross-project meeting today
15:11:58 <ttx> you might want to be around
15:12:13 <mestery> I'll be there, but there won't be much to report yet, Oleg is still on holiday in Russia I believe.
15:12:17 <mestery> May make sense to move that to next week when we'll have more to say there.
15:12:22 <mestery> But either way, an update is fine
15:12:32 <ttx> sure, update can be -- waiting on Oleg
15:12:42 <ttx> just wantr to make sure we don't wait on other resources
15:12:43 <mestery> lol
15:12:50 <ttx> like a nova liaison
15:12:59 <ttx> or support from ops
15:13:04 <mestery> Good idea
15:13:13 <mestery> And thanks for helping to get this more visilbility!
15:13:33 <ttx> questions on your side ?
15:14:01 <mestery> Nothing at this time, we're just plowing ahead in Kilo-2 now.
15:14:02 <mestery> Thanks ttx!
15:14:08 <ttx> alright, talk to you later
15:14:13 <mestery> have a great week!
15:14:19 <ttx> nikhil_k: ready when you are
15:14:25 <nikhil_k> ready
15:14:30 <ttx> #topic Glance
15:14:42 <ttx> #link https://launchpad.net/glance/+milestone/kilo-2
15:15:05 <ttx> about smooth-deletes-over-time: can I switch it to "not started" ?
15:15:15 <ttx> or is it started
15:15:49 <nikhil_k> it's in discussion
15:16:03 <nikhil_k> the guy has been active and discussing design with us
15:16:09 <ttx> ok, implementation:not started is probably more accurate then
15:16:12 <nikhil_k> sure
15:16:27 <ttx> I like to keep "unknown" for when we have no idea
15:16:52 <ttx> Do you expect a lot more blueprints to show up in that k2 landscape ?
15:16:59 <nikhil_k> yes ttx
15:17:04 <nikhil_k> around 10 or so
15:17:20 <ttx> What's their current status ? Waiting on spec approval ?
15:17:33 <nikhil_k> we are keeping a informal freeze 2 weeks after k2
15:17:50 <nikhil_k> so, based on who has started working on the the implementation the specs are getting processed
15:18:14 <nikhil_k> otherwise we have a review queue build up near the close of k2
15:18:19 <ttx> hmm, ok... so we should expect more stuff to appear in the coming weeks
15:18:44 <nikhil_k> right, hope to see at least 4 specs in the next week and half
15:18:49 <ttx> whenever you're pretty sure something is coming, just add it to the mix. If the spec is not approved yet (but will most likely be) you can add the blueprint with status: Blocked
15:19:00 <nikhil_k> that sounds good
15:19:47 <ttx> alright, that's all I had.. questions on your side ?
15:20:03 <nikhil_k> nothing this week :)
15:20:12 <ttx> cool then talk to you later
15:20:17 <nikhil_k> cya
15:20:27 <nikhil_k> Thanks, bye.
15:30:10 <ttx> thingee: o/
15:30:20 <thingee> ttx: hi!
15:30:23 <ttx> #topic Cinder
15:30:32 <ttx> #link https://launchpad.net/cinder/+milestone/kilo-2
15:31:05 <ttx> Lots of "unknown" in there, let me see if I can clarify them
15:31:20 <ttx> chiscsi-iscsi-helper looks Not started
15:31:37 <ttx> same for assisted-snapshot-improvements
15:31:50 <thingee> yeah the assignee has been reached out to for an update. I will be removing it this week otherwise
15:32:01 <ttx> same for all actually
15:32:09 <ttx> will move them to "Not started" now
15:32:19 <thingee> eric is part of core. forgot to reach out to him yesterday in irc to update those or a plan to divide up his work to k-3 as well
15:33:21 <ttx> ok done
15:33:38 <ttx> Apart from those Not started, the rest looks good
15:33:39 <thingee> thank you. I'll make sure to do that for future targeted items
15:33:53 <thingee> ttx: need to verify that incomplete in target bugs too
15:33:53 <ttx> "unknown" should just mean "I have no idea"
15:34:07 <ttx> while most of the time you have an idea and it's just the default status that stuck
15:34:33 <ttx> Do you expect a lot more to be added to the k2 target, or is it mostly complete ?
15:35:05 <thingee> Yeah I have one more.
15:35:08 <thingee> but that should be it
15:35:35 <ttx> ok good
15:35:57 <ttx> I don't think I have any more questions
15:36:35 <thingee> I have now targeted the other bp
15:36:35 <ttx> cross-project meeting today discussing two cross-project specs
15:36:46 <thingee> yes log standards will be great
15:37:00 <ttx> have a great week back!
15:37:09 <thingee> thank you, you too
15:37:32 * ttx starts to wonder if we could not replace 1:1 syncs with more asynchronous pings on this channel
15:38:12 <ttx> david-lyle: ready when you are
15:38:54 <ttx> david-lyle: ready when you are
15:39:00 <david-lyle> ttx: ready
15:39:43 <ttx> #topic Horizon
15:40:27 <ttx> #link https://launchpad.net/horizon/+milestone/kilo-2
15:40:41 <ttx> https://blueprints.launchpad.net/horizon/+spec/launch-instance-redesign appears to be unassigned
15:41:10 <ttx> There are 5 blueprints with undefined priority to process, too
15:41:38 <ttx> david-lyle: Should I just turn all "unknwon" to "not started" ?
15:41:45 <ttx> unknown*
15:41:51 <david-lyle> ttx: was walking through them now
15:42:04 <david-lyle> some already are up for review
15:42:18 <david-lyle> I'll finish walking through them after this
15:42:55 <david-lyle> I'll add an owner for the redesign. It's being actively worked by several people
15:43:29 <ttx> ok, I'll let you clear that all up
15:44:11 <ttx> that's a lot of blueprints compared to the 9 you got in in k1
15:44:26 <ttx> but I guess a lot of those are postponed items
15:44:43 <david-lyle> yeah, a lot that just missed k-1
15:44:54 <ttx> so would be great to get those in early
15:45:00 <david-lyle> now that people are back from holiday, I expect several to land shortly
15:45:09 <ttx> That's about all I had -- questions on your side ?
15:45:23 <david-lyle> no, I'm set
15:45:32 <ttx> alright then. Talk to you later!
15:45:39 <david-lyle> see you later
16:58:00 <ttx> notmyname: around?
17:01:19 <ttx> morganfainberg: around?
17:01:25 <morganfainberg> ttx, o.
17:01:29 <morganfainberg> erm o/
17:01:34 <ttx> #topic Keystone
17:01:46 <ttx> #link https://launchpad.net/keystone/+milestone/kilo-2
17:01:58 <morganfainberg> happy new year
17:01:58 <ttx> 2 unassigned blueprints in there
17:02:14 <ttx> hope you had a good break
17:02:15 <morganfainberg> cadf should be assigned, that'll be taken care of today
17:02:23 <morganfainberg> as will the other one
17:02:32 <morganfainberg> those need house keeping, but people are working on them.
17:02:46 <ttx> should I set all 3 "unknown" to "not started", or will you clarify ?
17:02:52 <morganfainberg> i'll clarify
17:03:13 <ttx> OK... are you expecting a lot more BPs to show up in the next week(s) ?
17:03:23 <morganfainberg> yes, i expect more to show up this week
17:03:35 <morganfainberg> much beyond that i expect k3 to see the last of them appear
17:03:43 <ttx> ok. Don't hesitate to list the ones you're waiting for spec approval on as "Blocked"
17:03:48 <morganfainberg> will do.
17:04:04 <ttx> alright then, no more questions -- did you have any ?
17:04:32 <morganfainberg> nothing at this time, still getting back into the swing of things post holidays
17:04:42 <ttx> indeed
17:04:54 <ttx> ok then, have a good week!
17:05:03 <ttx> devananda: ready when you are
17:05:18 <notmyname> ttx: here
17:05:22 <devananda> ttx: o/
17:05:32 <ttx> Let's slip notmyname in those extra 5 min
17:05:36 <ttx> #topic Swift
17:05:48 <notmyname> I've been out and I'm catching up
17:06:12 <notmyname> 4 of us (core devs) are working on EC stuff in the office yesterday and today
17:06:14 <ttx> I had a good break so things are a bit fuzzy in my mind, but I seem to remember we considered some release for end of january
17:06:29 <notmyname> otherwise, we've got some patches that will land for a next release...yeah
17:06:47 <notmyname> I'll let you know when those are good and give you a head's up on timing as soon as I know it
17:06:56 <ttx> sounds good
17:07:20 <ttx> I'll be traveling a bit end of Jan / start of Feb
17:07:25 <ttx> (for work)
17:07:41 <notmyname> I'll be at LCA next week
17:07:41 <notmyname> hmm...looks like 6am there now, so I probably can still do the update
17:07:54 <notmyname> ok
17:08:05 <ttx> notmyname: we can skip next week, I won't make you get up at 6am for 2 min of update
17:08:11 <notmyname> heh, ok
17:08:18 <notmyname> thanks :-)
17:08:27 <notmyname> I think that's all I've got for this week
17:08:45 <ttx> or we can ping more randomly. Actually was thinking we could drop the concept of scheduled pings since we don't have that much to communicate
17:08:58 <ttx> (not just you, everyone)
17:09:19 <ttx> the only real moment we need sync is around releases/milestones
17:09:23 <notmyname> I think the scheduled stuff is good. and offers less chance for communication failures later
17:09:31 <notmyname> I'd prefer to keep them (for everyone)
17:09:35 <ttx> ok, that's good feedback
17:09:51 <ttx> have a great week!
17:09:54 <notmyname> it's at least a time when we both know the other is online
17:09:56 <notmyname> you too!
17:09:59 <ttx> devananda: still around?
17:11:03 <devananda> ttx: yup
17:11:40 <ttx> #topic Ironic
17:12:46 <ttx> #link https://launchpad.net/ironic/+milestone/kilo-2
17:13:08 <devananda> folks are still trickling back in after the holiday break
17:13:09 <ttx> Will set https://blueprints.launchpad.net/ironic/+spec/non-glance-image-refs to "started" since work seems to have happened there
17:13:36 <devananda> we had our first post-new-year meeting last night, which is also part of our attempt to split meetings across time zones
17:13:46 <ttx> how did that go ?
17:13:48 <devananda> so far, I'm not convinced it's going well (the meeting time split, that is)
17:14:23 <ttx> devananda: yeah, it's a difficult balance. You want to be inclusive, but not split them to the point where they are not reaching critical mass either
17:14:30 <devananda> 0500 UTC meetings are hard for US west coast people. we lose all the US east. EU don't attend either.
17:14:50 <devananda> so we get a few sleepy US west, plus china/japan/korea/australia
17:14:51 <ttx> damn earth for being round
17:14:56 <devananda> right?
17:15:35 <devananda> i'm curious if other teams have tried this and gone back to a single time
17:16:01 <ttx> devananda: that's a good question for the cross-project meeting open discussion today
17:16:11 <devananda> duly noted
17:16:34 <devananda> on the topic of mid cycle
17:16:55 <devananda> i'm trying to make it clear to folks that this is a sprint, not planning -- but it's pretty clear we're going to be split
17:17:19 <ttx> yeah, felt that way on the ML
17:18:08 <devananda> I don't have a lot of project updates at this point
17:18:22 <ttx> devananda: do you expect a lot more specs to make it to the k2 page soon ?
17:18:34 <devananda> a few, but not many
17:18:56 <ttx> ok no more questions from me, anything else ?
17:19:20 <devananda> there are a lot of open specs, but most are blocked by other work and either late additions to k3, or more likely won't make it this cycle
17:19:39 <devananda> nope
17:19:43 <devananda> cheers :)
17:19:44 <ttx> Cool, have a great day and week then
17:19:53 <ttx> SlickNik: ready when you are
17:20:03 <SlickNik> o/
17:20:08 <ttx> #topic Trove
17:20:13 <ttx> #link https://launchpad.net/trove/+milestone/kilo-2
17:20:32 <ttx> Looks pretty good, most code already in review
17:20:38 <ttx> expecting a lot more to come ?
17:20:41 <SlickNik> Chugging along trying to get the BPs for kilo-2 reviewed.
17:20:54 <SlickNik> Expecting a couple more to show up, but not much else.
17:21:19 <SlickNik> Should be in during the next week/two as well.
17:21:52 <ttx> ok, no more questions from me
17:22:00 <ttx> questions on your side ?
17:22:12 <SlickNik> Will keep the BPs updated — a couple are close to merging.
17:22:19 <SlickNik> None so far.
17:22:30 <ttx> OK then, have a good back-from-holiday week
17:22:39 <SlickNik> Thanks!
17:22:40 <ttx> #endmeeting