09:04:45 <ttx> #startmeeting ptl_sync
09:04:46 <openstack> Meeting started Tue Feb 24 09:04:45 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:04:47 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:04:49 <openstack> The meeting name has been set to 'ptl_sync'
09:04:51 <ttx> #topic Heat
09:04:54 <asalkeld> sorry, a bit late
09:05:19 <ttx> #link https://launchpad.net/heat/+milestone/kilo-3
09:05:41 <ttx> What's the status of those "Unknown" ? Just not started, or really unknown ?
09:06:06 <asalkeld> the convergence ones are been worked on
09:06:12 <asalkeld> i'll update those
09:06:35 <asalkeld> the barbican one i might push to L
09:06:57 <ttx> OK, and keep "Unknown" for when you have no idea -- use "not started" for those that are just not started
09:07:08 <asalkeld> ok, makes sense
09:07:27 <ttx> Remember Feature Proposal Freeze is Thursday next week, and ISTR you said you would follow it*
09:07:43 <ttx> that means that everything should be "needs code review" in 10 days :)
09:07:58 <asalkeld> wow, ok
09:08:04 <ttx> so yeah, early defrring of stuff not started that won't make it sounds like a good idea
09:08:21 <ttx> I mean, you can also decide to not enforce FPF
09:08:41 <ttx> but generally that doesn't really result in better situations at the end of the line
09:08:48 <asalkeld> ok
09:09:00 <ttx> especially if you piled up enough reviews for the last 2 weeks already
09:09:01 <asalkeld> i'll chase the status of these up
09:09:35 <asalkeld> i am hopefully most of those will land
09:09:42 <asalkeld> they are small bp's
09:09:54 <asalkeld> just broken up to spread the load
09:09:54 <ttx> ok
09:10:00 <ttx> On the design summit space request side, you indicated that you would confirm the proposed allocation in a meeting
09:10:14 <asalkeld> when do you need that info?
09:10:27 <ttx> well, I don't need a final request, just an idea
09:10:42 <asalkeld> we have a meeting in 1.5days
09:10:43 <ttx> But I need it asap
09:10:54 <asalkeld> i ways hoping to canvas there
09:11:03 <ttx> ok, that works
09:11:07 <asalkeld> cool
09:11:48 <ttx> That's about all I had. i'll add proposed changes to release tracking to discuss at the cross-project meeting tomorrow morning for you
09:12:09 <asalkeld> ok
09:12:14 <ttx> If you can't make it --> https://wiki.openstack.org/wiki/Release_Cycle_Management/Liberty_Tracking
09:12:26 <asalkeld> thanks
09:12:39 <ttx> asalkeld: anything else ?
09:12:46 <asalkeld> all ok from my side
09:12:57 <ttx> zz_johnthetubagu: awake?
09:13:04 <ttx> asalkeld: ok, have a great day
09:13:08 <ttx> err..; evening
09:13:15 <asalkeld> ttx: you too
09:16:59 <johnthetubaguy> ttx: hi, just going to head down to get a coffee, will only be 2 mins hopefully
09:17:26 <ttx> standing by
09:23:35 <johnthetubaguy> ttx: hi
09:24:02 <ttx> #topic Nova
09:24:05 <ttx> johnthetubaguy: o/
09:24:27 <ttx> #link https://launchpad.net/nova/+milestone/kilo-3
09:24:43 <ttx> Is that ~current with the Goals + non-goal FFEs list ?
09:24:57 <johnthetubaguy> yes
09:25:18 <johnthetubaguy> although the non implemented FFEs will get bumped today/tomorrow, in theory
09:25:50 <ttx> We have feature proposal freeze next week on Thursday
09:25:54 <johnthetubaguy> so I need to chase some folks down to see how much they will have by feature proposal freeze
09:26:02 <ttx> does it look like your goals will make it ?
09:26:29 <johnthetubaguy> honestly, a few are touch and go, but looks like they should all get something useful up
09:26:41 <johnthetubaguy> I will try push people for answers on some of those
09:26:43 <ttx> ok
09:27:19 <ttx> Separate topic, I asked mikal for an idea of the mix between fishbowl and work room sessions for the next summit
09:27:35 <johnthetubaguy> did you get an answer from him?
09:27:48 <ttx> (I expect nova to use 18 sessions as always, but I need an idea of what the mix should look like
09:27:50 <ttx> )
09:27:53 <ttx> No he didn't yet
09:28:01 <ttx> Was wondering if you discussed it in any Nova meeting
09:28:16 <johnthetubaguy> so I think going with the assumption of the same as last time, but I haven't brought that up I am afraid
09:28:54 <johnthetubaguy> when is the drop dead time for an answer?
09:29:01 <ttx> johnthetubaguy:  the new thing is that for normal sessions, you can pick between fishbowl where you want large attendance, and work rooms where you would rather keep it for the nova team
09:29:13 <johnthetubaguy> ah got you
09:29:37 <ttx> and that's a team discussion on how you best want to use your time there
09:29:57 <ttx> other teams generally pickes a 1/3 2/3 mix (1/3 fishbowl)
09:30:01 <johnthetubaguy> yeah, for sure, we had lots of good comments about the mix last time
09:30:19 <ttx> anyway, I'll reach out to mikal
09:30:33 <johnthetubaguy> cool, I will put it on the nova meeting agenda before I forget
09:30:55 <ttx> I'll also discuss at the cross-project meeting tonight evolution in release tracking for Liberty, as previously discussed here
09:31:04 <ttx> If you can't make it --> https://wiki.openstack.org/wiki/Release_Cycle_Management/Liberty_Tracking
09:31:11 <johnthetubaguy> ah, cool, thank you
09:31:21 <ttx> That's all I had
09:31:29 <ttx> Anythign on your side ?
09:31:37 <johnthetubaguy> cool, thanks for the updates, I don't think there is much with us
09:31:46 <ttx> ok, ttyl then
09:32:05 <johnthetubaguy> thanks, talk to you soon
09:37:54 <johnthetubaguy> ttx: FWIW I am totally +1 your ideas in that liberty tracking wiki page, a really nice writeup
09:38:08 <ttx> cool, thx
13:00:10 <eglynn> ttx: knock, knock, ready when you are
13:01:20 <ttx> o/
13:01:26 <ttx> #topic Ceilometer
13:01:44 <ttx> #link https://launchpad.net/ceilometer/+milestone/kilo-3
13:01:50 <ttx> Looks all good
13:02:26 <ttx> Had a question on design sumit space requests -- you mention on the sheet that you still need to confirm your proposed allocation
13:02:35 <ttx> shall I consider the guess confirmed now ?
13:02:43 <ttx> It's not a final request anyway, just an overall idea
13:02:52 <ttx> so we can work on room layout
13:03:07 <eglynn> yeah, does the initial request look out of line to you?
13:03:21 <ttx> no no, was just wondering how final that guess was
13:03:30 <ttx> much less crazy than others iirc
13:03:47 <eglynn> cool, otherwise, I'd be happy go with that
13:03:49 <eglynn> ... with the understanding that there's more horse trading to come
13:03:55 <ttx> definitely
13:03:58 <eglynn> coolness
13:04:24 <ttx> In other news we'll discuss liberty release tracking at the cross-project meeting tonight
13:04:44 <ttx> mostly the idea of switching to tracking what landed rather than predicting what will likely not land
13:04:44 <eglynn> just thinking BTW, does danpb's "modest proposal" warrent a cross project meeting agenda item?
13:04:52 <eglynn> a-ha OK
13:04:55 <eglynn> #link http://lists.openstack.org/pipermail/openstack-dev/2015-February/057614.html
13:05:15 <eglynn> ... or let that discuss play out a bit more first
13:05:19 <eglynn> *discussion
13:05:19 <ttx> Missed the call for today's meeting, and discussion is only starting
13:05:27 <eglynn> yeap, fair enough
13:05:29 <ttx> i expect it to bleed onto that release trackign discussion though
13:05:38 <eglynn> yeah, I expect so too
13:05:39 <ttx> and definitely a topic for next week
13:05:42 <eglynn> agreed
13:06:20 <ttx> OK, that is all from me
13:06:26 <eglynn> yep, that's all I had also
13:06:30 <eglynn> thanks for your time!
13:06:37 <ttx> remember FPF is Thursday next week, if you want to enforce it
13:06:53 <eglynn> yeap, I intend to
13:10:17 <ttx> SergeyLukjanov: o/
13:11:00 <SergeyLukjanov> o/
13:11:04 <ttx> #topic Sahara
13:11:04 <SergeyLukjanov> ttx, hi
13:11:13 <SergeyLukjanov> #link https://launchpad.net/sahara/+milestone/kilo-3
13:11:13 <ttx> #link https://launchpad.net/sahara/+milestone/kilo-3
13:11:17 <SergeyLukjanov> oops :)
13:11:39 <ttx> Looks relatively good, lots of not started 10 days from feature proposal freze
13:12:21 <SergeyLukjanov> FPF is March 5?
13:12:36 <ttx> last time I looked yes
13:12:41 <ttx> But then you can ignore it
13:12:58 <ttx> since two weeks befroe FF might be a bit heavy for you
13:14:48 <SergeyLukjanov> yeah
13:14:57 <SergeyLukjanov> (was checking the release page)
13:15:08 <ttx> anyway, those "High" not started should probably get goin,g
13:15:18 <SergeyLukjanov> I'm not expecting new big proposals
13:15:38 <SergeyLukjanov> ttx, it's a good chance that we'll postpone several of them :(
13:16:14 <ttx> In other news we'll discuss the possibility to simplify release tracking for liberty at the Cross-Project meeting today
13:16:26 <ttx> If you can't make it --> https://wiki.openstack.org/wiki/Release_Cycle_Management/Liberty_Tracking
13:17:05 <SergeyLukjanov> yeah, I saw this item, I'll be on the meetings
13:17:06 <ttx> That is all I had. Questions on your side ?
13:17:25 <SergeyLukjanov> (I'm just mostly always very quiet on this meetings :) )
13:17:34 <SergeyLukjanov> nope, I think nothing more from my side
13:17:35 <ttx> heh
13:17:42 <ttx> ok then talk to you later
13:17:47 <ttx> dhellmann: around?
13:18:08 <SergeyLukjanov> ttx, thx
13:19:18 <dhellmann> ttx: I'm here, but also just diving into a nova issue
13:19:31 <ttx> dhellmann: want to postpone ?
13:20:43 <dhellmann> yeah, can I have 10-15 min?
13:21:00 <dhellmann> I have all the people I need together, so we should be able to resolve the path forward shortly
13:21:12 <ttx> sure
13:21:15 <ttx> ping me when ready
13:21:20 <ttx> i'm not moving anywhere
13:35:32 <dhellmann> ttx: ok, that took longer than expected but I think we're clear
13:36:38 <ttx> ok
13:36:43 <ttx> #topic Oslo
13:36:50 <ttx> #link https://launchpad.net/oslo/+milestone/kilo-3
13:37:14 <ttx> dhellmann: I think you'll want to cull that list early rather than late
13:37:35 <dhellmann> ttx: yeah, I need to weed
13:37:41 <ttx> there is little point in releasing a new lib if nobody has time to switch to using it
13:38:03 <ttx> do you have a deadline / set date for new graduations ?
13:38:04 <dhellmann> well, I don't agree with that, but we haven't seen progress on a couple of those
13:38:20 <dhellmann> no, we just work constantly with the idea that adoption can start during the next cycle if it needs to
13:38:47 <ttx> dhellmann: ok, so we maintain the code on the incubator stable branch ?
13:39:09 <dhellmann> right
13:39:10 <ttx> i.e. if adoption happens over a release boundary it's not such a big deal ?
13:39:13 <ttx> ok
13:39:14 <dhellmann> hang on, we've written this down...
13:39:23 <ttx> yes, taht rings a bell :)
13:39:51 <dhellmann> #link http://specs.openstack.org/openstack/oslo-specs/specs/policy/incubator.html#graduation
13:40:49 <ttx> hmm, that's actually a bit unclear
13:40:59 <ttx> "After the first release of the new library, the module(s) should be removed from the master branch of the incubator. During this phase, only critical bug fixes will be allowed to be back-ported to the prior stable branches."
13:41:41 <ttx> so... new lib is released, code is removed from master, stable branch is cut from master
13:42:00 <ttx> there is nowhere to backport to for projects that have not switched to the lib yet
13:43:04 <dhellmann> we expect them to use the previous stable branch -- so things we delete in master are maintained in stable/juno right now, for instance
13:43:04 <ttx> issue detected in nova kilo copy of the code -- fix will only be on that copy because there is no incubator stable branch to sync from ?
13:43:35 <dhellmann> nope, the library, then stable/juno are fixed and nova syncs just that module from stable/juno
13:44:06 <ttx> hmm, wait let me illustrate
13:44:26 <ttx> nova has a copy of incubator foobar module
13:44:53 <ttx> nova syncs new feature added on oslo-incubator master branch
13:45:11 <ttx> oslo.foorbar is released
13:45:28 <ttx> foobar code is removed from oslo-incubator master branch
13:45:37 <ttx> nova releases kilo
13:45:52 <ttx> issue detected in nova's foobar code copy
13:46:23 <ttx> that issue is only present in nova's code copy, not on any of the remaining oslo-incubator branches
13:47:03 <ttx> oslo-incubator master doesn't have it, stable/kilo doesn't have it (being cut from master), stable/juno doesn't have it (since the feature was added in kilo)
13:47:30 <ttx> so there is nowhere for nova to sync from, fix has to land in each code copy
13:47:59 <dhellmann> ugh, my internet just bounced so I'm not sure if my last reply came through
13:48:04 <ttx> (only happens if graduation happens on release boundary)
13:48:07 <dhellmann> (replay) we have not yet had to change modules in the incubator once we identify them as candidates for graduation, so it hasn't been an issue, yet
13:48:14 <dhellmann> right, that step "nova syncs new feature added on oslo-incubator master branch" -- when we identify something for graduation we would try to avoid that step
13:48:21 <dhellmann> if it's a bug fix, we sync it to the stable branch, so that's ok
13:48:29 <dhellmann> the rule is features are not added to the code in nova before they go into the incubator, so if someone violates that rule it's on them to deal with it
13:48:43 <dhellmann> graduation candidates are frozen at the start of the cycle, basically
13:48:46 <ttx> ok
13:49:03 <ttx> works if people follow the rule.
13:49:04 <dhellmann> so even if we don't get to it right away, we're not tracking differences that would cause issues
13:49:14 <ttx> thx!
13:49:17 <dhellmann> most of this code is pretty stable anyway by the time we're ready for graduation
13:49:35 <dhellmann> so, as I said, it hasn't come up, but if it turns into an issue we'll adjust the policy
13:50:02 <dhellmann> we used to allow changes and then try to do backports in master, but that made it harder to do things like allow the master branch to have the import statements updated to use graduated modules
13:50:16 <ttx> #link https://launchpad.net/oslo/+milestone/next-kilo
13:50:45 <ttx> You target the week before FF for the "likely kilo-final" versions of the libraries ?
13:50:53 <dhellmann> that's right
13:51:13 <ttx> OK, that's all the questions I had
13:51:28 <dhellmann> we're working on finalizing that policy: https://review.openstack.org/#/c/153642/
13:51:44 <ttx> You might be interested in the discussion on evolution of release tracking we'll have at the meeting today
13:52:06 <ttx> i.e. switch to tracking what landed rather than track what we think will land
13:52:14 <dhellmann> I haven't caught up with email yet, is there an agenda with a link?
13:52:22 <ttx> https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting
13:52:28 <dhellmann> oh, well, yeah :-)
13:52:30 <ttx> Topic summary @ https://wiki.openstack.org/wiki/Release_Cycle_Management/Liberty_Tracking
13:52:45 <dhellmann> does this relate at all to the product management working group?
13:53:18 <ttx> dhellmann: not really. i reached out to some of them though to check how valid my assumtions were
13:53:28 <dhellmann> ok
13:54:02 <dhellmann> I'll read through that before the meeting, thanks for the heads-up
13:54:05 <ttx> basically they prefer an accurate list of things being worked on, rather than a failed prediction at what will land next milestone
13:54:25 <ttx> that doesn't mean you shouldn't have key goals and try to get those completed
13:54:40 <dhellmann> right, I expect we'll still set goals for ourselves
13:54:41 <ttx> but it wouldn't be release tracking job to push for those to get completed
13:54:49 * dhellmann nods
13:55:10 <ttx> me beating the drum to get the goals completed is no longer really efficient
13:55:54 <ttx> anyway, ttyl
13:56:08 <dhellmann> does that mean no more 1:1 meetings next cycle?
13:56:50 <ttx> the wiki page suggests to switch to on-demand, then syncs at each milestone/intermediary release
13:57:15 <dhellmann> that makes more sense -- I'll read the rest so you don't have to type it all out here ;-)
13:57:18 <dhellmann> thanks, ttyl
13:57:21 <ttx> we could still sync weekly, since we are the only ones having a productive discussion there
13:57:41 <ttx> (and that's because you actually do release management of Oslo* stuff
13:57:52 <ttx> so we need to share tools/processes
13:58:03 <ttx> dhellmann: ^
13:58:25 <ttx> but between milestones, I found the recent 1:1s to be pretty useless
13:58:37 <ttx> (for non-oslo)
13:58:57 <ttx> and I would be glad to have that time back
15:02:32 <mestery> ttx: Locked and loaded and ready when you are :)
15:03:22 <ttx> #topic Neutron
15:03:28 <ttx> mestery: o/
15:03:46 <ttx> #link https://launchpad.net/neutron/+milestone/kilo-3
15:04:18 <ttx> mestery: are all those unknowns real unknowns ?
15:04:27 <mestery> ttx: I've been updating some of them the last few minutes :)
15:04:38 <mestery> Some of them are unknowns, and I'm going to start removing them
15:04:38 <ttx> ah :)
15:05:12 <ttx> Other question that jumps to mind is how far are those essential things from being code-proposed ?
15:05:32 <ttx> FPF is Thursday next week (if you still plan to enforce it)
15:05:44 <mestery> ttx: I need to talk to kevinbenton on the first one, but he's out sick today, I'm hoping he will have something.
15:05:53 <mestery> The one assigned to salv-orlando will hve some code land but not complete.
15:06:00 <mestery> Some of the work armax is doign is in refernce to that BP
15:06:27 <ttx> ok, so you expect a late landing or a ffe on that one ?
15:06:48 <mestery> If anything, a ffe exception on kevinbenton's, salv-orlando's won't complete in Kilo.
15:07:02 <mestery> I'll know more once I sync with kevinbenton when's feeling better :)
15:07:18 <ttx> hmm, ok
15:08:07 <ttx> Other topic is the design summit space allocation. You actually asked for a total of 20 sessions where there is only time for 18 (assuming you have a slot on every time on Wed and Thu)
15:08:21 <ttx> so would be good to come up with a total of <=18
15:08:38 <mestery> OK, I'll do that! Assuming that is total of fish bowl + working sessions?
15:08:42 <ttx> yes
15:08:50 <mestery> OK, I'll update that once our meeting is done to be <= 18 :)
15:09:06 <mestery> Are we likely to get 18 if I move it to that? Or shoudl I go lower?
15:09:17 <mestery> Whatever works for the broader community I'm good with
15:09:45 <ttx> well, asking for slightly less would allow you to have sessions in common with Nova
15:10:17 <ttx> so maybe aiming for 16 will give you some flexibility
15:10:30 <mestery> ++, good idea! Thanks ttx!
15:10:40 <mestery> I'd really like some overlap with nova and possibly QA/infra as well
15:10:51 <ttx> also given that Neutron is generally a magnet for random people, not sure how well the working sessions will work for you
15:11:03 <mestery> Yeah, we always face that problem as well
15:11:11 <mestery> Fish bowels don't work well either to be honest
15:11:12 <ttx> the idea being to not advertise those and make them unattractive, but those peolpe are persistent
15:11:21 <mestery> having 200 people shouting about network protocols isn't anyone's idea of fun ;)
15:11:39 <ttx> having 200 people standing up around a 25-people boardroom is even less fun
15:11:40 <mestery> Stealth mode, I like it ;)
15:11:45 <mestery> lol
15:11:59 <mestery> The team is really focusing on making hte working sessions working sessions
15:12:08 <mestery> Hopefully they are boring enough to keep the marketing people away ;)
15:12:28 <ttx> 8+8 sounds like a good tradeoff
15:12:40 <ttx> + the full day friday
15:12:53 <mestery> Ideally we just want a morning session Friday.
15:12:56 <ttx> or 7+9 and the half day
15:12:59 <mestery> yes
15:13:36 <ttx> in other news... will discuss evolution in release tracking for Liberty at the cross-project meeting
15:13:44 <ttx> I think I already discussed that with you
15:13:54 <mestery> Yes! But I'm looking forward to that discussion in Vancouver
15:14:23 <ttx> we'll discuss it today
15:14:34 <ttx> so that things are ready when the cycle starts
15:14:44 <mestery> Ah, ok, good!
15:14:46 <mestery> Perfect
15:15:02 <mestery> As I've said before, OpenStack is not afraid of change ;)
15:15:04 <ttx> we migth end up discussing shorter cycles/releases in Vancouver instead :)
15:15:29 <ttx> ok, that's all I had
15:15:38 <mestery> That's a good discussion to have.
15:15:40 <mestery> OK. that's all from me too.
15:15:42 <mestery> Thanks ttx!
15:16:10 <ttx> nikhil_k: ready when you are
15:16:18 <nikhil_k> ttx: o/
15:16:24 <ttx> #topic Glance
15:16:38 <ttx> #link https://launchpad.net/glance/+milestone/kilo-3
15:16:59 <ttx> Looks good, you might want to set a prio for https://blueprints.launchpad.net/glance/+spec/metadefs-notifications
15:17:33 <ttx> Also Feature Proposal Freeze (the deadlien for getting code under review) is fast approaching (Thursday next week) in case you intend to enforce it
15:17:36 <nikhil_k> done
15:18:02 <nikhil_k> ttx: I was thinking March 12th for Glance
15:18:14 <ttx> ok, makes sense
15:18:27 <nikhil_k> thanks
15:18:29 <ttx> #info Glance may do FPF on Mar 12 instead of Mar 9
15:18:56 <ttx> That's all I had, anything on your side ?
15:19:10 <nikhil_k> ttx: I've replied to the google doc for the session schedule
15:19:24 <nikhil_k> I was curious when would that be published?
15:19:24 <ttx> nikhil_k: saw that, thx. That will help us work on room layout
15:19:44 <ttx> this was just a poll to see how we should lay out the rooms
15:19:47 <nikhil_k> People want me to send email saying that Friday would have a sprint session to help plan travel early
15:20:09 <nikhil_k> ttx: ah ok, so sending such email would be ok then?
15:20:12 <ttx> we are still expecting new project teams to appear and need space, so final allocation will happen much later
15:20:31 <ttx> I think you can bet on at least a half-day Friday
15:20:47 <nikhil_k> oh, we just have 1 halfday so that seems doeable
15:21:16 <ttx> yes
15:21:36 <ttx> anything else ?
15:21:48 <nikhil_k> that was it, thanks!
15:21:57 <ttx> nikhil_k: thx, talk to you later
15:22:11 <nikhil_k> cya, have a nice one
15:26:14 <ttx> thingee: o/
15:26:17 <ttx> ready when you are
15:26:47 <thingee> ttx: hi!
15:28:21 <ttx> #topic Cinder
15:28:27 <ttx> sorry, parallelizing :)
15:28:39 <ttx> #link https://launchpad.net/cinder/+milestone/kilo-3
15:28:47 <ttx> Looks pretty godo overall
15:28:50 <ttx> good*
15:29:14 <thingee> yes, a lot of these are very close. Some are not going to make the march 1st, code needs to be passing jenkins and ready.
15:29:38 <thingee> I've been reaching out to people to contributors about march 1st. oh well
15:29:51 <ttx> March 1st ?
15:30:09 <thingee> http://lists.openstack.org/pipermail/openstack-dev/2015-February/056964.html
15:30:37 <thingee> I will untarget bps not ready for review by march 1st.
15:30:44 <ttx> ok, so FPF 4 days in advance
15:30:59 <ttx> #info Cinder will do FPF on March 1st
15:31:30 <thingee> "to people to contributors"...heh sorry still waking up
15:31:57 <ttx> ok, and then.. review review review
15:32:11 <thingee> ttx: I'm on it! Hopefully I'll have time with my own bps :(
15:33:13 <ttx> ok, what else... we'll discuss evolution in release tracking at the cross-project meeting today
15:33:44 <ttx> the idea that central release management should stop caring about the milestone pages and their bad predictions
15:33:53 <ttx> feel free to join the fun
15:34:14 <thingee> heh
15:34:55 <ttx> that's about all I had in store for you
15:35:01 <ttx> Anything on your side ?
15:35:07 <thingee> nope
15:36:07 <ttx> thingee: ok then, ttyl
15:36:15 <ttx> david-lyle_afk: ping me when around
15:47:58 <david-lyle> ttx: ping
15:48:45 <ttx> david-lyle: o/
15:48:49 <ttx> #topic Horizon
15:49:30 <ttx> #link https://launchpad.net/horizon/+milestone/kilo-3
15:49:48 <ttx> Looks generally far from goal
15:49:57 <ttx> https://blueprints.launchpad.net/horizon/+spec/static-file-bower has no assignee
15:50:22 <ttx> How much of the feature proposal freeze on March 9 do you plan to enforce ?
15:50:24 <david-lyle> I just need to assign it
15:50:55 <david-lyle> FPF is code?
15:51:07 <david-lyle> trying to recall
15:51:40 <ttx> code for the blueprint must all be up for review
15:51:54 <ttx> so that you don't lose time reviewing stuff that won't make it to release anyway
15:52:25 <david-lyle> I suspect a couple of high priority items may come late, but I'll generally enforce it
15:52:55 <david-lyle> so likely a couple of exceptions, otherwise I will enforce
15:53:12 <ttx> right -- you might want to remind everyone of the deadline at your next meeting
15:53:28 <david-lyle> will do, thanks for the reminder
15:53:35 <ttx> what else... we'll discuss a lighter form of release tracking to implement in Liberty
15:53:39 <ttx> at the cross-project meeting today
15:53:52 <david-lyle> excellent
15:54:05 <david-lyle> I look forward to ito
15:54:07 <ttx> gist at https://wiki.openstack.org/wiki/Release_Cycle_Management/Liberty_Tracking
15:54:08 <david-lyle> *it
15:54:17 <ttx> anything on your side ?
15:54:44 <david-lyle> no I think we just need to get stuff landed
15:55:13 <david-lyle> been sprinting to try help big ticket items make progress toward that
15:55:27 <david-lyle> which has been fairly successful
15:55:32 <david-lyle> but a lot still at risk
15:56:40 <ttx> ack. I'll let you return to work then :)
15:56:44 <ttx> ttyl
15:57:40 <david-lyle> thanks, later
16:51:32 <morganfainberg> Ttx: we moved to 1650 right? /me might have put the wrong time on the calendar.
16:52:24 <ttx> yes!
16:52:27 <ttx> #topic Keystone
16:52:37 <ttx> morganfainberg: sorry, too many fires to address at the same time
16:52:55 <morganfainberg> No worries! I was worried I picked the wrong time for my calendar :)
16:52:58 <ttx> #link https://launchpad.net/keystone/+milestone/kilo-3
16:53:36 <ttx> so so so... a bit late to hit FPF on Mar 5 (10 days from now)
16:53:41 <morganfainberg> So today we are scrubbing that list for anything that doesn't have a chance of landing / significant code done
16:53:50 <ttx> ack
16:54:00 <ttx> also one of those has "unknown" status
16:54:17 <ttx> otherwise looks good
16:54:21 <morganfainberg> That one is a new Bp, but good work on it.
16:54:30 <morganfainberg> Iirc. Just was registered this morning.
16:54:46 <ttx> what else... we'll discuss simplifying release tracking at the cross-project meeting later
16:54:46 <morganfainberg> Spec was a spec proposal exception but had POC code ready to
16:54:50 <morganfainberg> Go.
16:55:02 <ttx> https://wiki.openstack.org/wiki/Release_Cycle_Management/Liberty_Tracking if you miss it
16:55:03 <morganfainberg> L1 specs will open after k3 is cut.
16:55:44 <morganfainberg> That looks good at a glance btw. The lighter version.
16:55:45 <ttx> that's all I had. Anything on your side before you jump in another funny meeting ?
16:56:03 <morganfainberg> Nope that's it.
16:56:17 <morganfainberg> I'm off to get coffee :) and review code.
16:56:33 <ttx> alright then, have a good day
16:57:44 <ttx> notmyname: ready when you are
17:00:37 <notmyname> ttx: here
17:00:44 <ttx> #topic Swift
17:01:15 <ttx> notmyname: so.. sprinting, feature branches...
17:01:29 <notmyname> oh yeah, we didn't meet last week, did we?
17:01:30 <ttx> notmyname: a vague idea of a window for the next kilo releases ?
17:01:37 <ttx> notmyname: yep, lnog time no see
17:01:40 <ttx> or long
17:01:49 <notmyname> next release for swift will be our rc for the integrated release
17:02:01 <ttx> ok, that works (and gives a bit of time)
17:02:11 <notmyname> right now I'm tracking weather EC will be included. that's the major focus
17:02:22 <notmyname> should be able to make a call in a couple of weeks
17:02:24 <ttx> right, would be awesome
17:02:34 <notmyname> hackathon (mid-cycle) was great
17:02:40 <ttx> #info next release for swift will be our rc for the integrated release
17:02:40 <notmyname> and we have a new feature branch now
17:02:55 <notmyname> #info swift has a feature/crypto feature branch now
17:03:11 <notmyname> we're doing a pluggable encryption thing there
17:03:20 <ttx> that's for at-rest encryption ?
17:03:23 <notmyname> yes
17:03:26 <ttx> ok
17:03:40 <notmyname> very very likely barbican integration
17:04:17 <ttx> makes sense
17:04:24 <notmyname> in more minor news, our OPW intern is finishing up her project (a tool to test proper configuration of clusters)
17:05:17 <notmyname> I've been talking to a company that has a tape library for swift. ie use upstream swift to store data on swift. they're planning on open-sourcing it soon. more info probably around the vancouver timeframe
17:05:43 <notmyname> also, similarly, IBM is open-sourcing their storelets thing (doing compute in the swift cluster). also should be more info in the vancouver timeframe
17:06:03 <notmyname> and we have a new core dev. mattoliverau
17:06:10 <ttx> sounds... interesting
17:06:15 <ttx> a bit like novm ?
17:06:30 <notmyname> like zeroVM (conceptually)
17:06:35 <notmyname> not quite like nova
17:06:44 <ttx> right zeoVM. not novm.
17:06:52 <ttx> although novm means zerovm.
17:06:56 <notmyname> he
17:06:58 <notmyname> heh
17:07:12 <ttx> ok, interesting days, I see
17:07:27 <notmyname> so, in summary, dev community is doing well and focusing on EC. the ecosystem is growing. things are going well. prepping for the summit, as always, will take up more and more time in the coming weeks
17:07:36 <notmyname> do you know any more about the summit scheduling?
17:07:49 <notmyname> we filled out the spreadsheet. when will we know what we get for timeslots?
17:08:00 <notmyname> and what will be use to submit/schedule the sessions?
17:08:00 <ttx> I'll use the prelimiary requests to build the room layout
17:08:13 * notmyname would prefer the old system instead of etherpads
17:08:15 <ttx> we'll refine the allocation when we know the exact list of projects we need to support
17:08:36 <notmyname> ok
17:09:03 <ttx> as far as the scheduling goes, working on a new system for the scheduling part, to take into account the added complexity
17:09:24 <ttx> but could also revive an instance of the old system for the CFP part
17:09:27 <notmyname> ok, great
17:09:30 <ttx> (or anyone could, actually)
17:09:53 <ttx> worst case scenario scheduling will be done separately
17:10:01 <notmyname> ok
17:10:03 <ttx> i.e. you select the talks then copy paste to schedule
17:10:43 <ttx> but to answer your question, final allocation should be closer to summit. I could probably try to give a range before
17:10:53 <notmyname> ok, great
17:11:09 <notmyname> I didn't sandbag, thinking I'd only get less than I asked for :-)
17:11:10 <ttx> but it depends a lot on how many projects will file to be "part of openstack" and therefore be present
17:11:36 <ttx> well, I took it as "as many as possible"
17:11:38 <notmyname> but I really like the idea on the general organization this time: formal talks, working sessions, and "free/open" time
17:11:59 <ttx> what you asked for though means no free time at all on wed/thu
17:12:14 <ttx> i.e. be in a work room all the time when you're not in a fishbowl
17:12:30 <notmyname> what is this "free time" you mention? does that exist at a summit? ;-)
17:12:55 <ttx> you mentioned "free/open" time
17:12:58 <notmyname> I was referring to the thus/fri open time. I don't remember what you called it
17:13:02 <ttx> or is that the Friday ?
17:13:05 <ttx> ok
17:13:07 <notmyname> ya, the friday
17:13:23 <ttx> contributors meetup / sprint / time together
17:13:31 <ttx> a.k.a. lets get some work started if we can
17:13:45 <ttx> ok, need to jump to next sync
17:13:45 <notmyname> ya. I'm also counting on the working sessions for that too, actually
17:13:54 <notmyname> ok. have a good day
17:14:05 <ttx> soudns like a perfectly legitimate use case for those
17:14:07 <ttx> have a good day!
17:14:12 <ttx> devananda: around?
17:14:18 <devananda> ttx: hi!
17:14:24 <ttx> #topic Ironic
17:14:45 <ttx> #link https://launchpad.net/ironic/+milestone/kilo-3
17:15:00 <devananda> ttx: we spent yesterday making sure that is up to date
17:15:13 <ttx> it's still missing quite a few assignees
17:15:22 <devananda> it's full of the crazy right now, as it represents the current state of accepted blueprints
17:15:31 <devananda> and some best guesses of priority from me
17:15:35 <ttx> ok :)
17:15:47 <ttx> well, keep it updated as you know more, I guess
17:16:05 <ttx> FPF is March 5th, as a reminder
17:16:17 <ttx> and I think you signed up to enforce it
17:16:20 <devananda> my goal for this week (amongst my goals...) is having that completely up to date, and then paring it down
17:16:26 <devananda> I did
17:16:46 <devananda> so that at our weekly meeting on monday, we can all go over it and, hopefully, agree without too much fuss
17:16:55 <ttx> In other news, that little discussion we had around that Ethiopian food in BRU turned into this: https://wiki.openstack.org/wiki/Release_Cycle_Management/Liberty_Tracking
17:17:11 * devananda looks
17:17:14 <ttx> If you're interested in discussing it, join us at the cross-project meeting later
17:17:20 <devananda> will do!
17:17:24 <ttx> awesome!
17:17:31 <ttx> That's all I had
17:17:35 <devananda> also, I saw your proposals for new tags about release cadence
17:17:46 <ttx> release models yes
17:17:53 <ttx> will be discussed at TC meeting today
17:18:19 <devananda> we'll be discussing the release model for ironic after this cycle
17:18:34 <devananda> I think some of the cores would like to go to the common model, fwiw
17:19:03 <ttx> common or compatible ?
17:19:06 <devananda> I'll pass that wiki page to them and hope they show up at the cross project meeting too
17:19:15 <devananda> erm. /me refreshes memory
17:19:17 <ttx> common is basically what you have right now (except you get free coordination)
17:19:32 <ttx> compatible is swift-style. Release at will, but try to match the end
17:19:41 <devananda> compatible
17:19:41 <devananda> yes
17:19:44 <ttx> right
17:20:14 <devananda> one other significant change to annouce
17:20:38 <devananda> as we move to standardizing our deploy tooling around IPA, we've just switched it in our main gating job
17:20:40 * ttx braces himself
17:21:03 <devananda> s/switched/prepared to switch/
17:21:04 <ttx> IPA?
17:21:11 <devananda> ironic-python-agent
17:21:15 <ttx> hah!
17:21:21 <ttx> ok
17:21:27 <ttx> maybe you should #info it
17:21:43 <ttx> in case anyone reads our logs, one never knows
17:22:03 <ttx> RL interrupt , brb
17:22:21 <devananda> #info ironic is switching our main gating job to use deploy ramdisk based on ironic-python-agent rather than diskimage-builder
17:23:56 <ttx> devananda: sounds good
17:24:01 <ttx> ttyl!
17:24:11 <ttx> SlickNik: around?
17:25:28 <SlickNik> ttx: here
17:26:05 <ttx> #topic Trove
17:26:17 <ttx> #link https://launchpad.net/trove/+milestone/kilo-3
17:26:23 <ttx> Looks up to date and good
17:26:33 <SlickNik> So that's accurate for the most part.
17:26:54 <ttx> We have FPF March 5 next week, so people should get their code up for review this week
17:27:10 <ttx> anything on your side ?
17:27:21 <SlickNik> I've been trying to find folks who are involved with BPs that are "slow progress" and check on whether those are indeed going to make it into kilo.
17:27:36 <SlickNik> Will keep that updated as I get more info.
17:27:53 <SlickNik> Yes — working towards that FPF date.
17:28:09 <SlickNik> One thing that we ran into, that's worth mentioning.
17:28:30 <SlickNik> We had a python-troveclient job that was gating against stable/juno and stable/icehouse.
17:29:07 <SlickNik> The stable branches have been updated recently to cap the version of the openstack/python-xclients that they support on them though.
17:29:33 <SlickNik> And this was breaking our client gate (since the requirements were "too recent")
17:30:09 <SlickNik> So we had to explicitly take a change to not gate our latest clients against the stable brances.
17:30:32 <SlickNik> Not sure if this affects any other projects — but worth mentioning.
17:30:32 <ttx> hmm
17:31:02 <ttx> you might want to reach out on #openstack-stable and give them a heads up. Or raise a [stable] thread
17:31:13 <SlickNik> ttx — will do.
17:31:18 <ttx> cool thx
17:31:22 <ttx> have a great day!
17:31:31 <SlickNik> That's all I had.
17:31:41 <ttx> cool, talk to you later
17:31:54 <SlickNik> Thanks! See you in a bit.
17:32:47 <ttx> #endmeeting