08:59:02 <ttx> #startmeeting ptl_sync
08:59:03 <openstack> Meeting started Tue Jan 13 08:59:02 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:59:04 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:59:07 <openstack> The meeting name has been set to 'ptl_sync'
08:59:09 <ttx> asalkeld: around?
08:59:18 <asalkeld> hi ttx
08:59:20 <ttx> #topic Heat
08:59:28 <ttx> #link https://launchpad.net/heat/+milestone/kilo-2
08:59:34 <ttx> asalkeld: o/
08:59:44 <asalkeld> is that ok?
08:59:51 <asalkeld> tried to prune stuff
08:59:56 <asalkeld> on in unknown state
09:00:02 <asalkeld> s/on/one
09:00:11 <asalkeld> https://blueprints.launchpad.net/heat/+spec/support-cinderclient-v2
09:00:16 <asalkeld> need to checkup on that
09:00:20 <ttx> ok
09:00:46 <ttx> I'd say you're a bit late in progress
09:01:04 <asalkeld> what do you mean?
09:01:17 <ttx> You should have more stuff in review if you want to complete all those targets :)
09:01:28 <ttx> (only 3 weeks left)
09:01:38 <asalkeld> i think it's ok
09:02:09 <asalkeld> there are patches up for all but the unknow one
09:02:10 <ttx> #info 1 done, 1 inreview, 4 inprogress, 1 uhnknown
09:02:46 <ttx> OK -- do you have specific deadlines for Heat ? Trying to collect them and list them on the cycle page
09:03:03 <ttx> like a spec proposal or a spec approval deadline
09:03:04 <asalkeld> nothing specific
09:03:08 <ttx> ok good
09:03:25 <ttx> We'll skip next week sync point as I'll be travelling
09:03:31 <asalkeld> ok
09:03:45 <asalkeld> i'll update the states of thoes bps
09:03:45 <ttx> so tyalk to you in two weeks, or ping me before if you have something urgent
09:03:51 <asalkeld> cool
09:04:02 <ttx> asalkeld: have a good day!
09:04:10 <asalkeld> you too
09:04:15 <ttx> johnthetubaguy: ready when you are
09:04:36 <johnthetubaguy> ttx: I was just going to do a quick coffee run, back in 5
09:04:45 <ttx> sounds like a good idea.
09:08:40 * johnthetubaguy has smelt the coffee now
09:08:47 <ttx> #topic Nova
09:08:56 <ttx> #link https://launchpad.net/nova/+milestone/kilo-2
09:09:25 <ttx> #info 22 inreview, 29 inprogress, 17 notstarted
09:09:42 <johnthetubaguy> yes, fun fun
09:10:03 <johnthetubaguy> its looking like a pending blood bath at the end of kilo-2
09:10:22 <johnthetubaguy> I need to send a mail that just talks about that deadline later
09:10:35 <ttx> At this point I'd say the High "Not started" ones should really get started... and the Low "Not started" ones should start feeling the heat
09:11:17 <johnthetubaguy> yes, the high are likely to slip to kilo-3 at this point
09:11:25 <ttx> Could you remind me of the Nova deadlines ?
09:11:57 <johnthetubaguy> sure, two weeks before kilo-2 I plan to cut everything that does not have any code up
09:12:08 <johnthetubaguy> well, doesn't have all code up
09:12:18 <johnthetubaguy> priority list items go to kilo-3
09:12:23 <johnthetubaguy> other stuff goes to l
09:12:33 <johnthetubaguy> basically its feature freeze for stuff not on the priority list
09:13:00 <johnthetubaguy> there will be exceptions, but we don't want to grant them till blueprints are completed, to try and manage the review bandwidth, but lets see
09:13:06 <johnthetubaguy> does that make sense?
09:13:19 <ttx> so a non-priority-feature-code-proposal deadline on... Jan 22 ?
09:13:58 <johnthetubaguy> yes
09:14:13 <ttx> #info Nova non-priority-feature-code-proposal on Jan 22
09:14:48 <ttx> I've seen the rush for exceptions on the list already
09:15:04 <johnthetubaguy> yes, I need to work through those
09:15:12 <johnthetubaguy> there are quite a few priority things, which we should approve
09:15:19 <johnthetubaguy> the other stuff, I hope we can mostly push back on
09:15:27 <ttx> right, need to map them to the prio list
09:15:49 <johnthetubaguy> it should be in the spec in gerrit, but I might reply to the list to confirm the priority ones, that could help
09:15:55 <ttx> we'll skip the 1:1 next week as I'll be on a staff sprint, but feel free to ping me if you need me
09:16:15 <johnthetubaguy> Ok, thats cool
09:16:23 <johnthetubaguy> the week after, its the nova-meetup
09:16:31 <johnthetubaguy> so might be catching up with you later in the day, if thats OK
09:16:37 <ttx> sure, no pb
09:16:42 <johnthetubaguy> cool, thanks
09:16:45 <ttx> anything else ?
09:16:51 <johnthetubaguy> I think thats all for now
09:16:59 <ttx> johnthetubaguy: ok, have a good day and week!
09:17:03 <johnthetubaguy> and you!
12:59:55 <eglynn> ttx: knock, knock whenever you're ready
13:02:07 <ttx> eglynn: sorry was busy replying to privacy vs. logging nonsense
13:02:17 <ttx> #topic Ceilometer
13:02:28 <eglynn> ttx: np!
13:02:30 <eglynn> #link https://launchpad.net/ceilometer/+milestone/kilo-2
13:02:34 <ttx> Ah, Daniel beat me to it
13:02:58 <eglynn> so some progress in unblocking k2 BPs where the specs review hadn't landed
13:03:10 <eglynn> still a couple in the blocked state
13:03:15 <ttx> ack
13:03:21 <eglynn> if not resolved by EoW I'll bump off kilo-2
13:03:47 <ttx> #info 3 inreview, 4 inprogress, 2 blocked
13:04:15 <ttx> We'll skip the 1:1s next week
13:04:16 <eglynn> other than that progress continues ... cdent is making waves with gabbi
13:04:26 <ttx> I'm travelling and will probably be off
13:04:34 <ttx> just ping me if anything urgent surfaces
13:04:38 <eglynn> (the underpinnings of declarative-http-tests, but also useful accross the baord for API testing)
13:04:41 <eglynn> coolness
13:04:52 <ttx> yep, read that thread, I think this is a good thing
13:05:03 <eglynn> cool
13:05:14 <ttx> I was wondering if there were any special deadline the ceilometer team would like to implement
13:05:22 <ttx> want to document them on the release cycle page
13:05:37 <ttx> so if you have a spec deadline, or code proposal deadline... let me know
13:05:52 <ttx> (by default we only have feature freeze on kilo-3 day
13:05:54 <ttx> )
13:06:08 <eglynn> a-ha, k, I discuss that with the team at the weekly meeting on Thurs
13:06:40 <ttx> there used to be convergence around those but this cycle it's all over the map, so I figured I should try to list them all to clarify
13:06:55 <eglynn> yeap, good idea
13:07:39 <ttx> on the progress side, I feel like this is still going a bit slow, hopefully people will switch gears in the coming 3 weeks
13:07:54 <ttx> you're not the only project in that situation :)
13:08:06 <ttx> That's all I had -- anything on your side ?
13:08:07 <eglynn> yeah, last week let like folks just waking up
13:08:20 <eglynn> nope, that's all for me
13:08:45 <eglynn> *felt like
13:08:50 <eglynn> thanks for your time!
13:08:58 <ttx> eglynn: have a good week!
13:10:01 <ttx> SergeyLukjanov: ready when you are
13:19:41 <dhellmann> ttx: hi
13:19:47 <ttx> #topic Oslo
13:19:50 <ttx> dhellmann: o/
13:20:09 <ttx> #link https://launchpad.net/oslo/+milestone/kilo-2
13:20:22 <ttx> #link https://launchpad.net/oslo/+milestone/next-kilo
13:21:08 <dhellmann> we cleaned up the k-2 list a bit since last week
13:21:10 <ttx> How many libs are left to migrate to the non-namespace world ?
13:21:54 <dhellmann> we need to patch oslo.vmware (in flight) and then we have 4 more to release
13:22:05 <dhellmann> that's 4 after the vmware patch lands
13:22:19 <dhellmann> we could do oslo.rootwrap any time you're ready for a release
13:22:20 <ttx> ok, so likely to be completed at k2 or start of k3, good
13:22:39 <dhellmann> yeah, I expect to release them all in the next ~1.5 wks
13:22:42 <ttx> dhellmann: there was a bug reported that I could try to fix, let me up the prio on my todo list
13:22:48 <dhellmann> ok
13:22:59 <ttx> if I don't get to it this week, we'll just release with the namespace package drop
13:23:36 <ttx> Do you have any oslo-specific deadline this cycle ?
13:23:56 <ttx> Like all graduations must be completed by X, or all feature code must be proposed by Y ?
13:24:06 <dhellmann> no, we haven't proposed anything like that
13:24:07 <ttx> (by default we only have feature freeze on kilo-3 day)
13:24:25 <ttx> ok -- if you do, keep me posted. I'd like to document them all to reduce confusion
13:24:41 <ttx> Also I'll skip next week's 1:1 because I'll be traveling
13:24:42 <dhellmann> certainly
13:24:48 <ttx> ping me for anything urgent
13:24:54 <dhellmann> oh, we'll probably freeze a week or so earlier than k-3 like we did last cycle
13:25:05 <dhellmann> we haven't picked a date, I'll put that on my list of things I need to figure out
13:25:24 <ttx> dhellmann: freeze as in code freeze, or code proposal freeze ?
13:25:36 <ttx> i.e. no more n,ew code to review, or no more code merged ?
13:25:36 <dhellmann> feature freeze
13:25:46 <ttx> ok, so no more code merged
13:26:02 <dhellmann> well, unless we have to fix bugs to allow the other projects to move ahead
13:26:09 <ttx> #info Oslo feature freeze likely to happen one week before the kilo-3 common freeze
13:26:23 <ttx> makes sense for libraries and probably keystone
13:26:36 <dhellmann> yeah, it worked pretty well for us last cycle
13:26:56 <ttx> dhellmann: ok, anything else ?
13:27:19 <dhellmann> nothing from me
13:28:13 <ttx> dhellmann: ok then, have a good day and week! Talk to you later
13:28:20 <dhellmann> ttx: thanks, you too!
13:29:08 <ttx> SergeyLukjanov: you can still go now if you want
15:00:52 <mestery> ttx: Ready when you are
15:01:43 <ttx> mestery: hi!
15:01:46 <ttx> #topic Neutron
15:02:01 <ttx> #link https://launchpad.net/neutron/+milestone/kilo-2
15:02:33 <mestery> FYI: We discussed all "Essential" and "High" priority BPs in our meeting just now
15:02:35 <mestery> #link http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-01-13-14.02.html
15:02:44 <mestery> So the broader logs for more information
15:02:49 <ttx> #info 3 done, 18 inreview, 6 inprogress, 5 notstarted
15:02:52 <mestery> #link http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-01-13-14.02.log.txt
15:03:42 * ttx quicklooks
15:04:03 <mestery> Bottom line: I expect some of those to slip to Kilo-3 as they always do :)
15:04:05 <mestery> But we're making good progress in others
15:04:48 <ttx> yep, but overall you don't seem completely off
15:04:57 <mestery> No, we're doing pretty good this time around actually!
15:05:01 <ttx> lots of stuff in review already
15:05:03 <mestery> People are focused on the right thigns now, which helps
15:05:11 <ttx> so now would be a good time to land them
15:05:20 <mestery> Yes
15:05:46 <mestery> Also, as far as this is concerned:
15:05:48 <mestery> #link http://specs.openstack.org/openstack/neutron-specs/specs/kilo/core-vendor-decomposition.html
15:05:51 <mestery> We're making great progress!
15:06:00 <mestery> Lots of people decomposing their plugins and moving code to stackforge, github, etc.
15:06:05 <mestery> I'm pleasantly surprised actually
15:06:06 <mestery> ;)
15:06:16 <ttx> mestery: cool
15:06:37 <ttx> I seem to remember you have specific deadlines already announced
15:06:51 <mestery> Yes, and armax has been great at helping people here.
15:06:53 <ttx> I'm collecting them so I can docuemnt them all
15:07:17 <mestery> ttx: The spec indicates plugins/drivers should make progress during Kilo, and during Lxxx we may take efforts to remove those which are not complying
15:07:21 <mestery> I wanted to give two cycles for this, so we did :)
15:07:32 <ttx> More generally, do you have a spec proposal/approval deadline ? Or a code proposal deadline ?
15:08:13 <mestery> Yes: SPD/SAD was 12-8-2014 and 12-15-2104
15:08:15 <mestery> *2014
15:08:17 <mestery> Those passed last year :)
15:08:21 <ttx> right
15:08:30 <ttx> I'll still document them for posterity :)
15:08:45 <mestery> Got it, and thanks!
15:08:47 <ttx> #info SPD was 12-8-2014 and SAD was 12-15-2104
15:08:53 <mestery> lol
15:08:56 <mestery> 12-15-2014
15:09:03 <mestery> My typo made it to your #info! :)
15:09:13 <ttx> don't underestimate my capacity to copypaste
15:09:24 <mestery> rofl
15:09:47 <ttx> do you already have a code proposal deadline ? or you expect to follow the usual one two weeks before FF ?
15:09:56 <mestery> Yes, we'll follow the usual I suspect
15:10:13 <ttx> #info Likely to have CPF two weeks before kilo-3
15:10:36 <ttx> We'll be skipping 1:1s next week -- ping me if you have an uregnt question or topic to discuss
15:10:47 <ttx> That's all I had
15:10:56 <mestery> ACtually, that works out great, I'm travelling next week so would have had to miss anyways ;)
15:11:04 <ttx> hah! awesome
15:11:06 <mestery> I'll have more stats on plugin decomposition in two weeks for you
15:11:08 <mestery> Just to track progress.
15:11:11 <mestery> Thats all from me, thanks!
15:11:13 <ttx> Ok then, have a good day and week
15:11:33 <mestery> you too!
15:15:44 <SergeyLukjanov> ttx, I'm sorry for being late :( calendar reminder ended last week...
15:15:53 <ttx> heh
15:15:53 <SergeyLukjanov> ttx, if you're able to make a sync now..
15:16:01 <ttx> SergeyLukjanov: you have 5 min now if you want
15:16:11 <ttx> #topic Sahara
15:16:22 <SergeyLukjanov> ttx, probably it'll be better for you to use another time today?
15:16:22 <ttx> #link https://launchpad.net/sahara/+milestone/kilo-2
15:16:29 <ttx> SergeyLukjanov: no fine now
15:16:43 <ttx> #info 7 inreview, 1 inprogress, 2 blocked
15:17:15 <ttx> Time to turn some of those to "implemented", otherwise looks good
15:17:17 <SergeyLukjanov> yeah, blocked are now candidates to be moved to kilo3
15:17:29 <ttx> Any specific deadlines announced for Sahara ?
15:18:20 <SergeyLukjanov> ttx, I think no, everything is going ok
15:18:36 <ttx> ok, so just the feature freeze on kilo-3
15:18:52 <SergeyLukjanov> ttx, FPF at March 5 will be used I think
15:18:53 <ttx> We'll skip 1:1s next week, ping me if urgent questions arise
15:19:22 <ttx> #info Likely to have FPF two weeks before kilo-3
15:19:26 <SergeyLukjanov> ttx, okay, thank you, sorry again about being late, already created reminders for the whole year
15:19:43 <ttx> SergeyLukjanov: sounds all good -- talk to you later
15:19:57 <ttx> nikhil_k: ready when you are
15:20:00 <nikhil_k> ttx: o/
15:20:04 <ttx> #topic Glance
15:20:24 <ttx> #link https://launchpad.net/glance/+milestone/kilo-2
15:20:33 <ttx> #info 1 inreview, 1 notstarted
15:20:47 <ttx> Sounds manageable
15:21:05 <nikhil_k> ttx: yeah, we've some glance_store specs/BPs
15:21:20 <nikhil_k> however, they do not come in this milestone release cycle
15:21:24 <ttx> I didn't notice any specific deadline for Glance apart from Feature Freeze on kilo-3
15:21:33 <ttx> let me know if I missed any
15:21:57 <nikhil_k> We've an inofficial one ~2 weeks after k-2
15:22:15 <nikhil_k> Where would you like me to post that bulletin?
15:22:27 <ttx> I can #info it
15:22:30 <ttx> what is it ?
15:22:48 <ttx> some code proposal freeze ?
15:22:57 <ttx> or spec freeze ?
15:23:07 <nikhil_k> We want all the features to be code-ready (good for approvals) 2 weeks after k-2
15:23:23 <ttx> ok, so feature/code proposal freeze
15:23:28 <nikhil_k> yes
15:23:36 <ttx> #info FPF 2 weeks after k2
15:23:39 <ttx> Wanted to ask you for confirmation before formally adding Erno to glance-stable-maint
15:23:59 <ttx> I briefed him on stable policy so he is good ot go if you +1 it
15:24:00 <nikhil_k> ttx: I've communicated to most of folks that specs would not be officially approved unless a decent amount of code is posted
15:24:17 <nikhil_k> ttx: ok, your topic first
15:24:43 <nikhil_k> ttx: I'm okay with it. One question: does the glance-stable-maint apply to all the repos in the program?
15:24:56 <ttx> nikhil_k: only those with a stable branch
15:25:05 <ttx> so probably only openstack/glance
15:25:27 <nikhil_k> ttx: cool. We should soon have glance_store to the list
15:25:35 <ttx> ok
15:25:51 <ttx> so, specs requiring some code to be approved
15:25:56 <nikhil_k> so, does that mean he and I are in that group?
15:26:04 * ttx checks group
15:26:22 <nikhil_k> ttx: wondering how could I add more people when necessary?
15:26:26 <ttx> Currently Flavio and you in the group
15:26:33 <nikhil_k> ah ok
15:27:01 <ttx> nikhil_k: if you feel it's necessary you can propose other people. We'll reach out to them to teach/explain them stable policy and then add them
15:27:15 <ttx> but I would go with the 3 and see how it goes
15:27:21 <nikhil_k> That sounds good.
15:27:29 <ttx> better keep an active small group, there aren't that many backports to review
15:27:48 <nikhil_k> Actually. I've someone really good for that job, in mind.
15:27:54 <nikhil_k> Anyways, until next time...
15:28:08 <ttx> about specs requiring some code to be approved, I don't think other projects do that but that shouldn't prevent you from doing it
15:28:19 <nikhil_k> ah ok
15:28:21 <ttx> let me know how that goes
15:28:22 <nikhil_k> the issue is
15:28:28 <nikhil_k> ok
15:28:48 <ttx> I'll miss the 1:1 sync next week, ping me if you have questions
15:28:59 <nikhil_k> sure thing! Appreciate it/
15:29:03 <ttx> Anything you wanted to mention now ?
15:29:12 <nikhil_k> one question
15:29:34 <nikhil_k> Would you like to track glance_store specs/BPs in the launchpad milestone
15:29:43 <nikhil_k> so that it comes in the release notes at the end of the cycle
15:30:00 <nikhil_k> however, that project does not follow the milestone dates
15:30:06 <nikhil_k> it has it's own releases
15:30:15 <ttx> nikhil_k: actually depends how you consider glance_store. My understanding is that it's a library which strives to have backward compat, much like oslo libs
15:30:28 <nikhil_k> yeah
15:30:31 <ttx> those don't have formal stable branches, more like semver versioning
15:30:44 <nikhil_k> gotcha
15:30:49 <ttx> so we usually track them separately (different version numbers)
15:31:00 <ttx> better release them separately as well
15:31:07 <nikhil_k> okay, I will try to do that and get back to you if run into issues
15:31:11 <ttx> if you want a template, consider using the ones in oslo
15:31:14 <ttx> sure
15:31:17 <ttx> thingee: around?
15:31:24 <ttx> nikhil_k: thx!
15:31:26 <thingee> ttx: hello!
15:31:26 <nikhil_k> Thanks
15:31:29 <ttx> #topic Cinder
15:31:41 <ttx> #link https://launchpad.net/cinder/+milestone/kilo-2
15:32:01 <thingee> I moved out the ones that haven't started
15:32:09 <thingee> contacted people individually
15:32:13 <ttx> #info 2 done, 17 inreview, 6 started
15:32:16 <ttx> Looks good to me
15:32:34 <thingee> I have put reminders in the ones in review with no updates in a while that a reminder of k-2 deadline
15:32:34 <ttx> yeah, that sounds reasonable (removing not started at this point)
15:32:50 <thingee> just left comments in review. might email people too
15:33:11 <ttx> So if I remember correctly, you have a non-priority feature freeze at k2, much like Nova does
15:33:24 <ttx> then only priority stuff / exceptions alowed in k3
15:33:27 <thingee> this week, the plan is to get on people with no code yet for their spec. I'm worried about some people that have multiple things assigned this milestone
15:33:33 <ttx> is that right?
15:34:04 <thingee> ttx: that is correct. In fact I set a topic for our meeting tomorrow as a reminder. email to the list to follow
15:34:20 <ttx> thingee: yes, people sometimes sign up for 3 things and deliver none, while if they signed up for one they would have completed it
15:35:27 <ttx> #info Non-priority feature freeze at kilo-2
15:35:41 <ttx> (trying to keep track of them all)
15:36:12 <ttx> ok, you seem to have things under control. We'll skip 1:1s next week as I'm traveling
15:36:21 <ttx> Feel free to ping me as needed though
15:36:31 <thingee> ok, hope it's fun traveling
15:36:52 <ttx> Should be fun traveling yes. Foundation staff retreat
15:36:56 <ttx> Questions on your side ?
15:37:03 <thingee> sounds great
15:37:07 <thingee> nope
15:37:16 <ttx> alright then, have a great day & week
15:37:34 <thingee> have a great rest of your day too
15:38:33 <thingee> btw, cross project meeting today is still marked to be confirmed.
15:38:44 <ttx> oh. Fixing that now. I sent a reminder this morning
15:39:02 <ttx> thx for the heads-up
16:58:01 <ttx> morganfainberg: I'll be 5 min late
17:03:47 <morganfainberg> ttx, np
17:07:10 <ttx> morganfainberg: back
17:07:15 <ttx> #topic Keystone
17:07:32 <morganfainberg> ttx, wb
17:07:38 <ttx> #link https://launchpad.net/keystone/+milestone/kilo-2
17:07:58 <morganfainberg> bugs are trickling in / being assigned
17:08:17 <ttx> #info 4 inreview, 4 inprogress, 2 notstarted
17:08:35 <ttx> Looks like this is on track
17:08:46 <ttx> Though the not started ones should probably get started soon
17:08:51 <morganfainberg> we might have a couple smaller specs and associated BPs land in k2 as well
17:08:59 <ttx> ok
17:09:02 <morganfainberg> i'm still curating before assignign and marking as blocked
17:09:10 <ttx> Do you have any specific deadlines in Keystone ?
17:09:17 <morganfainberg> k2 is spec-proposal-deadline
17:09:30 <ttx> #info spec proposal deadline at K2
17:09:38 <ttx> I'm trying to collect them all
17:09:42 <morganfainberg> though next cycle i hope we can roll that back a good deal.
17:09:55 <morganfainberg> i hate cramming all the spec code into m3
17:10:08 <ttx> any other ? (apart from classic Feature freeze at k3)
17:10:20 <ttx> Maybe the code proposal freeze two weeks before k3 ?
17:10:34 <morganfainberg> yeah i'll float that at the meeting today, but no one should complain
17:10:51 <ttx> #info probably a code proposal freeze two weeks before k3
17:11:15 <ttx> In other news, I added the keystonemiddleware / keystoneclient deprecation discussion to the TC agenda
17:11:20 <morganfainberg> cool
17:11:21 <ttx> will you be around ?
17:11:21 <morganfainberg> thanks
17:11:23 <morganfainberg> yes
17:11:38 <ttx> OK, hopefully we'll have time to discuss it -- it's in a deep agenda
17:11:39 <morganfainberg> i expect it to go mostly with sdagues recommendation
17:11:54 <ttx> Also we'll skip 1:1s next week as I'll be away
17:11:57 <morganfainberg> but this is a case where the TC signing off on it would be good.
17:12:09 <ttx> ping me if anything urgent comes (unlikely but...)
17:12:13 <morganfainberg> keystone midcycle is next week, I was going to ask for a skip anyway
17:12:19 <ttx> hah, good
17:12:23 <morganfainberg> enjoy the foundation off-site! :)
17:12:28 <ttx> Alright, that's all I had
17:12:45 <ttx> morganfainberg: have a good day and week and nextweek !
17:12:53 <morganfainberg> cheers.
17:12:54 <ttx> devananda: around?
17:13:06 <devananda> ttx: sorta
17:13:16 <ttx> #topic Ironic
17:13:21 <ttx> shouldn't take long
17:13:24 <devananda> k k
17:13:29 <ttx> #link https://launchpad.net/ironic/+milestone/kilo-2
17:13:38 <devananda> biggest news on my end is rackspace confirmed they'll host a second sprint in SF
17:13:42 <ttx> #info 4 inreview, 3 inprogress, 4 blocked
17:13:43 <devananda> I updated the wiki page with details
17:14:24 <ttx> I suspect you have code lined up for those Blocked ones, just pending spec approval ?
17:14:34 <devananda> as far as k2 milestone, I have a suspicion that many things will slip to k3, given that the state machine changes are still underway and blocking several other specs
17:14:43 <ttx> oh, ok
17:15:01 <ttx> I'm collecting project-specific deadlines -- do you have any in Ironic ?
17:15:08 <devananda> nope - w
17:15:19 <devananda> we're following the general guidelines this cycle
17:15:28 <ttx> ok
17:15:38 <ttx> we'll skip next week's 1:1s
17:15:46 <ttx> That's all I had
17:16:13 <ttx> #info State machine blocking several specs, expecting some deferrals to k3
17:16:26 <ttx> devananda: have a good day and week!
17:16:34 <devananda> ttx: cheers! you too
17:16:40 <ttx> SlickNik: ready when you are
17:30:43 <ttx> Hmm, I guess we'll skip Trove today
17:35:16 <ttx> ok, let's skip
17:35:19 <ttx> #endmeeting