08:14:50 <ttx> #startmeeting ptl_sync
08:14:51 <openstack> Meeting started Tue Aug 26 08:14:50 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:14:52 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:14:54 <openstack> The meeting name has been set to 'ptl_sync'
08:14:57 <ttx> #topic Nova
08:15:10 <ttx> #link https://launchpad.net/nova/+milestone/juno-3
08:16:03 <ttx> #info 8 implemented, 50 in review
08:16:46 <ttx> It's not totally bad -- but yes, you need to seriously increase the conversion rate here
08:17:03 <ttx> go from 5 to 25.
08:17:06 <ttx> :)
08:17:43 <ttx> johnthetubaguy: how close are the "High" ones ?
08:19:02 <johnthetubaguy> ttx: I am told very close
08:19:28 <johnthetubaguy> so ironic is risky, but we really want it
08:19:29 <ttx> It would be... safer to merge them this week basically
08:19:40 <ttx> (or at least most of them)
08:20:04 <johnthetubaguy> right, I think these are ones that get exceptions if they don't make it, but I need to dig a big further, I might demote the scheduler libriary
08:20:23 <johnthetubaguy> yeah, ironic will be to the wire I think, but lets see
08:20:58 <ttx> At least now the list is finite
08:21:06 <johnthetubaguy> true :)
08:21:21 <ttx> and easily prioritized
08:21:38 <johnthetubaguy> yeah, we have lots of mediums, I should probably check up on those, and try to demote the ones that are slipping
08:21:47 <ttx> This is really review money time (now)
08:22:06 <ttx> next week is the milestone week, I wouldn't expect that much work to get through
08:23:22 <ttx> Any specific event (like a review day) planned?
08:23:31 <johnthetubaguy> not at this point
08:23:41 <johnthetubaguy> its a good idea though
08:24:08 <ttx> It could help in getting a few that are at 99% landed
08:24:18 <johnthetubaguy> yeah, maybe try for Thursday or Friday as a review day
08:24:29 <ttx> Or just a review-specific meeting
08:24:51 <ttx> single out the ones that are almost there, and give them the final push
08:25:05 <johnthetubaguy> yeah, we can try do that informally on IRC
08:25:32 <johnthetubaguy> I guess
08:25:37 <ttx> ok
08:25:56 <ttx> We'll track further progress during the week
08:25:59 <johnthetubaguy> honestly, I feel like I need more insight into how close all these blueprints are
08:26:11 <johnthetubaguy> its a bit opaque right now
08:26:29 <johnthetubaguy> yeah, would be good to catch up later in the week
08:26:29 <ttx> I agree that the status is too granular
08:27:08 <johnthetubaguy> my plan is, I need to do some more reviews, so I will dig in and just see how its all going
08:27:14 <ttx> it works well only for single-review things and there aren't so many of those
08:27:23 <johnthetubaguy> yes, thats true
08:27:59 <ttx> anything else you wanted to mention?
08:28:07 <ttx> Any topic for the meeting today?
08:28:19 <johnthetubaguy> I don't think so, I guess I will try demote the priority of a few blueprints where they don't seem close
08:28:27 <johnthetubaguy> nothing really to filter up
08:28:36 <johnthetubaguy> well, I guess, the slots ideas are still cooking
08:28:52 <johnthetubaguy> we kinda quietly opened for K specs
08:28:58 <ttx> sssh.
08:29:03 <johnthetubaguy> yeah, sorry
08:29:04 <ttx> don't speak too loud
08:29:05 <johnthetubaguy> :)
08:29:14 <johnthetubaguy> thats exactly my plan...
08:29:33 <johnthetubaguy> we have no intention of reviewing them right now but anyways
08:29:38 <ttx> johnthetubaguy: ok then. I'll be in touch, probably Thursday, to see how well we progressed
08:29:44 <johnthetubaguy> awesome, thanks
08:30:00 <ttx> Thank you!
12:02:08 <ttx> SergeyLukjanov: ready when you are
12:09:14 <SergeyLukjanov> ttx, I'm here
12:09:39 <SergeyLukjanov> ttx, sorry for being a bit later
12:10:09 <ttx> #topic Sahara
12:10:19 <SergeyLukjanov> #link https://launchpad.net/sahara/+milestone/juno-3
12:11:35 <ttx> #info 7 implemented, 4 under review, 5 inprogress
12:11:50 <ttx> slow progress compared to last week
12:12:15 <ttx> but still on track
12:12:35 <SergeyLukjanov> yup, there were some blockers
12:12:48 <SergeyLukjanov> but I think it's going to be merged till j3
12:13:32 <ttx> don't forget gate is likely to explode next week
12:13:43 <ttx> so don't count on Tuesday-Thursday next week that much
12:13:55 <ttx> I would get everything in this week if I were you ;)
12:13:55 <SergeyLukjanov> ttx, yeah, our sahara-ci has been exploaded this weekend :)
12:14:25 <ttx> How is https://blueprints.launchpad.net/sahara/+spec/edp-swift-trust-authentication doing?
12:14:44 <ttx> is there a lot of code missing?
12:14:58 <SergeyLukjanov> not a lot, but some code is still missing
12:15:18 <SergeyLukjanov> I think that all sahara parts of this blueprint will be ready in j3
12:15:29 <SergeyLukjanov> and will not use FFE for it
12:15:38 <ttx> OK cool.
12:15:52 <ttx> anything you wanted to talk about ? Any topic for the meeting later?
12:16:11 <SergeyLukjanov> I think no topics
12:16:26 <SergeyLukjanov> I'd like to note that sahara@horizon is going good
12:16:35 <SergeyLukjanov> and mostly all of the changes has been merged
12:16:45 <SergeyLukjanov> and we're not going to release dashboard's j3
12:16:56 <ttx> awesome
12:17:16 <SergeyLukjanov> we need to keep repo fot some more time because of stable/icehouse branch in it
12:17:29 <ttx> SergeyLukjanov: right
12:17:42 <ttx> SergeyLukjanov: ok then, talk to you later
12:17:46 <ttx> dhellmann: around?
12:17:48 <SergeyLukjanov> thank you
12:17:52 <dhellmann> ttx: hi!
12:17:57 <ttx> #topic Oslo
12:18:02 <ttx> dhellmann: hola!
12:18:17 <ttx> dhellmann: I think we have a way forward for the LP tracking now
12:18:28 <dhellmann> the project group?
12:18:33 <ttx> dhellmann: yes. I'll proceed and ask LP admins to move things
12:18:46 <dhellmann> ok, let me know if there's anything you need me to do, too
12:18:48 <ttx> oslo->oslo-incubator and new oslo projectgroup
12:19:12 <ttx> the only thing that I could see malfunctioning is that Lp has a (handy) redirection feature for renamed projects
12:19:36 <ttx> so if you go to lp/svanna you get the lp/sahara page
12:19:47 <dhellmann> ah, and we wouldn't want that turned on
12:19:53 <ttx> but here we want lp/oslo to land on the projectgroup :)
12:20:10 <dhellmann> we could call the group openstack-oslo
12:20:13 <ttx> right, so that's the only left unknown (together with the will of LP admins to accept to create a projectgroup)
12:20:30 <ttx> I guess we could.
12:20:44 <ttx> but oslo would be better I think, if we can have it
12:20:48 <dhellmann> if they can avoid the bad redirect, oslo is fine, sure
12:21:34 <ttx> hm.
12:21:48 <ttx> ctrl-C is too close to ctrl-X apparently
12:21:53 <dhellmann> heh
12:21:56 <ttx> https://launchpad.net/oslo/+milestone/juno-3
12:22:16 <ttx> I think we established in the past that most of the work here is not FF-sensitive
12:22:37 <ttx> but still, is it time to defer a few things ?
12:22:41 <dhellmann> yeah, at this point I don't expect active adoption of new libraries
12:23:06 <dhellmann> dims started working on the logging stuff yesterday, so that may be done even though it was assigned to me :-)
12:23:24 <ttx> hmm, rootwrap daemon mode should be considered implemented, fixing
12:23:24 <dhellmann> we're behind on some reviews, so we'll be shifting gears to focus on finishing things this week
12:23:37 <dhellmann> has that been released?
12:23:47 <ttx> merged, not released
12:23:57 <ttx> waiting for a few more tests, but we'll release this week
12:24:11 <ttx> one question is shoudl we do 1.3 or 2.0
12:24:15 <dhellmann> ok, I have a short list of other releases for this week but I'll let you handle that when you're ready
12:24:24 <dhellmann> is the old API still present?
12:24:29 <ttx> yes
12:24:43 <dhellmann> as long as it's still compatible with existing users, you can stay in the 1.x series
12:24:51 <ttx> well, its' not strictly an API, but the old way of using it is preserved
12:25:08 <ttx> ok, makes sense
12:25:10 <dhellmann> well, yeah, that's what I meant
12:25:13 <ttx> 1.3 it is
12:25:24 <ttx> 1.3 ships a client API though for the daemon mode
12:25:38 <dhellmann> that's fine, that's a new feature not a breaking change
12:25:41 <ttx> so we'll have to preserve that starting from now
12:26:08 <dhellmann> do you foresee removing the old command line API?
12:26:23 <ttx> Not really. It's still "more secure"
12:26:38 <ttx> as in simpler.
12:26:38 <dhellmann> ok
12:27:36 <dhellmann> I do have something to bring up with you, to be thinking about for kilo.
12:27:43 <ttx> so do you still plan to cover all the j3 targets ?
12:27:56 <ttx> with some being deferred to rc1 probably ?
12:28:21 <dhellmann> I'm going to review that list today and talk to josh and a couple of other people about their status. I'll have it up to date by tomorrow morning.
12:28:25 <dhellmann> is there an rc1 target yet?
12:28:31 * ttx tries to wrap his haed around this list but without the incub/lib distinction it's kinda hard
12:28:46 <dhellmann> yeah, I wish I could tag bps and filter this list
12:29:06 <ttx> in the meantime, i just trust you have things under control :)
12:29:06 <dhellmann> soon enough
12:29:16 * dhellmann tries not to laugh out loud
12:29:44 <ttx> dhellmann: so.. kilo
12:29:51 <dhellmann> seriously, I think most of this is going to land at some point in juno, but since we're not rushing to make the ff deadline some is likely to be rc1 or later
12:29:59 <ttx> right
12:30:23 <dhellmann> ok, so, we have recently had some trouble with graduating modules that are dependencies of modules that have not graduated
12:30:42 <dhellmann> for instance, oslo.utils took strutils out of the incubator, but lots of things use strutils and are not graduating
12:31:22 <dhellmann> our original plan was to leave the incubated code alone, but in some cases that makes it harder to adopt because tests in the projects are mocking out the incubated version of a function and some code is calling the non-incubated version
12:31:37 <dhellmann> I think that was actually timeutils, but it doesn't really matter
12:31:46 <ttx> why is it a problem for non-gaduated libs to use graduated libs ?
12:32:16 <dhellmann> well, we didn't want to update the incubated code to use the graduated libs because that meant if anyone needed a patch to the non-graduated code they would *have* to adopt the library at the same time
12:32:32 <dhellmann> but that's turning into too much trouble, so we want to change that
12:32:51 <dhellmann> for kilo, we want to branch early, and then delete things as soon as their graduated library is available for use
12:33:10 <dhellmann> the early branch still gives us a way to backport changes for projects that haven't adopted a library
12:33:22 <dhellmann> although it occurs to me that the branch might just be stable/juno
12:33:48 <ttx> stable/juno shall work for you if you branch early in Kilo, yes
12:34:09 <dhellmann> when would that stable branch normally be cut?
12:34:28 <dhellmann> your "if you branch early" comment makes me think not immediately?
12:34:50 <ttx> we usually did it sometimes between RC1 and release
12:35:02 <dhellmann> ok, that seems like good timing for us
12:35:18 <ttx> i.e. we would tag the "final" juno oslo-incubator when you want it opened for kilo
12:35:49 <ttx> and once the final tag is in, we can branch
12:35:52 <dhellmann> right, and I think earlier is probably better
12:36:32 <dhellmann> I'll need to make sure we have the necessary changes landed first, but I don't think we have much targeted so it shouldn't be an issue
12:36:37 <ttx> although we can do even earlier if needed, nothing "consumes" that anyway
12:36:48 <ttx> testing-wise
12:36:59 <dhellmann> and I will go through the juno planning stuff we put together and make sure the change to deleting modules isn't going to introduce any other weirdness
12:37:13 <ttx> ack
12:37:19 <dhellmann> ok, we might do it when our last planned graduation happens this cycle, then
12:37:31 <dhellmann> that way if we do have juno bug fixes, we have a place to put them
12:37:41 <ttx> Sounds good. anything else you wanted to mention ? Topics for the release meeting ?
12:37:55 <dhellmann> no, that was it
12:38:08 <ttx> dhellmann: thx!
12:38:11 <ttx> gordc: o/
12:38:19 <dhellmann> ttx: thanks, ttyl!
12:38:28 <gordc> o/
12:38:31 <ttx> #topic Ceilometer
12:38:41 <ttx> #link https://launchpad.net/ceilometer/+milestone/juno-3
12:39:20 <gordc> so we have code for all our bps up and ready for review
12:39:22 <ttx> #info 3 implemented, 6 in review, 1 in progress, 1 blocked
12:39:42 <gordc> i think we're making good progress on high priority items...
12:39:51 <gordc> we've gone through several rounds of reviews on those items
12:40:00 <ttx> Is https://blueprints.launchpad.net/ceilometer/+spec/paas-event-format-for-ceilometer code already in review ?
12:40:15 <ttx> it's only marked "good progress"
12:40:35 <gordc> that bp has a patch up as well but i don't believe it's passed jenkins yet so i've left it as good progress for now
12:40:44 <ttx> ok
12:40:55 <gordc> it's been reviewed a few times i believe so i could mark it as review if that's easier to track
12:41:36 <ttx> https://blueprints.launchpad.net/ceilometer/+spec/grenade-resource-survivability still blocked on https://review.openstack.org/#/c/102354 ?
12:42:08 <gordc> yes, that's the one issue we have... i switched the item to blocked recently since we made no progress
12:42:10 <ttx> gordc: if it doesn't need a complete rewrite of the patch, making it "needs code reveiw" will not raise any alarm
12:42:37 <gordc> ok i'll confirm with owner and switch to needs review
12:42:38 <ttx> gordc: could you summarize the issue on grenade-resource-survivability, see if I can help unblock?
12:42:59 <gordc> sure. i'll try my best to summarise
12:43:47 <gordc> from my understanding there is a debate on what we should be testing in grenade test between joe gordon and chris dent.
12:44:18 <gordc> to my knowledge chris is pretty much unsure what to do... just that what he put  up for review isn't it.
12:44:47 <gordc> we reached out to joe gordon on thursday at our meeting for clarification and he said he'd contact chris later.
12:45:11 <ttx> might be worth raising that issue at the meeting today
12:45:17 <gordc> i just checked with chris today and he hasn't heard from joe yet so i was probably going to reach out to him today to see if we can get some action
12:45:19 <ttx> we could collect more opinions
12:45:24 <gordc> yeah. that sounds good.
12:45:40 <gordc> i think chris is open to anything. just that we're not sure what 'anything' is at this point
12:46:05 <ttx> #info grenade-resource-survivability blocked pending discussion between jog0 and Chris Dent
12:46:54 <gordc> aside from grenade bp i think we're ok. hoping to get more reviews once eglynn and llu return in next few days
12:47:30 <ttx> I would definitely advise to merge as much as you can this week
12:47:35 <ttx> next week should be a bit busy
12:48:09 <gordc> yeah. i was hoping to get a bit more merged this past week but we were blocked by a gating issue when tox was upgraded in the gates.
12:48:22 <gordc> we have a workaround now so we should be able to make some progress
12:48:28 <ttx> ok, cool
12:48:37 <ttx> gordc: that's all I had
12:48:45 <ttx> gordc: anything else for the meeting tonight ?
12:49:03 <gordc> i think thats all on my end
12:49:08 <gordc> i'll just track the grenade item for onw
12:49:10 <gordc> now*
12:49:21 <ttx> gordc: great, and thanks a lot for stepping up while eglynn was away
12:49:48 <gordc> np. he did a good job doing a brain dump before he left.
14:01:19 <ttx> jgriffith: around?
14:07:50 <ttx> dolphm: you can go now if you're around
14:16:19 <dolphm> ttx: o/
14:16:39 <dolphm> would have helped if i had irc open
14:18:03 <ttx> indeed
14:18:06 <ttx> #topic Keystone
14:18:21 <ttx> #link https://launchpad.net/keystone/+milestone/juno-3
14:18:46 <ttx> #info 3 implemented, 5 in review, 2 in progress, 1 blocked
14:19:14 <ttx> About the blocked one, I raised a thread and will mention it at the cross-project meeting again
14:19:18 <dolphm> bp non-persistent-tokens (currently good progress) has been a series of roadblocks and hurdles throughout juno - we made a ton of progress, but it doesn't look like it's going to make juno-3
14:19:24 <dolphm> ttx: thanks
14:19:38 <ttx> I'd like to understand if it('s just "annoying" or "blocking"
14:19:48 <ttx> (the dep thing)
14:20:58 <dolphm> our approach for federating across multiple keystones is to use SAMLv2 (which allows us to federate with non-keystones as well). our approach for generating SAMLv2 docs is with pysaml2
14:21:29 <dolphm> so it's either re-invent an XML + crypto library or use one off the shelf
14:21:50 <dolphm> steve documented a couple alternatives in the requirements review, but it doesn't sound like any others are a better option
14:22:11 <dolphm> and switching libs would probably mean missing juno
14:22:14 <ttx> yeah, I was wondering if the saml one (which was the less worse alternative) was an option
14:22:40 <ttx> could be good to explore that scenario, just in case we hit a wall
14:22:53 <ttx> but my understanding was that it was a pain generator, not a blocker
14:23:03 <dolphm> that one describes itself as an alpha; but at least has a release this year
14:23:07 <ttx> we could even have a plan to migrate off to saml to remove the pain generator
14:23:29 <ttx> that's what I want us to clear up tonight
14:24:07 <ttx> in the mean time, you need to continue landing stuff, nice progress over the last week
14:24:57 <dolphm> 44 patches to go at this point :(
14:25:23 <ttx> I'd recommend you get as much merged this week as you can :)
14:25:33 <dolphm> of course!
14:25:51 <ttx> We'll review in-week progress in ~2 days
14:26:18 <dolphm> alrighty
14:26:20 <ttx> anything else you wanted to mention ?
14:26:35 <ttx> Anything for the meetign (in addition to the saml discussion) ?
14:27:04 <dolphm> no sir
14:27:24 <ttx> alright, thx!
14:28:16 <ttx> jgriffith: still not around?
14:29:56 <ttx> david-lyle: we can start now if you're available
14:30:13 <david-lyle> ttx: ready
14:30:15 <ttx> #topic Horizon
14:30:26 <ttx> #link https://launchpad.net/horizon/+milestone/juno-3
14:30:38 <ttx> #info 9 implemented, 38 under code review
14:30:56 <ttx> Still leaves a lot to process :)
14:31:11 <david-lyle> yeah, there are a lot in flight
14:31:34 <david-lyle> quite a few are in good shape just need another review
14:31:55 <david-lyle> a few are still a little less reviewed and may not make the cut
14:32:03 <ttx> david-lyle: ok, you should really push early this week, rather than next week
14:32:12 <david-lyle> definitely
14:32:30 <ttx> I like that all the High targets are in
14:32:49 <david-lyle> but we want to do our part to add to the semi-annual gate jam
14:32:57 <david-lyle> :)
14:33:10 <ttx> You might want to call a specific meeting to get those last reviews the final +2
14:33:41 <david-lyle> Sounds like a good idea
14:33:59 <ttx> I don't think I can suggest much more from where i stand.. review review review... we'll lok at progress in two days
14:34:17 <ttx> see how fast the wall is approaching
14:34:25 <david-lyle> always too quickly
14:34:50 <ttx> anything you wanted to discuss at the meeting ? You don't seem to have anything blocked
14:35:10 <david-lyle> no, I think reviews are our only hold-up now
14:36:00 <ttx> david-lyle: then I'll let you concentrate on those :)
14:36:02 <ttx> david-lyle: thx!
14:36:10 <david-lyle> thanks
14:37:06 <ttx> mestery: ready when you are
14:37:11 <mestery> \o/
14:37:16 <ttx> #topic Neutron
14:37:28 <ttx> #link https://launchpad.net/neutron/+milestone/juno-3
14:37:46 <ttx> #info 10 implemented, 54 in review
14:38:00 <ttx> nice cleanup
14:38:08 <mestery> Thanks, more to come, but I'm working on it everyday at this point.
14:38:24 <ttx> but 1/day velocity won't get you very far when the door closes
14:38:29 <mestery> Agreed.
14:38:38 <mestery> I've already started booting some out which I don't think have a chance at landing.
14:39:01 <ttx> anything planned to give the medium/high a final push?
14:39:08 <ttx> some review-centric meeting?
14:39:21 <ttx> your meetings have had other issues to discuss recently
14:39:29 <mestery> I've been thinking of that, perhaps Thursday this week.
14:39:31 <ttx> so you can't really prioritize reviews there
14:39:35 <mestery> Right
14:39:47 <mestery> Speaking of meetings: I plan to completely revamp the Neutron meeting after Feature Freeze
14:39:49 <mestery> It's become stale
14:39:50 <ttx> yes, thursday this week is about as much you can wait
14:39:53 <mestery> Needs a breath of fresh air
14:39:58 <mestery> ttx: ++
14:40:15 <ttx> after that, it will get difficult, unless you work on Labor day
14:40:34 <mestery> Totally agree, I'll see if I can set it up for Wednesday actually.
14:40:38 <mestery> That gives us one more day
14:40:46 <ttx> ++
14:41:14 <ttx> I don't think there is anything I can help unblock, apart from reviews you seem in good shape
14:41:15 <mestery> The good news is we're making progress on many High/Medium community BPs
14:41:21 <mestery> Agreed
14:41:33 <ttx> yes, I would focus the review meeting on medium/high tbh
14:41:33 <mestery> L3 HA, ipset, and security groups RPC refactor are all in good shape.
14:41:39 <mestery> Absolutely
14:41:45 <mestery> Low are "best effort"
14:41:52 <ttx> if time left, you can address low-hanging fruit in Low
14:41:57 <mestery> yes
14:41:59 <ttx> but there won't be (time left)
14:42:03 <mestery> :)
14:43:11 <ttx> Anything you'd like to discuss at meeting today?
14:43:30 <mestery> Is the "PTL vs. czar" thing on the agenda?
14:43:34 <mestery> Or is that a ML thread only thing.
14:43:40 <mestery> Seems project meeting may be a good place to continue that discussion
14:44:49 <ttx> we can discuss that, sure
14:45:01 <ttx> Could you add it to the agenda ?
14:45:01 <mestery> Well, only if others want as well, maybe the ML thread is dieing down now :)
14:45:10 <mestery> Will do
14:45:13 <ttx> thx!
14:45:18 <mestery> np!
14:45:51 <ttx> ok then, talk to you later!
14:45:57 <ttx> jgriffith: still not around?
14:46:18 <mestery> ttx: later and thanks!
15:22:36 <jgriffith> ttx: hey... still up?
15:22:47 <ttx> jgriffith: sure, just a sec
15:23:42 <ttx> jgriffith: hi!
15:23:46 <ttx> #topic Cinder
15:23:48 <jgriffith> ttx: howdy
15:24:04 <ttx> #link https://launchpad.net/cinder/+milestone/juno-3
15:24:16 <ttx> #info 3 implemented, 16 in review
15:24:21 <jgriffith> :(
15:24:35 <ttx> that's still a lot of review work to complete in 8 days :)
15:24:42 <jgriffith> agreed
15:24:50 <jgriffith> some are pretty far along
15:24:50 <ttx> how are the two medium ones going?
15:25:01 <jgriffith> those are close
15:25:14 <jgriffith> I expect them to get cleaned up and finished in the next day or so
15:25:14 <ttx> would be great to land them this week to remove a bit of pressure
15:25:18 <ttx> cool
15:25:23 <jgriffith> yeah, totally agree
15:25:43 <jgriffith> I've already let it be known drivers are my lowest priority
15:25:56 <ttx> that must make you a very popular person
15:25:57 <jgriffith> There's a couple in there I need to manually update
15:26:03 <jgriffith> ttx: Yeah, I'm loved!
15:26:05 <jgriffith> :)
15:26:47 <ttx> do you think you could benefit from a review meeting where you would give a few targeted blueprints a final +2 push?
15:26:50 <jgriffith> ttx: I'm not sure about the bugs, but at least I know I can work on those after 3 closes
15:27:02 <jgriffith> j3 that is
15:27:16 <ttx> re: bugs; that's what rc1 is for, unless you have critical ones or regressions
15:27:26 <jgriffith> yeah
15:27:29 <jgriffith> that's my plan
15:27:40 <jgriffith> but I'm certain there will be *new* ones once we cut
15:27:49 <jgriffith> based on history at any rate
15:28:07 <jgriffith> everyones's pretty distracted right now, between last minute features/reviews and third prty ci
15:28:29 <ttx> I'll let you go back to it. This week is money time
15:28:37 <jgriffith> I'll have an updated turn on the bp list tomorrow
15:28:48 <jgriffith> well... one today, and another after the meeting tomorrow
15:28:53 <ttx> anything you'd like to discuss at meeting today?
15:29:07 <ttx> i'll look at progress in a couple of days, see how badly we are f*ed
15:29:11 <jgriffith> we could continue the summit talks :)
15:29:20 <jgriffith> ttx: think positive!
15:29:31 <jgriffith> see how amazing the recovery is in 24 hours :)
15:29:38 <ttx> we have merged 15% of the j-3 targets in 80% of the time
15:29:50 <jgriffith> damn you and your statistics
15:29:53 <ttx> how positive is hat
15:29:54 <jgriffith> :)
15:29:55 <ttx> +t
15:30:17 <jgriffith> alright... I'll catch up with you this afternoon
15:30:18 <jgriffith> thanks
15:30:23 <ttx> jgriffith: thx!
15:30:38 <ttx> notmyname: ready when you are
15:30:47 <ttx> unless you want to opsmeetup-skip
15:30:54 <notmyname> ttx: I'm here. I'm in the ops meetup right now
15:31:05 <notmyname> nah, I can space a few minutes
15:31:06 <ttx> notmyname: we can make it quick and painless
15:31:17 <notmyname> thanks for doing the rc tag
15:31:17 <ttx> like a stab in a kidney
15:31:21 <notmyname> heh
15:31:27 <ttx> #topic Swift
15:31:36 <notmyname> I'm reminded that I need to send an email to the ML about the RC
15:31:40 <ttx> #link https://launchpad.net/swift/+milestone/2.1.0
15:31:47 <ttx> I think I saw one
15:31:55 <notmyname> oh yeah. maybe I didn that
15:32:00 <notmyname> *did
15:32:15 <notmyname> yup. just checked
15:32:22 <ttx> [openstack-dev] [Swift] 2.1.0-rc tagged
15:32:30 <notmyname> I'll be getting LP filled out this week
15:32:34 <ttx> looking good so far?
15:33:03 <notmyname> yes, AFAIK. there wasn't much in it that's concerning. work continues on erasure code work
15:33:31 <ttx> do you think the erasure code stuff would land in the juno final?
15:33:53 <ttx> or you'd rather introduce it early in kilo when ready
15:34:38 <notmyname> I think it will be very hard to get it in juno. early kilo is more likely. (although there are many people who want it in juno)
15:34:55 <notmyname> #link https://trello.com/b/LlvIFIQs/swift-erasure-codes
15:35:02 <notmyname> that's the living "what's going on" tool
15:35:07 <ttx> I'll be around on monday for your sign-off on the 2.1.0 tag. If you need backports, contact me asap so that we set up the branch
15:35:20 <notmyname> ttx: thanks. will do
15:35:44 <ttx> notmyname: anything you'd like to discuss at meeting today? Or will you be enjoying post-meetup activities?
15:36:19 <notmyname> I'll be in the middle of the ops meetup (facilitating a storage discussion) this afternoon and won't be able to make it)
15:36:53 <ttx> ok, fair enough!
15:36:57 <ttx> talk to you later then
15:37:08 <notmyname> thanks
15:37:30 <ttx> zaneb: ready when you are
15:37:36 <zaneb> o/
15:37:38 <ttx> #topic Heat
15:37:45 <ttx> #link https://launchpad.net/heat/+milestone/juno-3
15:38:02 <ttx> #info 3 implemented, 8 in review, 3 in progress
15:38:42 <ttx> that's slow progress in last two weeks, lots of ground left to cover in one week
15:39:03 <ttx> zaneb: how are those two "high" priority ones doing ?
15:39:06 <zaneb> yeah, there are lots of reviews to do
15:39:22 <ttx> cancel-update-stack & update-failure-recovery
15:39:45 <zaneb> mine has not made much progress because I've been debating with you on openstack-dev all week ;)
15:40:05 <zaneb> but it should be a matter of adding a couple of unit tests, most of the patches have been reviewed already
15:40:06 <ttx> zaneb: I'll stop arguing then :)
15:40:23 <ttx> ok, so should land this week ?
15:40:45 <zaneb> yes
15:40:48 <ttx> what about the other one ?
15:40:58 <zaneb> the other one is looking somewhat doubtful
15:41:36 <zaneb> I need to check back on comments on the review
15:41:45 <ttx> would you be requiring a feature freeze exception to get it in?
15:41:57 <ttx> or a few extra days won't hep it
15:41:58 <ttx> +l
15:42:41 <zaneb> I would be inclined not to do a FFE, except that TripleO needs this
15:43:01 <zaneb> I'll have to review the latest comments and see what the scope of any changes is
15:43:22 <ttx> ok
15:43:56 <ttx> https://blueprints.launchpad.net/heat/+spec/stack-display-fields is not assigned -- does it have anybody working on it ?
15:44:15 * ttx sees Richard Lee
15:44:29 <ttx> should he be assigned/credited for it?
15:44:39 <zaneb> I think andersonvom
15:44:53 <zaneb> actually, I believe they pair-program
15:44:58 <zaneb> so it's always hard to tell :D
15:45:06 <ttx> damn
15:45:24 <ttx> we need to make sure storyboard is PP-compatible
15:45:41 <ttx> randomly displaying one or the other
15:45:47 <zaneb> looks like it already merged anyway
15:46:07 <ttx> yay win
15:46:16 <ttx> I assigned, you can update status
15:46:39 <zaneb> yeah, I just pinged Richard in #heat for an update
15:47:07 <ttx> OK well, just keep on reviewing, and don't place too much hope in the gate next week, so review now if you have a choice
15:47:20 <zaneb> hah, yes :)
15:47:21 <ttx> anything you'd like to discuss at cross-project meeting today?
15:47:43 <zaneb> I had a question about packaging of functional tests on openstack-dev
15:47:55 <zaneb> might be a good one to discuss quickly while everyone is in one place
15:48:02 <ttx> sure, add it to agenda
15:48:06 <ttx> https://wiki.openstack.org/wiki/Meetings/ProjectMeeting
15:48:26 <zaneb> #link http://lists.openstack.org/pipermail/openstack-dev/2014-August/044072.html
15:48:33 <ttx> talk to you later, then?
15:48:52 <zaneb> yep, thanks!
15:50:08 <ttx> SlickNik: ready when you are (our usual time is ok)
15:59:01 <SlickNik> ttx: here now
15:59:28 <ttx> #topic Trove
15:59:30 <ttx> SlickNik: o/
15:59:36 <SlickNik> o/
15:59:59 <ttx> #link https://launchpad.net/trove/+milestone/juno-3
16:00:08 <ttx> #info 8 in review
16:00:30 <ttx> so that's not showing that much progress compared to two weeks ago
16:00:49 <ttx> wasn't your meetup all focused on getting stuff done ?
16:01:01 <SlickNik> We have a couple of pretty big items that we're almost done with.
16:01:23 <SlickNik> Yes, and I think we made good progress at the meetup.
16:01:30 <ttx> I fear you're going to get blocked in gate if you submit those too late... so get them reviewed and merged asap
16:01:34 <SlickNik> Just need to close out a couple of more patches
16:01:39 <SlickNik> Replication and clustering
16:01:44 <SlickNik> Roger that.
16:01:58 <SlickNik> Replication is on track to be implemented today / tomorrow.
16:02:01 <ttx> How is replication coming up ? How far is it ?
16:02:04 <ttx> heh
16:02:08 <ttx> cool
16:02:35 <SlickNik> Of the 7 patches needed - 4 are merged.
16:02:49 <SlickNik> And 2 / 3 have 1 +2
16:02:55 <ttx> We'll be havign another look at progress in two days, see how fast the wall is approaching
16:03:04 <SlickNik> and 1 is pending to look at today.
16:03:17 <ttx> in the mean time, I'll try to stay out of the way
16:03:40 <ttx> anything you want to discuss at meetign today ? Anything blocking you?
16:04:02 <SlickNik> Nothing blocking, just trying to get stuff moved through the pipeline. :)
16:04:24 <SlickNik> btw, one of the things we discussed at the mid-cycle is that we want to move to a trove-specs process.
16:05:20 <ttx> awesome!
16:05:29 <ttx> starting with Kilo I suspect
16:05:33 <SlickNik> One of the big challenges we have is being able to review BPs offline, and trove-core unanimously felt that having the specs in gerrit will really help here.
16:05:40 <ttx> #info Trove to adopt -specs for Kilo
16:05:42 <SlickNik> ttx: yes, starting with Kilo
16:06:06 <ttx> SlickNik: ok, anoything else coming out of the meetup?
16:06:09 <SlickNik> after juno-3, I'll work on getting the infra set up for that.
16:07:04 <SlickNik> Not much else interesting from a cross project perspective.
16:07:22 <ttx> ok, talk to you later then
16:07:32 <SlickNik> A lot of conversations trying to get on the same page with patches in flight, and reviews.
16:07:43 <ttx> hmm, ok
16:08:44 <ttx> Anyone here to represent glance ?
16:08:47 <SlickNik> Talk to you in a bit.
16:08:49 <SlickNik> Thanks ttx!
16:08:53 <ttx> SlickNik: thx!
19:29:53 <ttx> #endmeeting