21:24:51 <ttx> #startmeeting ptl_sync
21:24:51 <openstack> Meeting started Tue Sep  9 21:24:51 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:24:52 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:24:55 <ttx> #topic Nova
21:24:55 <openstack> The meeting name has been set to 'ptl_sync'
21:24:58 <ttx> https://launchpad.net/nova/+milestone/juno-rc1
21:25:31 <ttx> is that list complete with all approvals?
21:25:59 <mikal> I beleive so
21:26:06 <mikal> I ahven't checked in the last 24 hours, but it was before
21:26:19 <mikal> It should also be mostly accurate for implementation status too
21:26:24 <ttx> and you set a deadline for those last Friday, so new ones should be ignored anyway
21:26:40 <ttx> still on track to close them all by Friday?
21:26:40 <mikal> Yep
21:26:44 <mikal> Its hard to tell
21:26:47 <mikal> The gate is painful
21:26:53 <mikal> I can see two which need more dev work
21:26:57 <mikal> And the rest need the gate to agree
21:27:06 <mikal> https://etherpad.openstack.org/p/juno-nova-approved-ffes is our summary of review state
21:27:18 <mikal> So, looking at that
21:27:25 <mikal> virt-driver-name-placement is at risk
21:27:30 <ttx> mikal: if they are gating now and don't get in by Friday I'm fine with giving them extra time :)
21:27:32 <mikal> As is server-group-quotas
21:27:41 <mikal> And SRIOV
21:27:51 <mikal> ttx: yeah, I figured we'd sneak them in
21:27:57 <ttx> OK, if you see that they are not getting in in time, defer them early rather than late
21:28:17 <mikal> Sounds sensible
21:28:25 <ttx> i.e. if they are not approved by Thursday... or gating by Friday...
21:28:27 <mikal> It is probably a good idea for me to email -dev and remind people to be focussing on these
21:28:32 <ttx> probably simpler to just defer them
21:28:56 <ttx> because otherwise they will still be in progress by mid next-week
21:29:12 <mikal> Agreed
21:29:15 <ttx> especially if some of those are patchseries
21:29:25 <ttx> those can take a long time
21:29:36 <mikal> Yeah, gating is painful for those
21:30:01 <ttx> So, we'll see how it goes at the end of the week
21:30:12 <ttx> quick discussion on design summit
21:30:14 <mikal> There is also one important bug on my radar as I mentioned in email
21:30:19 <mikal> The ironic driver as landed does not work
21:30:23 <mikal> There is already a fix out for review
21:30:31 <ttx> oh, ok
21:30:38 <mikal> https://review.openstack.org/#/c/119944/
21:30:48 <mikal> Ahhh, it got approved while I slept
21:30:50 <mikal> In the gate now
21:30:56 <ttx> I think you'll want a full day of meetup on the Friday
21:31:18 <mikal> Sorry, at the summit you mean?
21:31:20 <ttx> yes
21:31:28 <mikal> So, there are four summit days, yes?
21:31:36 <ttx> on the Tuesday you have cross-project stuff
21:31:45 <ttx> that leaves Wed/Thu
21:32:01 <mikal> How does that compare with Atlanta, its the same number of slots right?
21:32:05 <ttx> where my original plan was to give you two full days of scheduled slots
21:32:09 <ttx> yes
21:32:16 <mikal> Ahhh, two days not three?
21:32:30 <ttx> well, the third is replaced by the meetup, so same time together
21:32:39 <mikal> Holdup
21:32:40 <mikal> I'm confused now
21:32:43 <mikal> What is the meetup?
21:32:53 <ttx> ok, /me rewinds
21:33:11 <ttx> on the wed/Thu we'll have traditional slots
21:33:16 <mikal> Ok
21:33:27 <ttx> i.e. 40-min, with a predetermiend theme and present on schedule
21:33:48 <ttx> on the Friday, all teams will have a half-day or a full-day "contributors meetup"
21:34:04 <ttx> that's a big block of time that they can organize how they see fit
21:34:16 <ttx> usually with an etherpad full of themes to discuss
21:34:22 <ttx> midcycle-meetup style
21:34:33 <ttx> no "slots", no 40-min bell
21:34:40 <mikal> Ahhh, cool
21:34:40 <mikal> Ok
21:34:45 <mikal> In that case I've changed my mind
21:34:53 <mikal> And I want all the slots I can get on the two non-meetup days
21:34:59 <ttx> ok
21:35:07 <mikal> If we didn't have the meetup I'd want to spread them out over the three days
21:35:14 <mikal> But that doesn't sound like an option here
21:35:16 <ttx> Ideally you would use the Friday to get alignment on a Kilo plan
21:35:52 <ttx> and solve "team problems"
21:36:04 <mikal> I think that's a good idea
21:36:09 <ttx> but it's really up to you, and can change at last minute
21:36:09 <mikal> I just somehow missed that it was the plan
21:36:31 <ttx> let's say it was just a thought, but I talked with our event partner and it may actually be possible
21:36:41 <ttx> we'll need to revamp the space between Thursday and Friday
21:36:49 <mikal> Ahhh yeah
21:36:56 <mikal> Tables and stuff instead of just 200 chairs
21:37:01 <mikal> Fair enough
21:37:02 <ttx> so that there are a lot of parallel spaces, and tables
21:37:20 <ttx> we might have LCDs to be able to show up stuff
21:37:38 <ttx> rather than prjector/screen combos
21:37:45 <mikal> And whiteboards?
21:37:49 <mikal> Whiteboards would be good
21:38:04 <ttx> actually the paperboards double as whiteboards. I asked that we have several of them
21:38:19 <ttx> so you could in theory build a large whiteboard
21:38:27 <mikal> LOLK
21:38:29 <mikal> Ok
21:38:52 <ttx> apparently large whiteboards would be difficult to se up
21:39:02 <ttx> they don't really come with wheels
21:39:13 <mikal> I could bring some wheels?
21:39:27 <mikal> But either way, it sounds like we're agreed here and I should let you go home?
21:39:38 <ttx> you should let me jump into my bed yes
21:39:52 <ttx> thanks for your time!
21:39:57 <ttx> #endmeeting