09:06:31 <ttx> #startmeeting ptl_sync
09:06:32 <openstack> Meeting started Tue Feb  3 09:06:31 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:06:33 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:06:34 <ttx> #topic Heat
09:06:35 <openstack> The meeting name has been set to 'ptl_sync'
09:06:41 <ttx> asalkeld: o/
09:06:45 <asalkeld> hi
09:07:02 <ttx> #link https://launchpad.net/heat/+milestone/kilo-2
09:07:05 <asalkeld> i think it's in ok shape
09:07:21 <asalkeld> there are 2 bugs and 2 bps soon to go in
09:07:24 <ttx> Still have 2 open BPs and 2 open bugs, are we trying to get those in before the tag ?
09:07:42 <asalkeld> ttx, just to be clear, the tag is in 2 days?
09:07:49 <asalkeld> on the 5th
09:08:05 <ttx> The tag window is Tuesday-Thursday
09:08:14 <ttx> so anytime during the window is fine
09:08:17 * ttx checks the Bp<->review mapping
09:08:29 <asalkeld> my wed-frid
09:08:42 <asalkeld> ttx, i'll keep that in mind
09:08:51 <ttx> decouple-nested is waiting on the 3 at https://review.openstack.org/#/q/topic:bp/decouple-nested,n,z ?
09:08:52 <asalkeld> all those *should* be ok
09:09:06 <asalkeld> ttx, yeah i have taken that one over
09:09:18 <ttx> stack-breakpoint waiting on https://review.openstack.org/#/c/146123/
09:09:19 <asalkeld> if it can't make it, i'll move to k3
09:09:27 <asalkeld> breakpoint should be fine
09:09:31 <asalkeld> just one patch
09:09:47 <ttx> bug 1411103 on https://review.openstack.org/#/c/147463/
09:09:58 <ttx> 1406692
09:10:12 <ttx> doesn't seem to have areview up yet
09:10:19 <ttx> is that correct ?
09:10:50 <asalkeld> but you just point out the review?
09:11:06 <asalkeld> ooo, different numbre
09:11:08 <ttx> bug 1406692
09:11:33 <asalkeld> we can move that one
09:11:41 <ttx> ok, moving
09:11:43 <asalkeld> pushed to k3
09:12:07 <ttx> OK, that sounds like a reasonable number of things to wait on
09:12:20 <asalkeld> cool, i'll try my best to get all that in
09:12:21 <ttx> I'll track progress against those reviews
09:12:30 <ttx> and will confirm itr's good to go once they are in
09:12:37 <asalkeld> thx!
09:12:46 <ttx> (and ping you if they obviously won't make it during the tag window)
09:13:10 <ttx> asalkeld: looks good to me... questions on your side ?
09:13:14 <asalkeld> ttx, when you ideally like to tag
09:13:35 <asalkeld> so i can gauge when this should be in
09:13:40 <ttx> I like to tag on my Wednesday morning, your Wednesday evening
09:13:43 <asalkeld> utc
09:13:49 <asalkeld> ok
09:13:55 <ttx> but it's fine to do Thursday morning too
09:13:55 <asalkeld> that's all godd
09:14:01 <ttx> I don't like Thursday evening that much
09:14:09 <ttx> but you should be sleeping then :)
09:14:09 <asalkeld> lol
09:14:30 <asalkeld> ok, all good from my end
09:14:33 <ttx> ok, if you don't have other questions, have a good week!
09:14:41 <asalkeld> you too
09:15:11 * ttx waits for johnthetubaguy
09:27:55 <johnthetubaguy> ttx: hey, sorry for the wait
09:28:25 <ttx> johnthetubaguy: o/
09:28:28 <ttx> #topic Nova
09:28:42 <ttx> #link https://launchpad.net/nova/+milestone/kilo-2
09:28:44 <johnthetubaguy> cool
09:28:57 <ttx> pretty impressive list of stuff under review here
09:29:37 <johnthetubaguy> yeah, its gone a bit mad
09:29:48 <johnthetubaguy> people actually got their code up for review, which is nice
09:29:50 <ttx> johnthetubaguy: what do you expect will happen ? a few of them merge and we defer the others ?
09:30:14 <johnthetubaguy> I actually expect to defer all the low ones, that have no patches merged yet
09:30:14 <ttx> Or do you plan to start pushing back to L ?
09:30:22 <johnthetubaguy> yeah
09:30:28 <johnthetubaguy> defer to L for those
09:30:34 <ttx> Would deferring now help in prioritizing reviews, or not so much ?
09:31:13 <johnthetubaguy> so, possibly, I was going to check through the list, and see if there are BPs with old −1s on the reviews, etc
09:31:28 <ttx> I'm a bit concerned with this multi-month feature freeze for non-priority stuff
09:31:53 <ttx> Historically, feature freeze was relatively well accepted because it's onlt a couple weeks before we open the next dev branch
09:32:10 <ttx> Will be a harder sell if it's a couple months away
09:32:24 <johnthetubaguy> yes, its basically us trying to do the slots things, just only for one sprint
09:32:29 <ttx> people with those patches will have to rebase against master and keep them in the fridge
09:32:49 <johnthetubaguy> just we don't see how we can get the priority stuff merged otherwise
09:33:00 <ttx> right, not saying you shouldn't do it
09:33:17 <ttx> just wondering how well that would be accepted, given how many patches fall into that group
09:33:26 <johnthetubaguy> yeah, I mean, lets be honest, its a massive experiment
09:33:37 <johnthetubaguy> people seemed to agree on the priorities as being important, and bug fixes
09:33:57 <ttx> A number of them have been asking for exceptions right
09:34:17 <johnthetubaguy> yes, but those where mostly the specs we didn't get merged
09:34:25 <johnthetubaguy> at least up until this point
09:34:32 <ttx> hmm, ok
09:35:02 <johnthetubaguy> yeah, its madness, we have way more code than we can review at this point, this is our attempt at being honest and telling people its no going to happen
09:35:02 <ttx> johnthetubaguy: so I guess we should wait as much as we can before we tag
09:35:16 <ttx> whatever gets in is in
09:35:23 <johnthetubaguy> yes, thats fair
09:35:49 <ttx> how about we have this same discussion on Thursday and see if there is value in waiting a feqw more hours ?
09:35:52 <johnthetubaguy> I think, the stuff thats almost, but not quite in, I might let slide into the first week of kilo-3, without too much process, but lets see how it looks I guess
09:36:25 <johnthetubaguy> I am good with that, I mean, maybe we catch up tomorrow morning, so see how the burn down is looking?
09:36:44 <ttx> johnthetubaguy: sounds good
09:37:02 <ttx> johnthetubaguy: I have been discussing recently the value of milestone targeting... It's a lot of effort to maintain and we consistently miss our predictions
09:37:14 <johnthetubaguy> I mean, we spoke about actually aiming for zero exceptions this time, possibly over-roating though
09:37:33 <johnthetubaguy> yes, that came up at the midcycle actually
09:37:46 <ttx> johnthetubaguy: we could technically take the linux approach and not even try to predict. Just collect whatever is landed
09:37:55 <johnthetubaguy> can't say we had any great ideas, yeah, thats the only one that came up
09:38:26 <ttx> The milestone is still useful as a reference date, the tag is still useful as a way to exercise the machinery
09:38:37 <ttx> but as a promise, it's not that great
09:39:04 <ttx> johnthetubaguy: and not having to maintain it would free us to do more useful things
09:39:12 <ttx> like focus on priority tasks
09:39:14 <johnthetubaguy> very true, I am keen on the idea
09:39:30 <johnthetubaguy> I guess we have to try it to know how it looks
09:39:55 <ttx> I will think about it a bit more... and probably start a thread on the ML
09:39:57 <johnthetubaguy> we should be able to have tooling to automatically fill in the milestone after we tag, I guess
09:40:07 <ttx> I know some projects are attached to producing meaningful milestones
09:40:23 <ttx> the milestone in LP always had two meanings
09:40:23 <johnthetubaguy> ttx: appreciated, it should make things more scalable
09:40:32 <ttx> the promise and the actual delivery
09:40:38 <ttx> using the same damn field
09:40:40 <johnthetubaguy> ah, thats true
09:40:46 <ttx> which causes all sort of pain
09:40:56 <ttx> The delivery is still very useful
09:41:04 <johnthetubaguy> yeah, we sorta stopped bothering with the promise, mostly, without telling people
09:41:11 <johnthetubaguy> yeah, if we can automate that, then awesome :)
09:41:19 <ttx> collecting what was merged when we tag and add it as a delivery milestone to the bug, very good
09:41:49 <ttx> using a single list of things to track, not so good
09:42:01 <ttx> that tension shows in how we use those milestone pages
09:42:03 <johnthetubaguy> yeah
09:42:15 <ttx> sometimes those are targets of opprtunity, sometimes those are milestone tag blockers
09:42:33 <ttx> and then suddenly we purge it and it becomes the list of stuff actually landed
09:42:47 <johnthetubaguy> priority is better for, this should go in first, then defer it if its too late for this release
09:43:01 <ttx> (fwiw in storyboard we don't really replicate the concept of "promised milestone")
09:43:18 <johnthetubaguy> yeah, thats a good way of talking about the problem, not thought about it as clearly as that before
09:43:21 <ttx> (and you should be able to use multiple "priority lists" to track random stuff)
09:43:37 <ttx> one could be milestone blockers, another could be targets of opportunity etc)
09:43:58 <ttx> Targeting tasks against a future milestone is still useful for RC tracking
09:44:14 <johnthetubaguy> thats true
09:44:16 <ttx> but that's actaully the exception rather than the rule
09:44:20 <johnthetubaguy> yeah
09:44:29 <ttx> anyway, random thoughts
09:44:33 <johnthetubaguy> I mean the discussion we had before was interesting
09:44:36 <ttx> just wanted to check where you stood on that
09:44:44 <johnthetubaguy> feature freeze time, we are really good at merging things
09:44:50 <johnthetubaguy> because we have a smaller list to focus on
09:45:15 <johnthetubaguy> so keeping that, maybe using priorities, sounds good
09:45:37 <johnthetubaguy> ignoring milestones, for want of a better word, should free up more time to set priorities better, etc
09:45:50 <ttx> johnthetubaguy: identifying those BPs which are 99% there could be a useful way to prioritize reviews
09:46:05 <ttx> (for k2)
09:46:08 <johnthetubaguy> yeah, I think I am going to go do that
09:46:25 <ttx> because those 99% there won't take a two-months wait that gracefully
09:46:26 <johnthetubaguy> this stuff has some +2s, lets finish it off, etc
09:46:31 <johnthetubaguy> agreed
09:46:39 <ttx> even if it's Low.
09:47:05 <johnthetubaguy> yeah, that makes them more angry, honestly
09:47:30 <ttx> so yes, identifying a few things that could easily make it with some focus could help
09:47:55 <ttx> alright, I'll talk to you later this week as we approach the fatidic tag
09:49:06 <ttx> johnthetubaguy: did you have any question ?
09:49:20 <johnthetubaguy> ttx: I am good, thanks for your help
09:49:29 <johnthetubaguy> looking forward to the thoughts on milestones
09:49:50 <ttx> johnthetubaguy: ack, have a good day!
09:50:24 <johnthetubaguy> any you!
09:50:26 <johnthetubaguy> ops
09:50:28 <johnthetubaguy> and you!
13:00:05 <ttx> eglynn: around?
13:00:50 <eglynn> ttx: hey
13:00:52 <ttx> #topic Ceilometer
13:00:55 <ttx> eglynn: hi!
13:01:03 <ttx> #link https://launchpad.net/ceilometer/+milestone/kilo-2
13:01:12 <eglynn> #link https://launchpad.net/ceilometer/+milestone/kilo-2
13:01:21 <ttx> I see 4 BPs and one bug.
13:01:29 <eglynn> I've already bumped the BP that won't make it
13:01:30 <ttx> All things you'd like to wait on before we tag ?
13:01:45 <eglynn> the others are likely to hand later today or early tmrw
13:01:51 <eglynn> *land
13:01:59 <ttx> checking blocking reviews
13:02:01 <eglynn> just minor nits in tests etc.
13:02:18 <ttx> disk-info-meters pending on https://review.openstack.org/#/c/145819/
13:02:42 <eglynn> yeap, that's the only one I'm slightly concerned about
13:02:43 <ttx> hyper-v-disk-latency-metrics pending on .. ? all merged?
13:03:14 <eglynn> a-ha yes, updating status
13:03:17 <ttx> declarative-http-tests pending on https://review.openstack.org/#/c/146187/
13:03:44 <eglynn> yep, cdent is working on the last test nit as we speak
13:04:01 <ttx> elasticsearch-driver pending on ... https://review.openstack.org/#/c/137131/ ?
13:04:16 <eglynn> yep gordc will be online soon to get that over the line today
13:04:39 <ttx> can't find the change in Gerrit for https://bugs.launchpad.net/ceilometer/+bug/1403787
13:05:15 <eglynn> darn, I mean to bump that
13:05:16 <ttx> Also ceilometermiddleware is marked completed but https://review.openstack.org/#/c/151744/ is still in flight
13:05:18 <eglynn> done now
13:06:05 <ttx> should it be reverted to NeedsCodeReview?
13:07:01 <eglynn> yeap, we were looking that just now ... I've +A'd the patch
13:07:34 <ttx> ok, let's mark it NeedsCodeReview until patch makes it ?
13:08:21 <eglynn> ok, done
13:08:25 <ttx> OK, so I'll keep track of those last things and ping you when I think we can tag. If they don't burn down in time, I'll ping you to remove blockers
13:08:42 <eglynn> sounds like a plan
13:08:47 <ttx> or just contact me when the page is all set :)
13:08:54 <eglynn> cool, will do
13:09:08 <ttx> alright. Questions on your side ?
13:09:17 <eglynn> nope
13:09:21 <ttx> alrighy then
13:09:24 <ttx> +t
13:09:29 <ttx> SergeyLukjanov: you around?
13:09:32 <eglynn> thank you for your time!
13:09:38 <ttx> eglynn: have a good week
13:09:45 <SergeyLukjanov> ttx, hello!
13:09:51 <ttx> #topic Sahara
13:09:57 <SergeyLukjanov> #link https://launchpad.net/sahara/+milestone/kilo-2
13:10:07 <ttx> 2 BPs left
13:10:10 <SergeyLukjanov> we have two blueprints on the go
13:10:19 <SergeyLukjanov> edp-spark-swift-integration waits for https://review.openstack.org/#/c/146659/ (-1’d for nit thing, will be updated and re-approved today)
13:10:26 <SergeyLukjanov> and indirect-vm-access with https://review.openstack.org/#/c/133590/ in the gate
13:10:36 <ttx> sounds good
13:11:00 <SergeyLukjanov> so, should be delivered before tomorrow
13:11:12 <ttx> heh, you pmake my job easy I see
13:11:26 <SergeyLukjanov> hope so :)
13:11:33 <ttx> note that we'll discuss reviews of Horizon panels at the cross-project meeting later
13:11:39 <ttx> you might want to stay around
13:11:54 <ttx> otherwise I'll bring the topic up anyway
13:12:10 <SergeyLukjanov> yup, I remember
13:12:27 <ttx> No other questions
13:12:32 <SergeyLukjanov> I don't have a story for it, just want to discuss what's the best approach for doing it
13:12:46 <ttx> it's a good discussion to have
13:12:51 <ttx> it won't get any better i the future
13:12:59 <SergeyLukjanov> I'm always on cross-project meetings, not aleays active due to the very late time :(
13:13:09 <ttx> yep
13:13:10 <SergeyLukjanov> nothing more from my side too
13:13:14 <ttx> SergeyLukjanov: have a good day then!
13:13:21 <SergeyLukjanov> ttx, thanks
13:13:25 <SergeyLukjanov> ttx, you too
13:13:34 <ttx> dhellmann: ready when you are
13:13:50 <dhellmann> ttx: hi!
13:13:59 <ttx> #topic Oslo
13:14:14 <ttx> #link https://launchpad.net/oslo/+milestone/kilo-2
13:14:26 <ttx> Looks all set for oslo-incubator tagging
13:14:38 <dhellmann> yep, I think we're clear
13:14:42 <ttx> dhellmann: anything we should wait on before we tag the incubator with the kilo-2 tag ?
13:14:54 <ttx> usually we do it late, we can as well do it early
13:14:59 <ttx> I think
13:14:59 * dhellmann checks the queue quickly
13:15:48 <dhellmann> nothing in the queue looks like it's critical, so we could go ahead
13:16:00 <ttx> ok, will do just after our discussion
13:16:02 <ttx> Quick glance at https://launchpad.net/oslo/+milestone/next-kilo
13:16:18 <ttx> any other library release this week?
13:16:33 <dhellmann> no, we decided to hold off until next week because of the deadline
13:16:44 <dhellmann> we'll have several on monday morning
13:16:48 <ttx> yes, it's not a week where breakage is appreciated
13:16:59 <dhellmann> utils, test, and db at least next week
13:17:20 <dhellmann> yeah, I thought josh was going to wait to do the taskflow release, too -- bad communication there on my part
13:17:28 <ttx> "I don't always break OpenSTack by releasing an Oslo library, but when I do, I do it after the milestone week"
13:17:37 <dhellmann> no that's a t-shirt slogan
13:17:40 <dhellmann> *now
13:18:18 <ttx> OK, anything more before I start running script
13:18:20 <ttx> ?
13:18:40 <dhellmann> nothing to report, and nothing for the meeting agenda
13:18:58 <ttx> alright then, tag on its way.
13:19:17 * dhellmann ducks
13:20:03 <ttx> heh, you aren't the one running the experimental neutron-aaS-friends-supporting branch of release-tools now
13:21:04 <ttx> ok done
13:21:29 <ttx> dhellmann: It's so awesome to see so little work being done in the incubator those days :)
13:35:56 <dhellmann> ttx: yeah, that'll change again next cycle when we shift back into "acquisition" mode, but I want us to set a goal of 1-2 cycles for incubation before graduation
14:54:44 <mestery> ttx: I'm ready whenever you're ready.
14:57:44 <ttx> mestery: ok, let's do this
14:57:48 <ttx> #topic Neutron
14:58:05 <ttx> #link https://launchpad.net/neutron/+milestone/kilo-2
14:58:18 <ttx> 7 Bps still up
14:58:27 <ttx> and 18 bugs
14:58:34 <mestery> ttx: Ack, all those BPs have a shot still.
14:58:37 <mestery> They have patches in flight.
14:58:40 <ttx> Should I treat any of those bugs as a milestone blocker ?
14:58:48 <mestery> But I've told people that if they aren't in the merge queue by Wednesday morning they're out.
14:58:50 <ttx> or just defer whatever doesn't make it ?
14:59:05 <mestery> I don't think any are blockers at this point.
14:59:20 <ttx> ok, so let's see if I can map those BPs to reviews
14:59:58 <ttx> refactor-iptables-firewall-driver > https://review.openstack.org/#/c/152512/ says it partially implements -- so are more patches coming ?
15:00:15 * mestery looks
15:00:35 <mestery> That's the last patch for that BP.
15:01:04 <mestery> I'm confirming with ajo now, but that's what he told me Friday.
15:01:12 <ttx> lbaas-api-and-objmodel-improvement > https://review.openstack.org/#/c/152171/ https://review.openstack.org/#/c/144834/ https://review.openstack.org/#/c/144832/
15:01:29 <mestery> Just got confirmation on https://review.openstack.org/#/c/152512/, it closed out refactor-iptables-firewall-driver
15:01:32 <mestery> *closes
15:01:45 <mestery> ttx: The LBaaS folks are having a sprint this week, I expect a lot of merges from them today/tomorrow.
15:01:59 <mestery> dougwig has indicated that LBaaS V2 BP will be done before Kilo-2, barring merge issues
15:02:38 <ttx> rootwrap-daemon-mode > https://review.openstack.org/#/c/84667/ https://review.openstack.org/#/c/82787/ https://review.openstack.org/#/c/145829/
15:02:47 <ttx> looks a bit far away
15:02:57 <mestery> ttx: If otherwiseguy doesn't propose a new patch by this morning, I'll move it out.
15:03:25 <ttx> extra-dhcp-opts-ipv4-ipv6 > https://review.openstack.org/#/c/136713/
15:03:54 <ttx> allow-mac-to-be-updated > https://review.openstack.org/#/c/112129/
15:03:57 <mestery> This one should merge today
15:04:10 <ttx> yes those two are looking good
15:04:13 <mestery> ++
15:04:40 <ttx> ofagent-flow-based-tunneling > https://review.openstack.org/#/c/130677/ https://review.openstack.org/#/c/130676/
15:04:57 <mestery> That one is a little further away than the prior too, but still close
15:05:03 <ttx> rpc-docs-and-namespaces > https://review.openstack.org/#/c/149735/
15:05:25 <ttx> OK, if that is correct I can track completion and help updating BP status
15:05:30 <mestery> I have an ask out to russellb on the status there, I suspect it may not be complete, but there's a lot of patches so it's hard to know :)
15:05:35 <mestery> Thanks ttx!
15:06:05 <ttx> sanity-checking the repos to see if tarballs are complete
15:06:16 <mestery> cool
15:06:30 <ttx> takes a bit of time
15:07:17 <ttx> while I wait, other questions ?
15:07:27 <mestery> I'm going to spend some time post our 1:1 going through the remaining bugs that are open yet
15:07:33 <mestery> I'll have those cleaned up this morning with only ones realistically having a chance at Kilo-2 targeted
15:07:35 <ttx> I'll ping you if it seems headed to the wall or if it looks ready
15:07:39 <mestery> One more thing
15:07:45 <mestery> #link https://docs.google.com/spreadsheets/d/1OQN0VlKzKC1gYlxgalQXKDTGGWogWFRtD3S5OpepsX4/edit?pli=1#gid=0
15:07:57 <mestery> That's the tracking page for our plugin decomposition status
15:07:57 <mestery> It's looking quite good actually!
15:08:01 <ttx> You can ping me if it looks ready from where you're standing
15:08:03 <mestery> We'll keep that updated as we go.
15:08:09 <mestery> ttx: Ack
15:08:55 <ttx> mestery: so those repos contains each vendor plugin
15:08:57 <ttx> ?
15:09:04 <mestery> Correct
15:09:13 <mestery> The backend logic for the plugin, a thin shim is still in the neutron tree.
15:09:22 <ttx> ok
15:09:50 <mestery> The process has gone quite smooth actually, kudos to armax for leading this
15:09:59 <ttx> ok, so we'll be in touch for the tag(s)
15:10:12 <mestery> Thanks ttx!
15:10:19 <ttx> I evolved the release scripts, they should support uploading neutron-*aas to same LP page now
15:10:26 <ttx> fingers crossed
15:10:27 <mestery> ++, awesome!
15:10:32 <mestery> ;)
15:10:45 <ttx> mestery: alright, have a nice day!
15:10:56 <mestery> ttx: Thank you! You have a great evening!
15:11:37 <ttx> nikhil_k: ready when you are
15:20:58 <nikhil_k> ttx: o/
15:21:07 <ttx> #topic Glance
15:21:14 <ttx> #link https://launchpad.net/glance/+milestone/kilo-2
15:21:18 <ttx> nikhil_k: o/
15:21:30 <ttx> I see 4 Bps still in progress
15:21:38 <ttx> All likely to make it in the coming days ?
15:21:47 <nikhil_k> ttx: so, there was some confusion on some of them
15:21:55 <nikhil_k> a couple of them are ready
15:22:05 <nikhil_k> https://blueprints.launchpad.net/glance/+spec/replace-snet-config-with-endpoint-config and
15:22:08 <nikhil_k> https://blueprints.launchpad.net/glance/+spec/software-metadefs
15:22:18 * ttx looks at those
15:22:21 <nikhil_k> this is being tested and needs a small change
15:22:21 <nikhil_k> https://blueprints.launchpad.net/glance/+spec/taskflow-integration
15:22:33 <nikhil_k> this looks unlikely https://blueprints.launchpad.net/glance/+spec/swift-retry-wait
15:22:49 <ttx> replace-snet-config-with-endpoint-config pending on https://review.openstack.org/#/c/150144/ IIUC
15:23:17 <ttx> software-metadefs pending on https://review.openstack.org/#/c/148007/
15:23:40 <ttx> taskflow-integration...
15:23:40 <nikhil_k> ttx: yeah, I heard back just gunna review it
15:23:51 <nikhil_k> about replace-snet-config
15:23:52 <ttx> is it just https://review.openstack.org/#/c/85211/ ?
15:23:57 <nikhil_k> yes
15:24:00 <ttx> ok
15:24:06 <ttx> swift-retry-wait...
15:24:19 <nikhil_k> ttx: the main blocker is https://bugs.launchpad.net/bugs/1412802
15:24:27 * nikhil_k waits
15:24:35 <ttx> yeah, it looks way farther away, better concentrate on the other 3
15:24:55 <ttx> how about we move this one to k3 already, to signal reviewers should focus on the other 3 ?
15:25:25 <nikhil_k> ttx: that sounds fine
15:25:31 <ttx> ok, doing it now
15:25:50 <ttx> About the bugs, anything we should block the milestone on ?
15:26:03 <ttx> Or I should just defer whichever are not merged when the BPs are done ?
15:26:19 <nikhil_k> the main blocker is https://bugs.launchpad.net/bugs/1412802
15:26:33 <ttx> right
15:26:42 <ttx> we should keep this one as blocker
15:26:48 <nikhil_k> and may be we should let this one slide https://bugs.launchpad.net/glance/+bug/1221274
15:27:25 <ttx> feels featury rather than buggy too
15:27:39 <ttx> How about I mogve out of the milestone all but the critical one ?
15:27:50 <ttx> If those get merged they will be reincluded anyway
15:27:50 <nikhil_k> yeah, feature related is https://review.openstack.org/#/c/145544/6
15:28:26 <nikhil_k> ttx: sure, if you have to. I was going to suggest to wait until tomorrow however, either way is fine
15:28:43 <nikhil_k> I think focusing on k3 and wrapping stuff up should like a better scenario
15:28:53 <nikhil_k> s/should/sounds/
15:29:01 <ttx> I prefer to use the k2 list as the blocker list at this point
15:29:16 <nikhil_k> ok, sure
15:29:45 <ttx> OK, it's clean now
15:29:48 <nikhil_k> :)
15:30:02 <nikhil_k> Appreciate it.
15:30:03 <ttx> I'll track those in the coming days and ping when if we won't hit the window or if all seem ready
15:30:13 <ttx> ping me the other way around if you feel it's good to go too
15:30:20 <nikhil_k> Sure thing
15:30:20 <ttx> Questions ?
15:30:27 <nikhil_k> Nothing for now :)
15:30:34 <ttx> alright, you know where to find me
15:30:39 <ttx> Have a good day
15:30:47 <nikhil_k> Have a good one, yourself!
15:31:30 <ttx> thingee: ready when you are
15:31:38 <thingee> ttx: hi!
15:31:45 <ttx> #topic Cinder
15:31:50 <ttx> #link https://launchpad.net/cinder/+milestone/kilo-2
15:31:59 <ttx> I see 5 open BPs in my crystal ball
15:32:09 <ttx> All still likely to make it ?
15:32:41 <thingee> I moved out a lot of stuff that have little to no consensus. If anything is going to make it, it's these.
15:32:46 <ttx> OK, let's map them to the corresponding reviews then
15:33:10 <ttx> over-subscription-in-thin-provisioning seems to be waiting on https://review.openstack.org/#/c/142171/
15:33:42 <ttx> remotefs-share-cfg-improvements on https://review.openstack.org/#/c/149765/
15:34:01 <ttx> database-purge on https://review.openstack.org/#/c/146766/
15:34:02 <thingee> https://etherpad.openstack.org/p/cinder-k2-priorities
15:34:41 <ttx> chiscsi-iscsi-helper > https://review.openstack.org/#/c/147758/
15:34:50 <ttx> adding them for the log
15:35:22 <ttx> nfs-manage-unmanage > https://review.openstack.org/#/c/138125/
15:35:36 <ttx> All sounds doable
15:35:57 <ttx> Theer are also 3 bugs. Are those blockers of just targets of opprtunity that I can defer to k3 if they miss ?
15:36:19 <thingee> yes
15:36:28 <ttx> (the latter)
15:36:41 <thingee> yea latter
15:36:43 <thingee> sorry
15:37:03 <ttx> Alright, I'm all clear
15:37:07 <thingee> last thing
15:37:09 <thingee> http://lists.openstack.org/pipermail/openstack-dev/2015-January/055719.html
15:37:15 <ttx> I'll track those
15:37:16 <thingee> sorry for switching this on you
15:37:53 <ttx> #info Cidner Blueprint/Spec approval deadline - February 15th
15:37:57 <thingee> not sure if it's doable for something cross project next time on deadlines? Or a table somewhere? I can't imagine this is easy for contributors to keep track of
15:38:02 <ttx> #info Cinder Code freeze for all features - March 10th
15:38:22 <ttx> I posted most of them on https://wiki.openstack.org/wiki/Kilo_Release_Schedule
15:38:34 <thingee> you're way ahead of me, thanks :)
15:38:48 <ttx> but I need to adjust dates it seems
15:39:42 <thingee> that's all for me
15:39:46 <ttx> thingee: code freeze for all features -- what does that mean
15:39:54 <ttx> features must be proposed ?
15:40:01 <ttx> (as in, in code review ?
15:40:05 <ttx> or merged ?)
15:40:08 <thingee> no accepting anymore code unless they're bug fixes
15:40:18 <thingee> not*
15:40:33 <ttx> so you're basically moving Feature Freeze up 9 days
15:40:49 <ttx> (normally on March 19th)
15:41:04 <thingee> correct
15:41:18 <ttx> OK, I'll add that to page
15:41:22 <ttx> now
15:43:18 <ttx> thingee: done
15:43:23 <thingee> ttx: thank you
15:43:28 <ttx> #link https://wiki.openstack.org/wiki/Kilo_Release_Schedule
15:43:40 <ttx> We'll probably evolve the format of that
15:43:53 <ttx> doesn't scale that beautifully
15:44:04 <ttx> david-lyle: you around ?
15:44:08 <david-lyle> ttx: here
15:44:09 <ttx> thingee: thx!
15:44:14 <ttx> #topic Horizon
15:44:19 <ttx> Sorry for the lateness
15:44:26 <david-lyle> no worries
15:44:30 <ttx> #link https://launchpad.net/horizon/+milestone/kilo-2
15:44:49 <ttx> 5 Bps up
15:44:59 <ttx> All still in the race to make the window ?
15:45:30 <david-lyle> top one will miss, just about to move
15:45:48 <ttx> was wondering if https://review.openstack.org/#/c/148031/ didn't complete it
15:45:58 <ttx> I guess not :)
15:46:15 <david-lyle> no, that's just a part of it
15:46:24 <ttx> heat-topology-display-improvement pending on https://review.openstack.org/#/c/110888/
15:46:41 <david-lyle> going to ping reviewers on that one
15:46:51 <ttx> migrate-all-instances-from-hosts-in-maintenance-mode on https://review.openstack.org/#/c/109586/
15:46:53 <david-lyle> smaller change, been sitting a while
15:47:09 <ttx> add-manage-unmanage-volume > https://review.openstack.org/#/c/129652/
15:47:26 <ttx> settings-migration-script > https://review.openstack.org/#/c/81255/
15:47:46 <ttx> view-volume-encryption-metadata > https://review.openstack.org/#/c/134341/
15:47:50 <ttx> All seem in good shape
15:47:52 <david-lyle> most of those look in really good shape, just need to get cores looking at them
15:48:01 <ttx> yes
15:48:09 <david-lyle> 2 of those I have on my list for after this
15:48:27 <ttx> Lots of bugs in the buglist, anything critical or can I just move the ones which don't make it to k3 ?
15:48:39 <david-lyle> all that don't land can move
15:48:47 <david-lyle> I already moved anything that wasn't in progress
15:48:59 <ttx> OK, sound all good
15:49:25 <ttx> Note that we'll discuss project-specific panels reviews at the cross-project meeting today
15:49:34 <ttx> if you can attend
15:49:38 <david-lyle> sure
15:49:49 <ttx> in particular it's interesting to see how that would scale in a bigger tent
15:50:10 <david-lyle> short answer, I don't think it does
15:50:21 <david-lyle> not with the current model at least
15:50:29 <ttx> agree, which is why we need to discuss/brainstorm how to solve that
15:50:39 <ttx> anyway, talk about that later
15:50:43 <david-lyle> sure
15:50:45 <ttx> questions on your side ?
15:51:13 <david-lyle> my only concern is I haven't seen anything new for ironic
15:51:16 <david-lyle> for horizon
15:51:36 <ttx> hmm, we could talk about it as part of that meeting topic
15:51:39 <david-lyle> tuskar-ui has some ironic support that we can pull in, but that's not the full story
15:51:49 <david-lyle> I can ping devananda directly as well
15:52:05 <david-lyle> was just looking through the bps today and didn't see anything
15:52:10 <devananda> o/
15:52:25 <ttx> devananda: oh right, you're in my timezone
15:52:37 <devananda> ttx: yah
15:52:38 <david-lyle> devananda: know of any efforts for ironic support in horizon for kilo?
15:52:43 <ttx> devananda: can you still make the regular 1:1 time ?
15:52:44 <devananda> nope
15:53:11 <david-lyle> we have tuskar-ui support, but that's only a fraction of the real use cases I believe
15:53:26 <david-lyle> if you don't know of any efforts, I'll try to motivate someone
15:53:56 <ttx> david-lyle: ok, if no other issues to report, ttyl
15:53:59 <devananda> I've had a few conversations with folks about doing it, but have not seen anything tangible yet
15:54:20 <david-lyle> thanks ttx
15:54:52 <david-lyle> devananda: let me know if any materialize, otherwise, I'll try to take a look
15:55:02 <david-lyle> would like to have support in kilo
16:12:39 <SlickNik> ttx: hi — got a minute?
16:12:50 <ttx> on a call
16:14:04 <SlickNik> okay, can wait.
16:17:58 <ttx> SlickNik: done
16:18:06 <ttx> want to sync now ?
16:19:02 <SlickNik> ttx: yes, please — since we will be busy with the mid cycle in a few.
16:19:08 <ttx> alright
16:19:11 <ttx> #topic Trove
16:19:22 <ttx> #link https://launchpad.net/trove/+milestone/kilo-2
16:19:33 <ttx> That looks pretty complete from where I stand
16:19:44 <SlickNik> Yes, have it pretty complete for kilo-2.
16:19:46 <ttx> Want to wait a bit more to see if anything else makes it ?
16:19:52 <ttx> Or shall I tag now ?
16:20:19 <SlickNik> Feel free to tag now — most folks are at the mid-cycle and there's no outstanding blockers.
16:20:24 <SlickNik> Hash: 4d31433b1e67acbba1932ba1b032fe55f2dfd00d
16:20:41 <ttx> OK, will do in a few
16:20:49 <ttx> and ping you when done
16:21:07 <ttx> I don't have more questions then ;)
16:21:25 <SlickNik> Thanks, tag at your convenience!
16:21:44 <SlickNik> I'll get back to prepp'ing for the mid-cycle then.
16:21:57 <SlickNik> Catch you later.
16:29:19 <ttx> SlickNik: all set at https://launchpad.net/trove/kilo/kilo-2
16:29:54 <ttx> devananda: want to run your sync now ?
16:35:45 <devananda> ttx: nope. having a delightful argument with jaypipes about whether or not Nova should have any support for Ironic
16:36:08 <ttx> ah :)
16:36:09 <devananda> ttx: tldr; the midcyucle is going on, we're updating LP as we land things, and I'll send you a SHA at some point
16:36:16 <devananda> ttx: and if not, you're free to tag on thursday :)
16:37:14 <ttx> ok, let's skip the regular time too then
16:53:14 <ttx> notmyname: around ? Nothing special to cover, so we can skip
16:53:25 <notmyname> ttx: I'm here
16:53:33 <ttx> #topic Swift
16:53:41 <ttx> #info 2.2.2 released
16:53:46 <notmyname> 2.2.2 was released yesterday
16:53:48 <notmyname> thanks
16:53:54 <ttx> #link https://launchpad.net/swift/kilo/2.2.2
16:54:07 <notmyname> #info next week is the swift midcycle/hackathon
16:54:13 <ttx> notmyname: where is that ?
16:54:22 <notmyname> at the swiftstack office in san francisco
16:54:32 <ttx> You might want to add it to https://wiki.openstack.org/wiki/Sprints
16:54:39 <notmyname> should be about 30 people (from at least 5 countries)
16:54:51 <ttx> (or do it next time)
16:54:54 * notmyname didn't know that page existed
16:55:03 <ttx> which is why I advocate its use :)
16:55:10 <ttx> not very successful at that
16:55:32 <ttx> but some people have been complaining that midcycle things suck because nobody knows they happen
16:55:41 <ttx> and that was the answer we gavce the board
16:56:05 <ttx> I'd argue the people who need to know know
16:56:12 <ttx> but then that feels a bit elitist
16:57:50 <ttx> notmyname: any other thing you wanted to cover ?
16:58:34 <notmyname> nope. I'm good
16:58:42 <ttx> notmyname: have a good week
16:58:52 <ttx> morganfainberg: ready when you are
17:02:39 <morganfainberg> O/
17:02:42 <ttx> #topic Keystone
17:02:45 <morganfainberg> Sorry was being chased
17:02:51 <ttx> #link https://launchpad.net/keystone/+milestone/kilo-2
17:02:52 <morganfainberg> By people in irc ;)
17:03:06 <ttx> I'm chased too, so don't worry if I go mute :)
17:03:10 <morganfainberg> Will be pairing that down today to anything that is not in flight
17:03:15 <morganfainberg> Or merged
17:03:26 <ttx> OK, today :)
17:03:29 <morganfainberg> Bugs might increase if a fix has been committed.
17:03:42 <ttx> just keep blockers in
17:03:46 <morganfainberg> The federation one might get one more patch.
17:03:49 <ttx> I mean, keep only blockers in
17:04:13 <morganfainberg> Bugs won't be reduced at this point I think. All should have code in flight.
17:04:54 <morganfainberg> Federation Bp that is. We are looking at the ietf don't use x prefixed headers
17:05:03 <ttx> OK, I might ping you when you are done if I spot a dark/incoherent area
17:05:06 <morganfainberg> Meaning a rename of 2 headers or elimination of it.
17:05:10 <ttx> ping me when you're done cleaning up
17:05:14 <morganfainberg> Sounds good. Will ping.
17:05:32 <morganfainberg> 2 new headers that is*
17:05:54 <morganfainberg> But I spent a chunk of time last night getting things pushed through.
17:06:07 <ttx> ok
17:06:18 <morganfainberg> Keystone client will be released on Monday same as middleware to prevent accidentally breaking gate this week for you.
17:06:25 <morganfainberg> ;)
17:06:33 <ttx> awesome!
17:06:36 <morganfainberg> Not that I expect to break gate. But...
17:06:53 <ttx> Will track the things you keep in the page and ping you if I think we won't make it, or if we made it :)
17:07:14 <ttx> morganfainberg: anything else ?
17:07:15 <morganfainberg> Yep. I hope to have a sha for you today.
17:07:26 <morganfainberg> Nope that's it.
17:07:32 <ttx> alrighty, ttyl
17:07:41 <ttx> #endmeeting