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