08:02:16 <ttx> #startmeeting ptl_sync
08:02:17 <openstack> Meeting started Tue Sep 23 08:02:16 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:02:18 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:02:20 <ttx> #topic Nova
08:02:20 <openstack> The meeting name has been set to 'ptl_sync'
08:02:25 <mikal> Hi
08:02:37 <ttx> ohai
08:02:42 <ttx> #link https://launchpad.net/nova/+milestone/juno-rc1
08:02:50 <mikal> Yeah, that
08:02:58 <mikal> So... where to start?
08:03:03 <mikal> I'm a bit worried about the unassigned bugs
08:03:16 <ttx> The curve is not really going down at http://old-wiki.openstack.org/rc/
08:03:28 <johnthetubaguy> mikal: yeah, had that issue a bit ago
08:03:42 <mikal> Huh, no worse than many other projects though
08:03:44 <johnthetubaguy> ttx: so people are adding all sorts they find important-ish, rather than blockers
08:04:11 <mikal> Yeah, I was trying to review things associated with those bugs and ended up lost spending the last two days fixing a security vulnerability that was release critical
08:04:16 <ttx> johnthetubaguy: it's tricky because damn LP doesn't prevent anyone from doing that
08:04:18 <mikal> Because the proposed fix set off my bogo filter
08:04:26 <johnthetubaguy> mikal: some of those critical gate bugs are just not likely to get fixed in time, some people were digging
08:04:41 <johnthetubaguy> ttx: yeah
08:04:46 <mikal> Yeah, I feel that critical gate != critical release
08:04:55 <mikal> They're important
08:05:00 <ttx> rigth, so they can stay criotical but not be release blockers
08:05:00 <mikal> Just not important to the release per se
08:05:04 <mikal> Agreed
08:05:20 <ttx> just remove the rc1 tag. If they get fixed, all th better, we'll take them
08:05:28 <johnthetubaguy> mikal: been chasing some nasty xenapi stabiity bugs that would have been embarrassing not to fix myself
08:05:34 <mikal> Heh
08:05:35 <ttx> but if nobody is assigned to them at this point, no point in keeping them in list
08:05:45 <johnthetubaguy> ttx: when are we hoping to tag, before thursday I guess?
08:05:47 <mikal> johnthetubaguy: can you take a pass at untargetting gate bugs which aren't release critical today?
08:06:02 <mikal> I thought we didn't tag until the rc bug list got to zero?
08:06:08 <johnthetubaguy> mikal: yeah, if we want to start drawing up the final list
08:06:09 <ttx> johnthetubaguy: before Tuesday next week.
08:06:19 <ttx> "end of month"
08:06:24 <johnthetubaguy> ttx: gotcha
08:06:38 <ttx> but yeah, at least trying this week would be nice
08:07:02 <johnthetubaguy> mikal: thing is, people were kinda thinking, we just take the criticals as blockers, the rest are just an "aim"
08:07:03 <ttx> mikal, johnthetubaguy: would you say the list contains all the true known blockers at this point ?
08:07:37 <mikal> ttx: all that I am aware of
08:07:42 <johnthetubaguy> ttx: "know" is a bit caveat, but yes I think so (minus security ones)
08:07:44 <mikal> There hasn't been a lot of conversation about it though
08:07:53 <mikal> The thread on -dev was pretty quiet
08:08:00 <mikal> Which surprised me to be honest
08:08:43 <johnthetubaguy> mikal: I think people just lobbed the tags on
08:08:54 <johnthetubaguy> well, target I mean
08:08:54 <mikal> johnthetubaguy: yeah, that's what I figured in the end
08:08:55 <ttx> So yeah, as far as bug list is concerned, I would trim it to assigned bugs only, and those that have some chance to make it before end of month
08:09:08 <johnthetubaguy> ttx: cools, I can do that
08:09:21 <mikal> "Dropping as unassigned" seems like a reasonable comment to leave on them
08:09:27 <mikal> johnthetubaguy: I can do that if you want me to be the bad guy
08:09:28 <ttx> Would be good to get the security fix worked on though
08:09:37 <ttx> since fixing before release is always better than after
08:09:40 <mikal> You're thinking of 1369627?
08:09:46 <ttx> but we shouldn't block on that
08:09:48 <mikal> For the security fix?
08:10:11 <ttx> no. Is 1369627 a security thing?
08:10:12 <johnthetubaguy> mikal: yeah, I don't mind, security stuff I probably just need to find people to work on them
08:10:15 <mikal> Yes, yes it is
08:10:20 <mikal> There's another I haven't noticed yet?
08:10:37 <mikal> We're fixing 1369627 by reverting three patches
08:10:46 <mikal> One done, one approved and in gate, the other needing review
08:10:52 <ttx> mikal: see pm
08:11:03 <mikal> johnthetubaguy: if you could review https://review.openstack.org/#/c/123072/ that would be cool
08:11:21 <ttx> Hmm, you should set "Public security" if it's a security bug
08:11:29 <ttx> otherwise it will never enter the OSSA realm
08:11:53 <ttx> although... it's juno-specific ?
08:11:53 <mikal> Ahhh, I see
08:12:07 <mikal> Yeah, we've never "released" the bad code
08:12:16 <mikal> On the other one, that sounds like something we could ask Vishy to look at
08:12:17 <ttx> so in that case we just need to fix it prerelease
08:12:23 <mikal> He's been playing there in the last couple of weeks
08:12:34 <ttx> no need to get the OSSA team on it, no advisory needed
08:12:40 <mikal> Yeah, I don't know of any CD'ers running rbd, so we should be ok with those guys
08:12:44 <johnthetubaguy> mikal: continuous deployment is a bit odd though
08:12:45 <ttx> as log as we fix it for rc1
08:13:35 <mikal> For the other one I am emailing Vishy now to ask if he can help
08:13:42 <ttx> OK, let's trim that list and start burning all targets down. We'll do another checkpoint on Thursday
08:14:03 <ttx> mikal: did you release a final novaclient ?
08:14:24 <mikal> Yes, I did
08:14:37 <mikal> Oh, can we add johnthetubaguy to whatever group gives him access to the security bugs if we havne't already?
08:14:44 <mikal> That makes sense from his LP wrangling role
08:14:49 <johnthetubaguy> mikal: I have access
08:14:58 <mikal> Oh, cool
08:15:23 <johnthetubaguy> mikal: just ended up focusing more on blueprints really
08:15:31 <mikal> johnthetubaguy: yeah, that's fair
08:15:38 <mikal> Just at the moment it makes sense to get you access if you don't alrady
08:15:42 <mikal> Which you do
08:15:42 <mikal> So ignore me
08:15:54 <johnthetubaguy> lol, no problem
08:16:09 <johnthetubaguy> so the list, I don't mind trying to trim that after the meeting
08:16:16 <ttx> ok, so the client looks fine now
08:16:18 <mikal> That would be cool, thanks
08:16:20 <johnthetubaguy> at least all unassigned ones that seem unlikely to make it
08:16:31 <ttx> questions ?
08:16:47 <mikal> Not a question, but I am unsure if I will make the release meeting
08:16:50 <mikal> I am hoping to
08:17:01 <mikal> But it depends on the school thing which is making me miss the TC meeting ending on time
08:17:04 <johnthetubaguy> what are the summit deadlines again, session wise?
08:17:05 <mikal> So we shall see...
08:17:29 <ttx> mikal: as far as design summit is concerned, you would get 18 scheduled sessions and a full-day of contributors meetup (instead of 27 sessions)
08:17:39 <mikal> ttx: ok
08:18:00 <mikal> johnthetubaguy: I think because we're not using the selection web site for sessions we're a bit more flexible with selection deadlines?
08:18:03 <johnthetubaguy> I guess its all decided post PTL election
08:18:05 <mikal> Or am I confused?
08:18:14 <mikal> Yeah, definitely new PTL territory
08:18:20 <mikal> But we can prime the pump for them, so to speak
08:18:41 <ttx> we just need a schedule 1 or 2 weeks before the thing starts
08:19:00 <johnthetubaguy> cools, that makes sense
08:19:05 <johnthetubaguy> I am just thinking about specs
08:19:06 <ttx> but given it's collaboratively discussed now, that may mean start earlier
08:19:27 <mikal> Well, we already have a brain storming etherpad
08:19:28 <johnthetubaguy> ttx: true, give people time to chime in
08:19:33 <mikal> We just need to start talking about it in meetings more
08:19:43 <mikal> But I think release should take most of our meeting time at the moment
08:19:45 <ttx> mikal: ++
08:19:46 <mikal> For the next week at least
08:19:58 <ttx> until RC1 is done, just talk release and RC bugs
08:20:17 <ttx> after RC1 is done we'll add bugs much more selectively
08:20:20 <mikal> Yeah, let's not confuse people
08:20:21 <ttx> if needed
08:20:28 <mikal> Although we promised to open kilo specs next week
08:20:30 <ttx> so it's easier to switch minds to kilo
08:20:34 <mikal> So I need to remember to not forget that as well
08:20:42 <johnthetubaguy> good good, sounds perfect
08:20:54 <johnthetubaguy> just wanted to make sure we are all on the same page
08:21:02 <mikal> So yeah, I think we're done here?
08:21:04 <mikal> Yeah, I think we are
08:21:06 <mikal> Which is good
08:21:07 <ttx> yes we are
08:21:11 <ttx> ttyl!
08:21:19 <johnthetubaguy> thanks all
08:21:20 <mikal> Cool, well thank for both of your time yet again
11:44:35 <ttx> eglynn: ready when you are
11:44:43 <eglynn-office> ttx: knock, knock :) ... ready when you are
11:44:46 <ttx> #topic Ceilometer
11:44:54 <eglynn-office> #link https://launchpad.net/ceilometer/+milestone/juno-rc1
11:45:14 <eglynn-office> so fair progress in landing bug fixes
11:45:20 <ttx> 6 bugs left, we might be able to tag before end of week?
11:45:28 <eglynn-office> well, there are 2 that I'd like to wait on especially
11:45:35 <eglynn-office> https://bugs.launchpad.net/bugs/1309555
11:45:41 <eglynn-office> https://bugs.launchpad.net/bugs/1357869
11:46:01 <eglynn-office> the first has an incomplete fix proposed, needs more testing and a more complete fix
11:46:02 <ttx> ok, we'll see how it goes
11:46:31 <eglynn-office> for the second, I've a simple config workaround to fall back on but I'm also experimenting with a more complete fix
11:46:38 <ttx> OK... On the client release side you did a 1.0.11
11:46:43 <eglynn-office> OK, so you're preference was EoW for RC1?
11:46:54 <eglynn-office> yep, I cut 1.0.11 on Monday
11:47:09 <eglynn-office> slightly delayed by lag in the gate getting the last couple patches merged
11:47:14 <ttx> My preference is by EoW yes, and before next Tuesday otherwise
11:47:28 <eglynn-office> #link https://pypi.python.org/pypi/python-ceilometerclient/1.0.11
11:47:33 <eglynn-office> OK, got it
11:48:24 <ttx> OK, you seem to be in good shape
11:48:35 <ttx> I'll sync again on Thursday and see if we can do RC1 before eow
11:48:44 <eglynn-office> cool, sounds like a plan :)
11:49:28 <ttx> As far as summit is concerned, you would get 5-6 scheduled sessions, and a full day of contributors meetup
11:49:50 <ttx> (compare to 10 scheduled sessions in ATL)
11:50:56 <eglynn-office> OK, obviously I'd prefer 6 to 5 if possible
11:51:26 <ttx> yeah, my current layout includes 6, but i'm waiting on feedback from some programs
11:51:26 <eglynn-office> I'd like to accomodate the Monasca folks with a design session on the ceilo track if poss
11:51:56 <eglynn-office> (I've been chatting with RolandH about opportunities for collaboration)
11:52:16 <ttx> ok that works
11:52:34 <ttx> anything to discuss at meeting . Any red flag wrt release ?
11:52:46 <eglynn-office> nope, no red falg from me
11:52:52 <eglynn-office> *flags
11:53:37 <ttx> OK then, talk to you later!
11:53:44 <eglynn-office> cool, laters
12:14:10 <ttx> dhellmann: ready when you are
12:14:32 <dhellmann> ttx: here
12:14:35 <ttx> #topic Oslo
12:14:46 <ttx> Are we all set release-wise ?
12:15:09 <dhellmann> yes, we should be set
12:15:18 <ttx> https://launchpad.net/oslo/+milestone/next-juno
12:15:21 <dhellmann> we had one patch release of oslo.db to help stabilize the nova gate, but that's it
12:15:35 <ttx> This should in theory show all FixReleased at some point
12:15:46 <ttx> (if we are indeed done)
12:16:06 <dhellmann> we never ran the script against the incubator. I can update those by hand. The others I'll move to kilo.
12:16:20 <dhellmann> I was holding onto the idea of a pbr release, but I think at this point we should wait for the other releases to finish.
12:16:45 <ttx> dhellmann: for oslo-incubator, maybe rename next-juno to 2014.2
12:16:51 <dhellmann> ok
12:17:10 <ttx> since that's what we tagged
12:17:39 <ttx> A few fixes were merged after that in master and should not get FixReleased, though
12:18:05 <dhellmann> we count master for the incubator as released, since the important tracking is when the merge happens in the apps
12:18:12 <ttx> (bug 1372177)
12:18:13 <dhellmann> at least that's how I've been treating it
12:18:55 <ttx> dhellmann: hmm, but those fixes are post-2014.2 tag
12:19:10 <ttx> so they should not appear FixReleased in 2014.2
12:19:29 <dhellmann> ok, that one isn't targeted to the milestone yet, so I'll put it in a kilo milestone
12:20:09 <ttx> the others were without a bug ref
12:20:21 <dhellmann> ?
12:20:23 <ttx> so that's the only one you could accidentally include
12:20:57 <ttx> dhellmann: let me explain
12:21:23 <ttx> if you run the script that turns FixCommitted bugs into FixReleased, you need to do it when you tag, otherwise you may catch bugs that were fixed after the tag ifs applied
12:21:40 <ttx> here I just checked the merges that happened after the tag to make sure we don't accidentally indlude them in 2104.2
12:21:58 <dhellmann> oh, yeah, I was going to just update all of those bugs by hand to avoid that
12:21:59 <ttx> There are 3 of them
12:22:20 <ttx> well, actually, 4
12:22:37 <ttx> https://review.openstack.org/#/c/122377/ references no bug
12:22:54 <ttx> https://review.openstack.org/#/c/123017/ references 1372177
12:23:19 <ttx> https://review.openstack.org/#/c/115213/ references no bug
12:23:33 * dhellmann nods
12:24:07 <ttx> https://review.openstack.org/#/c/121305/ references related bug 1368910
12:24:29 <ttx> anyway, just me and my damn accuracy :)
12:24:38 <dhellmann> I will make sure those bugs are targeted with kilo
12:24:43 <dhellmann> s/with/to
12:25:12 <dhellmann> I guess if I do that, I can use the script to update the bug settings instead of doing it by hand
12:25:32 <ttx> so, on https://launchpad.net/oslo/+milestone/next-juno there are still oslo.concurrency PBR taskflow and oslo.vmware things
12:26:02 <ttx> Are those all still waiting for a tag ?
12:26:16 <dhellmann> oh, we didn't do a final release of those, that should all move to kilo, too
12:26:30 <dhellmann> I'll spend the morning cleaning this up. I should have looked at it yesterday.
12:26:35 <ttx> we won't do a final release of those ?
12:26:57 <dhellmann> wait, hang on, we did a release of concurrency
12:27:20 <dhellmann> oh, no, that's serialization -- I keep mixing those up
12:27:30 <ttx> ETOOMANYLIBS
12:27:40 <dhellmann> no, we had a few libs that were not quite ready and weren't going to be adopted, so we focused on fixing up the ones in use
12:27:45 <dhellmann> I will move all of the unfinished work to kilo
12:27:52 <ttx> dhellmann: OK, so once you are done with the juno cleanup let me know, i'll doublecheck and we can close Juno for good
12:27:55 <dhellmann> yeah, seriously, we're up to something like 19 or 20 now
12:28:02 <dhellmann> ok, sounds good
12:29:07 <ttx> dhellmann: as far as design summit is concerned... I think we can preserve ~7 oslo scheduled slots
12:29:21 <ttx> (down from 11 in ATL)
12:29:29 <dhellmann> we should be able to make that work, esp. if we have pod space on friday
12:29:30 <ttx> You would get a dedicated "pod" on the Friday
12:29:38 <dhellmann> reading my mind :-)
12:29:47 <ttx> and we can also discuss major issues on the cross-project day, if any
12:30:34 <dhellmann> I don't want oslo to be seen as the driver for those things. We may have one or two, but I want the TC to really run those as "all of openstack" rather than funnelling them through oslo
12:30:50 <ttx> oh sure, that's what I meant
12:31:08 <dhellmann> ok
12:31:31 <ttx> any release red flag on your side ?
12:32:29 <ttx> anything to discuss at cross-project meeting today ?
12:32:31 <dhellmann> I haven't heard anything. We looked into that keystoneclient issue on the stable branches, but it's going to have to be fixed in their client.
12:32:49 <dhellmann> nothing this time around, I think
12:33:09 <dhellmann> well, I need to figure out the timing to remind everyone to prioritize adoption of libraries early in kilo
12:33:10 <ttx> dhellmann: ok, great!
12:33:24 <dhellmann> they're probably not thinking about that yet, but I don't know if we'll have project meetings after the release is actually done?
12:33:33 <ttx> dhellmann: if you have some time, you can help sdague and myself go through the requirements review
12:33:45 <dhellmann> yeah, I was going to ask if there's anything you need help with
12:33:53 <ttx> the more the merrier
12:33:58 <dhellmann> aren't we locked down for requirements changes?
12:34:10 <ttx> dhellmann: yes, that's why I'd like to clean up the slack there
12:34:18 <dhellmann> oh, so -2 things?
12:34:23 <ttx> -2 what can be, abandon some
12:34:26 <dhellmann> ok
12:34:38 <ttx> and discuss at release meeting today what still needs a final call
12:34:56 <ttx> I triued to come up with a list for that and got confused by some
12:35:01 <dhellmann> ok, I'll look at that after I clean up our bug tracker
12:35:34 <ttx> ok, you will be able to find us on #openstack-dev
12:35:51 <dhellmann> ok
14:00:21 <ttx> jgriffith: ready when you are
14:06:36 <jgriffith> ttx: ready
14:06:42 <ttx> #topic Cinder
14:06:50 <ttx> https://launchpad.net/cinder/+milestone/juno-rc1
14:07:03 <ttx> Your curve is one of the few going down at http://old-wiki.openstack.org/rc/
14:07:13 <ttx> so you seem on a good trend
14:07:22 <jgriffith> cool!
14:07:44 <ttx> There is one unassigned security issue though that we should at least try to get in the release rather than after
14:07:54 <ttx> (it's the one unassigned bug in the list)
14:08:06 <ttx> you might want to privately get it assigned
14:08:09 <jgriffith> ttx: ahh
14:08:17 <jgriffith> yeah, there's a patch proposed
14:08:24 <jgriffith> I can mark it assigned
14:08:39 <ttx> You did release a client last week (1.1.0) and the global requirements bump is gating
14:08:51 <ttx> so we are covered on that side
14:09:11 <jgriffith> Yeah, I'll do one more client bump after RC cut
14:09:12 <ttx> When do you think you can empty the list ? Sometimes this week ?
14:09:20 <jgriffith> I think this week yes
14:09:26 <jgriffith> most are in progress and doing "ok"
14:09:30 <ttx> jgriffith: one more client bump after RC cut ?
14:09:41 <ttx> We wanted to freeze the clients.. last Friday
14:09:43 <jgriffith> I'd like to if it doesn't make people freak out
14:09:48 <jgriffith> ahh...
14:09:52 <jgriffith> hmm...
14:09:54 <ttx> so unless you have some critical issue
14:09:59 <jgriffith> so I have one issue
14:10:11 <jgriffith> debug output was broken by all the i8n shenanigans
14:10:24 <jgriffith> patch is on it's way through right now to fix
14:10:32 <jgriffith> kinda of a big deal IMO
14:11:00 <ttx> OK, I think it's fine to tag a new one, but maybe not bump the global requirements
14:11:11 <jgriffith> ttx: oh.. for sure
14:11:13 <ttx> just make sure everyone knows about it when you cut it
14:11:17 <jgriffith> I'll avoid that at all costs
14:11:31 <jgriffith> I will... in fact I'll send a note to dev today warning them if that helps
14:11:50 <ttx> do you have a bug reference for that issue ?
14:11:55 <jgriffith> I do....
14:12:25 <jgriffith> https://bugs.launchpad.net/python-cinderclient/+bug/1130730
14:12:27 <jgriffith> and it landed
14:12:38 <jgriffith> so I'll push today and send an email to everyone
14:12:38 <ttx> #info New Cinder client expected soon (1.1.1 ?) to fix bug 1130730
14:12:47 <ttx> ok
14:13:03 <ttx> Any red flag release-wise ? Anything you'd like to discuss at meeting today ?
14:13:16 <jgriffith> No red flags (as of yet)
14:13:29 <jgriffith> and no, nothing I need to bring up at meeting
14:13:52 <ttx> jgriffith: as far as summit goes, i'm still working on allocation but you should get 6-7 scheduled slots
14:13:59 <ttx> + the half-day meetup
14:14:13 <ttx> in case there is room for it, would you be interested in a full-day thing ?
14:14:32 <jgriffith> ttx: always, but honestly I wouldn't rank us high priority for it
14:14:46 <jgriffith> ttx: and I'd rather see more cross-project interaction from Cinder team
14:15:00 <jgriffith> ttx: I'm realizing more and more that a lot of folks are really silo'd
14:15:07 <jgriffith> would like to prompt some change there
14:15:21 <ttx> ok.
14:15:41 <jgriffith> Keep in mind I'm going to propose being very picky about session topics this time around
14:15:51 <jgriffith> assuming my successor follows that plan
14:16:28 <ttx> ok, talk to you later then! Hope we can cut RC1 later this week
14:16:35 <jgriffith> sounds good
14:16:42 <ttx> morganfainberg: ready when you are
14:16:43 <jgriffith> I'll let you know if I think it's ready before Friday
14:17:01 <morganfainberg> ttx, o/
14:17:24 <ttx> #topic Keystone
14:17:35 <ttx> https://launchpad.net/keystone/+milestone/juno-rc1
14:17:47 <ttx> 2 bugs left, looks like we should be able to cut this week
14:18:00 <morganfainberg> ttx, those are both addressed by the same fix, should gate today
14:18:13 <ttx> OK, so I might be in touch soon :)
14:18:25 <morganfainberg> ttx, in fact, working with another core to get that reviewed right now as well :)
14:18:39 <ttx> morganfainberg: on another note, we might want a keystonemiddleware tag to catch the latest security issue in a release
14:18:55 <ttx> before we issue an advisory for it
14:18:57 <morganfainberg> ttx, Keystone client is also ready for 0.11.1 release fixing the bug in config
14:19:29 <ttx> which bug ?
14:19:39 <morganfainberg> ttx, keystonemiddleware is planned to get a new tag/release as soon as https://gist.github.com/dolph/651c6a1748f69637abd0 those 4 reviews merge.
14:20:01 <morganfainberg> ttx, https://launchpad.net/python-keystoneclient/+milestone/0.11.1
14:20:14 <morganfainberg> the glance exploding one, #1272422
14:20:14 <ttx> ah ok
14:20:18 <morganfainberg> erm 1372422
14:20:45 <morganfainberg> i will either need to have you push the tag or wait for dolphm today.
14:20:51 <ttx> ok
14:20:52 <morganfainberg> i do not have permission to push tags.
14:21:07 <ttx> ping me as needed
14:21:19 <ttx> any other thing release-wise ?
14:21:35 <morganfainberg> ttx, anytime today would be good to get 0.11.1 out.
14:21:58 <morganfainberg> ttx, no i think that is it. looking forward to getting Keystone tagged (hopefully minimal gate fighting for that last blocker)
14:22:10 <ttx> As far as summit goes, still working on allocation, but keystone could get 6-7 scheduled slots + a half-day meetup
14:22:26 <morganfainberg> ttx, that sounds about the same as last time, and fair.
14:22:28 <ttx> (compared to 8 scheduled slotsin ATL)
14:22:40 <morganfainberg> ttx, right, the 1/2 day covers the extra.
14:22:54 <ttx> morganfainberg: that's all I had
14:23:21 <morganfainberg> ttx, cool. sounds good and i'll def. ping you as soon as we have the middleware reviews ready. My goal is for all of them to be done today / tomorrow morning
14:23:46 <morganfainberg> ttx, i expect it's just going to be gate rechecks to get things through
14:24:03 <morganfainberg> ttx, same with keystone.
14:24:10 <ttx> ok, I'll be a bit busy today so I may not be able to get back to you wrt: python-keystoneclient tag.
14:24:20 <ttx> If still needed by tomorrow, I should be much more available then
14:24:43 <ttx> david-lyle: ready when you are
14:24:49 <ttx> morganfainberg: thx!
14:25:03 <morganfainberg> ttx, i'll ping dolphm if i see him.
14:25:04 <david-lyle> ttx: ready
14:25:10 <ttx> #topic Horizon
14:25:11 <morganfainberg> ttx, if not, will bug you tomorrow :)
14:25:21 <ttx> https://launchpad.net/horizon/+milestone/juno-rc1
14:25:40 <ttx> So... 44 opened RC1 bugs is way too much
14:26:02 <david-lyle> yes, getting ready to prune that down
14:26:07 <ttx> you need to cut down the list to release blcokers only. If anything else gets in in the mean time, taht's fine
14:26:32 <ttx> but there is no way those 44 will get in and we still hit the release date :)
14:26:55 <david-lyle> I think the list is actually about 4 for release blocking
14:27:20 <david-lyle> at least that's what I've been tracking
14:27:21 <ttx> Ideally we'd cut RC1 before end of week, worst case before end of month
14:27:45 <david-lyle> my target was end of the week, unless something else comes up
14:27:45 <ttx> ok, you can use a tag to track the nice-to-have
14:27:54 <david-lyle> sure
14:28:18 <ttx> we'll discuss the last depfreeze exceptions at the meeting today
14:28:25 <david-lyle> ok
14:28:26 <ttx> so that we can make the final call on them
14:28:59 <ttx> any red flag wrt: release ? Or topic for the meeting today ?
14:29:38 <david-lyle> no
14:29:56 <ttx> As far as design summit goes, my initial allocation gives horizon 6 slots + the half-day of meetup
14:30:12 <david-lyle> that sounds reasonable
14:30:17 <ttx> in case there is room for it, could you be interested in a full day ?
14:31:10 <david-lyle> I'm not sure we'll need a whole day if there is pod space available
14:31:26 <ttx> ok.
14:31:54 <ttx> david-lyle: that's all I had. Anything else ?
14:32:16 <david-lyle> if no other teams speak up we do have some architecture work I'd like to get done there, but I think the number of participants may not warrant a whole room
14:32:57 <david-lyle> want to make sure my recollection is correct, once RC1 is closed, master is Kilo
14:33:06 <david-lyle> correct?
14:33:44 <ttx> yes
14:33:55 <david-lyle> also a heads up, due to translations, we'll likely have an RC2 just for that, barring other issues
14:34:45 <david-lyle> I think the translation team is targeting end of month
14:35:59 <david-lyle> that's all I have
14:36:10 <ttx> david-lyle: it would be good to merge relatively-recent translations for RC1 anyway
14:36:12 <ttx> but i agree
14:36:31 <ttx> mestery: ready when you are, but you seem to have a conflict :)
14:36:48 <mestery> ttx: Sorry, yes, in a neutron meeting. Can we push this a bit for today? Apologies.
14:36:54 <ttx> sure
14:37:13 <mestery> ttx: OK, I'll ping you if this gets done early.
14:37:31 <david-lyle> ttx: they're automatic now, we merge as available
14:37:33 <david-lyle> thanks
15:01:04 <mestery> ttx: Here if you're around.
15:01:13 <ttx> mestery: on a call
15:01:22 <mestery> ttx: OK. Any ETA?
15:01:31 <mestery> I may jump into a 15 minutes call myself if you'll be at least that long.
15:01:48 <ttx> at least 15 min yes
15:01:51 <mestery> OK
15:29:31 <ttx> notmyname: around?
15:30:04 <ttx> mestery: you can go now if you want
15:32:12 <mestery> ttx: ack
15:32:15 <ttx> #topic Neutron
15:32:21 <ttx> https://launchpad.net/neutron/+milestone/juno-rc1
15:32:34 <ttx> 33 targeted bugs, at this point it's too much
15:32:43 <ttx> you need to reduce to true release blockers
15:32:44 <mestery> ttx: I agree.
15:32:51 <ttx> so that we can hit RC1 sometimes before the end of the month
15:32:52 <mestery> Yes, I spent some time in the meeting talking about that.
15:33:03 <mestery> I'll have this list culled down by tomorrow.
15:33:19 <ttx> great
15:33:30 <mestery> When will you cut RC1?
15:33:34 <mestery> Is it this week?
15:36:57 <mestery> ttx: There?
15:37:53 <ttx> sorry just a sec
15:37:59 <mestery> ttx: ack
15:39:42 <notmyname> I'm here (on my phone)
15:40:00 <mestery> ttx: Apologies, I need to take off now.
15:40:14 <ttx> mestery: ok
15:40:22 <mestery> ttx: I will get the RC1 page under control, and I have nothing specific for today's cross-project meeting other than to go over the Kilo schedule if people want to.
15:40:25 <mestery> ttx: Thanks!
15:40:55 <ttx> sorry got interrupted
15:41:07 <ttx> mestery: will talk to you again later
15:41:18 <ttx> #topic Swift
15:41:30 <ttx> notmyname: how is your next release coming up ?
15:41:48 <notmyname> Overall good.
15:42:04 <notmyname> Probably won't land everything I want, but the important stuff will
15:42:21 <ttx> notmyname: what would be the updated ETA ?
15:42:42 <notmyname> We're still on track for next week. I'll work closely with you for the RC
15:42:54 <ttx> notmyname: ok, I'll be around
15:43:05 <notmyname> I have 2 other things
15:43:11 <ttx> do you need to cut another swiftclient ?
15:43:22 <notmyname> First, we found a regression in the last swiftclient
15:43:23 <notmyname> Yes
15:43:45 <notmyname> The last one we thought was good but into'd a keystone v3 reg
15:43:49 <ttx> ok, the sooner the better, especially if you want to bump the global-requirements
15:43:58 <notmyname> Will cut a minor point release later this week
15:44:11 <notmyname> No requirements changes
15:44:12 <ttx> ok
15:44:37 <notmyname> Second, next week we have a kid cycle meetup thing in Boston
15:44:38 <ttx> #info new swiftclient expected later this week to fix a regression
15:44:56 <ttx> kid cycle?
15:45:12 <notmyname> Mid. Phone autocorrect
15:45:18 <ttx> kilo maybe
15:45:58 <notmyname> We'll be looking at ec work and summit prep and etc
15:46:47 <ttx> ok
15:47:20 <ttx> Still working on allocation, but looks like you would get 6 scheduled slots + half-day meetup
15:47:26 <ttx> compared to 8 slots in ATL
15:47:32 <ttx> so more time overall
15:47:46 <ttx> but less cheduled ones (like everyone else)
15:47:49 <notmyname> Ok. I'll be starting the communal scheduling this week
15:48:00 <notmyname> Sounds good
15:48:22 <ttx> notmyname: ok, anything els e?
15:48:37 <ttx> zaneb: around?
15:48:44 <notmyname> No. I'm good
15:48:44 <zaneb> o/
15:48:46 <notmyname> Thanks
15:48:50 <ttx> notmyname: thx!
15:50:06 <ttx> #topic Heat
15:50:16 <ttx> https://launchpad.net/heat/+milestone/juno-rc1
15:50:40 <zaneb> we got the FFEs in :)
15:50:41 <ttx> 14 targeted bugs left
15:50:46 <ttx> zaneb: yep:)
15:51:19 <ttx> are all those release vlockers ? Or could you refine the list so that only RC things are left in it ?
15:51:23 <ttx> blockers*
15:51:38 <ttx> I'd like to hit RC1 before the end of the month if possible
15:52:00 <zaneb> yeah, I definitely don't think all of those are release blockers
15:52:18 <zaneb> I think that's probably feasible
15:52:24 <ttx> you can use a tag for nice-to-have if you want to track them
15:52:39 <ttx> I'd like to make sure we are burning down release-critical ones at an acceptable rate
15:53:08 <zaneb> I think the High priority ones are the most release-critical
15:53:22 <ttx> So I'll be in touch later this week to see how far we are from RC1
15:53:24 <zaneb> fortunately we don't have a large number of those
15:53:37 <zaneb> ok
15:53:43 <ttx> You did cut a 0.2.11 heatclient
15:53:50 * zaneb needs to find time to scrub the whole bug list anyway
15:53:55 <zaneb> yes we did
15:53:59 <ttx> and I had a question for you about https://review.openstack.org/#/c/122520/
15:54:08 <ttx> is that bump *required* ?
15:54:16 <ttx> i.eL. does it fix some release-critical bug somewhere ?
15:54:31 <ttx> we shouldn't bump the floor unless it's required
15:54:42 <zaneb> not sure about that
15:54:49 <zaneb> I will check with stevebaker
15:55:00 <ttx> well, the review is -1ed until you do find a good reason why we should bump in those troubled times
15:55:10 <zaneb> fair enough :)
15:55:16 <ttx> and we'll discuss it again at the release meeting tonight
15:55:37 <zaneb> ok
15:56:09 <ttx> Last thing I had is the provisional slot allocation for summit. Looks like you could get 7 scheduled sessions and a full day of meetup
15:56:27 <ttx> (compared to 8 slots in ATL)
15:56:38 <zaneb> that sounds really good
15:56:55 <ttx> you get a lot because your allocation was a bit behind compared to your activity
15:57:17 <zaneb> yeah, it's surprisingly busy around here ;)
15:57:32 <ttx> (you are more active than Cinder but had 3 less slots)
15:58:03 <zaneb> I'm particularly looking forward to the day of meetup
15:58:45 <ttx> anything you'd like to flag release-wise ? Any topic for the meeting today ?
15:59:06 <zaneb> nope, can't think of anything
15:59:12 <ttx> ok great, talk to you later
15:59:22 <ttx> SergeyLukjanov, mestery: you can go now if you're around
15:59:33 <zaneb> thanks ttx
16:04:30 <ttx> SlickNik: ready when you are
16:04:44 <ttx> or markwash__ can beat you
16:04:52 <ttx> since 6pm is his slot
16:05:01 <SlickNik> o/
16:05:08 <ttx> going once
16:05:17 <ttx> markwash__: going twice
16:05:25 <ttx> #topic Trove
16:05:39 <ttx> https://launchpad.net/trove/+milestone/juno-rc1
16:06:32 <ttx> 33 bugs left targeted
16:06:33 <SlickNik> Looked at all the bugs we have, and spent some time triaging the criticals into Juno, and the rest out.
16:07:05 <ttx> 33 is still way to much, I bet all those are not release blockers
16:07:29 <ttx> any chance you could refine that list so that it only contains release blockers ?
16:07:33 <SlickNik> Agreed — not all of them are.
16:07:43 <ttx> and use a tag for the nice-to-fix-in-Juno ?
16:07:57 <ttx> taht way we can trigger a RC1 when we are done with the release blockers
16:08:09 <ttx> ideally this week, or early in the next
16:08:20 <SlickNik> Will do that this week.
16:08:31 <SlickNik> btw, didn't know Launchpad did tags.
16:08:35 <ttx> ok, I'll be in touch later this week to see if we can push a tag
16:09:04 <ttx> so if you could cull the list before then, that would be awesome
16:09:35 <ttx> Do you need to cut another troveclient release before Juno release ?
16:09:36 <SlickNik> I'll plan on spending some time to do that today.
16:09:46 <ttx> or is 1.0.7 good enough
16:10:14 <ttx> If you do, the deadline for that was last Friday, unless you got some regression in :)
16:10:14 <SlickNik> 1.0.7 is good enough — it's pretty recent (I think a week and a half ago)
16:10:18 <ttx> ack
16:10:33 <SlickNik> It has all the juno-3 feature bps done.
16:10:38 <ttx> That's all I had release-wise. Any red flag you'd like to communicate ?
16:10:47 <ttx> any topic for the meeting later ?
16:11:06 <SlickNik> Sad that we couldn't get the juno-3 functionality into horizon though. :(
16:11:22 <ttx> can't get everything
16:11:34 <SlickNik> Yup, understand.
16:11:40 <SlickNik> And it'll come in Kilo
16:11:41 <SlickNik> :)
16:11:53 <ttx> As far as design summit is concerned, looks like you could get 4 scheduled slots and a half-day meetup (compared to 6 scheduled slots in ATL)
16:12:06 <ttx> so slight more time oevrall, but less scheduled slots (like everyone)
16:13:20 <ttx> SlickNik: anything else ?
16:13:33 <SlickNik> Cool, are you planning on drawing up a tentative schedule for the slots and posting it on the wiki like you did last time?
16:13:41 <SlickNik> That was very helpful.
16:13:57 <ttx> SlickNik: yes, waiting on some feedback before I can do that
16:14:18 <SlickNik> Okay, sounds good.
16:14:20 <ttx> TripleO needs to tell me if they eed scheduled slots or if they would rather have a full-day meetup instead
16:14:24 <ttx> need*
16:14:38 <SlickNik> That's all I had. Thank you ttx!
16:14:43 <ttx> SlickNik: ok then, ttyl
16:14:44 <ttx> markwash__: around?
16:14:50 <markwash__> ttx hi there
16:14:55 <ttx> #topic Glance
16:15:19 <ttx> https://blueprints.launchpad.net/glance/+spec/refactoring-glance-logging is still open
16:15:23 <ttx> or appears to be
16:15:32 <ttx> It's time to close all FFEs I'm afraid
16:15:39 <ttx> time well passe
16:15:41 <ttx> dd
16:15:52 <ttx> what was there left ?
16:16:13 <markwash__> just https://review.openstack.org/#/c/116626/8
16:16:22 <markwash__> which looks fine to land, unless you think its too too late
16:16:48 <ttx> let me look at it
16:16:56 <ttx> no need for https://review.openstack.org/#/c/117204/ ?
16:17:32 <ttx> markwash__: 116626 is only log info level changes ?
16:17:56 <markwash__> ttx, actually sorry I spoke a little too soon
16:18:01 <markwash__> I guess we should just defer
16:18:19 <ttx> OK, I'll let you -2 the remaining reviews
16:18:24 <ttx> kilo opens in a few days now
16:18:45 <ttx> I'll mark the BP deferred
16:18:59 <markwash__> thanks
16:19:28 <ttx> OK, so I see no release blocker on that page
16:19:45 <markwash__> I'm a little scared
16:19:52 <markwash__> but its accurate TMK
16:19:53 <ttx> does that mean you're ready for RC1 tag, or that you didn't go through all the bugs to spot RC ones yet ?
16:20:03 <ttx> hmm, ok
16:20:40 <ttx> markwash__: maybe do a last pass on those and if still none, we could tag tomorrow or Thursday
16:20:50 <markwash__> will do
16:20:54 <ttx> https://bugs.launchpad.net/glance/+bug/1366515 could be added, maybe
16:21:21 <ttx> with maybe https://review.openstack.org/#/c/119613/
16:21:32 <ttx> (https://bugs.launchpad.net/glance/+bug/1366503)
16:22:25 <ttx> OK... anything else release-related ?
16:22:53 <markwash__> not from me
16:23:07 <ttx> Looking at design summit, Glance would get 4 scheduled sessions and a half-day meetup (compared to 5 scheduled sessions in ATL)
16:23:43 <ttx> markwash__: do we have candidates for Glance PTL position already ?
16:24:00 <markwash__> ttx: I was just taking a look at that, and so far no
16:25:09 <markwash__> I imagine 4 sessions and the meetup will be sufficient
16:25:16 <ttx> markwash__: ok
16:25:21 <markwash__> based on the past sessions
16:25:42 <ttx> markwash__: talk to you later then !
16:25:51 <markwash__> sayonara
16:26:02 <ttx> mestery, SergeyLukjanov: time now for one more
16:26:08 <ttx> first come first served
16:27:40 <SergeyLukjanov> ttx, hey
16:27:50 <ttx> #topic Sahara
16:27:54 <SergeyLukjanov> ttx, if you're able
16:28:04 <SergeyLukjanov> #link https://launchpad.net/sahara/+milestone/juno-rc1
16:28:14 <ttx> So we need to close all remaining FFEs now
16:28:19 <ttx> time has passed
16:28:35 <ttx> If I remeber correctly those were technical FFEs though
16:28:49 <SergeyLukjanov> heh, I forget to update statuses
16:28:49 <ttx> i.e. one was actually done but you kept it open to track -extra work
16:28:53 <SergeyLukjanov> both are implemented
16:28:55 <ttx> and the other was doc
16:28:57 <ttx> ok
16:29:14 <ttx> 11 bugs on the RC list
16:29:26 <ttx> would be good to refine to releae blockers
16:29:35 <ttx> I suspect the "undecided" unassigned one isn't
16:29:42 <SergeyLukjanov> ttx, most of the are doc ones
16:30:33 <ttx> s othose are more nice-to-have than release blockers, right ?
16:31:46 <ttx> maybe use a tag to track doc nice-to-haves for Juno release
16:31:51 <ttx> and keep the list for true release blockers
16:32:01 <ttx> so that we know how far we are
16:32:14 <ttx> ideally we would tag thiws week, or before Tuesday next week
16:32:30 <SergeyLukjanov> I think we're able to have a tag later this week
16:32:43 <SergeyLukjanov> we have only several blockers
16:33:09 <ttx> do you need to tag a client release to catch up with final oslo versions ?
16:33:11 <SergeyLukjanov> I will cleanup the list and share you the list of blockers
16:33:17 <SergeyLukjanov> ttx, yup
16:33:24 <ttx> ok, would be good to do it asap
16:33:29 <SergeyLukjanov> ttx, it'll be with only one change - oslo versions update
16:33:33 <SergeyLukjanov> I will do it today
16:33:33 <ttx> right
16:33:51 <SergeyLukjanov> do we need to bump version in global req?
16:33:52 <ttx> that's all I had releasewise
16:33:56 <ttx> SergeyLukjanov: no
16:34:00 <SergeyLukjanov> ttx, ack
16:34:07 <ttx> not unless that fixes a critical bug somewhere
16:34:18 <SergeyLukjanov> ok
16:34:52 <ttx> Looking at the design summit, Sahara would get 5 scheduled sessions and a half-day meetup (compared to 7 sessions in ATL)
16:34:57 <SergeyLukjanov> so, action items on me - release sahara client w/ updated oslo libs and cleanup list of issues that are blockers for release, mark doc issues with tag
16:35:01 <ttx> so more time overall, but less scheduled slots.
16:35:09 <SergeyLukjanov> ttx, that's great
16:35:34 <SergeyLukjanov> ttx, meetup time will make us able to discuss internalls much better than always
16:35:52 <ttx> agree on actions. I'll be in touch for a potential RC1 tag later this week if you make good progress
16:36:07 <ttx> anything for meeting tonight ?
16:36:42 <SergeyLukjanov> note: we have several sahara-related fixes in horizon still on review
16:36:56 <SergeyLukjanov> but it's not a topic for meeting I think
16:37:13 <SergeyLukjanov> so, I think nothing more from my side
16:37:14 <ttx> maybe just make sure they stay on their RC1 list
16:37:17 <ttx> ok, ttyl
16:37:21 <SergeyLukjanov> thank you
16:37:40 <ttx> mestery: i'll ping you around 19:30 UTC for more sync
16:37:47 * ttx takes a break
18:31:24 <dhellmann> ttx: I've cleaned up all of the oslo next-juno milestones (renamed the one for oslo-incubator and closed all of the others). The juno series is still open for all and I don't know how to close that, but if you let me know I can do it.
18:43:48 <sdague> ttx: the requirements readme from this morning is updated - https://review.openstack.org/#/c/116708/
18:56:19 <SergeyLukjanov> ttx, sahara client w/ fresh req just released
19:08:12 <mestery> ttx: I'll be here, thanks!
19:35:36 <ttx> mestery: around?
19:35:45 <mestery> ttx: o/
19:35:51 <ttx> #topic Neutron
19:36:14 <ttx> so you asked, when is RC1
19:36:19 <ttx> ideally some time this week
19:36:26 <ttx> if not, early next week
19:36:40 <mestery> OK, makse sense
19:36:52 <ttx> so the goal is to cut down the buglist so that it only contains release blockers
19:37:19 <mestery> Yes, I've been working on that
19:37:40 <mestery> I should have it under control by tomorrow
19:37:46 <mestery> Or even toinight
19:38:02 <ttx> You're fine with 2.3.9 as client release ?
19:38:22 <mestery> Yes, unless someone tells me otherwise
19:38:36 <ttx> ok, anything else about release ?
19:38:43 <ttx> I'll be in touch later this week to see if we can tag
19:39:04 <mestery> Nothing at this time nope
19:39:06 <mestery> Thanks ttx!
19:39:24 <ttx> OK, summit-wise, Neutron will get a full day of meetup + 9-11 scheduled sessions
19:39:49 <ttx> so you can start planning
19:39:50 <mestery> OK, that sounds about perfect
19:39:54 <mestery> We are doing that on an etherpad
19:40:07 <ttx> ok great
19:40:08 <mestery> https://etherpad.openstack.org/p/kilo-neutron-summit-topics
19:40:21 <ttx> mestery: anything else ?
19:40:27 <mestery> ttx: That's it, thanks!
19:40:29 <ttx> alright then.
19:40:30 <ttx> #endmeeting