14:00:11 <johnthetubaguy> #startmeeting Nova
14:00:14 <openstack> Meeting started Thu Sep 18 14:00:11 2014 UTC and is due to finish in 60 minutes.  The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:15 <ndipanov> o/
14:00:16 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:19 <openstack> The meeting name has been set to 'nova'
14:00:21 <n0ano> o/
14:00:23 <mriedem> hi
14:00:27 <dansmith> gurgle
14:00:29 <edleafe> o/
14:00:38 <mriedem> uh oh, merman in the room
14:00:57 <johnthetubaguy> #topic Juno RC1
14:01:01 <johnthetubaguy> hello all
14:01:03 <bauzas> \o
14:01:10 <johnthetubaguy> #link https://launchpad.net/nova/+milestone/juno-rc1
14:01:35 <johnthetubaguy> so we are adding bugs to rc1 for everything we feel must be in juno
14:01:46 <johnthetubaguy> #link http://lists.openstack.org/pipermail/openstack-dev/2014-September/046115.html
14:01:55 <johnthetubaguy> above is the email from mikal on the subject
14:02:07 <johnthetubaguy> so, do people have questions about this phase?
14:02:18 <johnthetubaguy> or any bugs that people want to talk about?
14:02:19 <ndipanov> yeah was a bit confused about Critical
14:02:38 <johnthetubaguy> ndipanov: confused, as in why only critical bugs?
14:02:43 <ndipanov> but I assume anything that we can reasonably fix is fair game - and we will only delay the RC1 for critical stuff
14:02:49 <johnthetubaguy> right
14:03:02 <ndipanov> okay
14:03:06 <johnthetubaguy> this is, what ttx will look at to decide when to pull the release trigger
14:03:12 <johnthetubaguy> we can merge other stuff in the mean time
14:03:29 <johnthetubaguy> but the word of caution is, if the gates jammed, then we might have to change our plans there
14:03:36 <johnthetubaguy> ndipanov: that make more sense?
14:03:52 <johnthetubaguy> so, the other thing… I don't think all critical should block rc1
14:03:53 <ndipanov> johnthetubaguy, yeah - the gate's been kind afaict these last few days
14:04:30 <bauzas> johnthetubaguy: most of the critical bugs don't have owners
14:04:39 <johnthetubaguy> I mean, if its affecting the gate, its going to hurt some people after release, and we should probably backport, but maybe not delay the release
14:04:49 <johnthetubaguy> bauzas: right, thats thats the next bit
14:05:04 <bauzas> johnthetubaguy: ok, so I'm keen to listen on it :)
14:05:21 <johnthetubaguy> well, who is happy to step up for these rc1 bugs
14:05:31 <johnthetubaguy> and which of those do we really need to block the release
14:05:59 <bauzas> johnthetubaguy: that's my question
14:06:02 <johnthetubaguy> #help we have critical bugs tagged for juno-rc1 with no owners, we need people to take these on
14:06:04 <dansmith> I've been trying to reprodcuce 1323658, but I really don't want to "own" it until I feel like I can do anything about it :/
14:06:12 <bauzas> johnthetubaguy: if we identify them as critical, then they're blockers
14:06:46 <johnthetubaguy> dansmith: OK, understood, I mean I wonder about a part time owner so others don't duplicate the repo effort, but I get your point
14:06:53 <johnthetubaguy> so, next question
14:07:06 <dansmith> johnthetubaguy: well, there's nothing to duplicate now, and parallelism is probably good right now :/
14:07:07 <johnthetubaguy> if we can't fix these quickly, should they block rc1?
14:07:15 <johnthetubaguy> dansmith: fair point
14:07:27 <johnthetubaguy> how bad are they really...?
14:08:02 * dansmith looks
14:08:10 <dansmith> ndipanov: is 1369945 really invalid?
14:08:17 <dansmith> if so, we should untarget it
14:08:39 <ndipanov> dansmith, yeah see danpb 's comment
14:08:47 <dansmith> can you untarget it then?
14:08:54 <ndipanov> dansmith, done
14:08:55 <johnthetubaguy> +1
14:08:58 <johnthetubaguy> thanks
14:09:17 <dansmith> 1370068 seems like a good one to fix
14:09:23 <dansmith> ndipanov: have you looked at that? it's assigned to someone else
14:09:34 <johnthetubaguy> OK, we an probably do this offline if thats a better use of peoples time? but certainly worth raising critical stuff
14:09:40 <dansmith> well,
14:09:51 <dansmith> after a quick skim, there are definitely some in there that seem blockerish,
14:10:04 <dansmith> but if we've been working on them for months already, like the resize with neutron thing,
14:10:16 <dansmith> blocking the release until we figure it out is probably not a reasonable thing to do
14:10:18 <johnthetubaguy> do we want to make 1370068 critical?
14:10:29 <johnthetubaguy> dansmith: right thats my thinking too, sadly
14:10:35 <dansmith> yeah, sad indeed :(
14:10:43 <baoli> https://review.openstack.org/#/c/121939/ needs another +2
14:11:06 <johnthetubaguy> so I wish I knew if all the "in progress" has patches up
14:11:09 <johnthetubaguy> I should check that
14:11:32 <johnthetubaguy> I guess its the confirmed ones, with no one assigned that worry me more
14:11:54 <ndipanov> dansmith, yeah - +2'd the fix
14:12:02 <ndipanov> dansmith, feel free to join in on that :)
14:12:08 <dansmith> ndipanov: link?
14:12:14 <johnthetubaguy> danpb: I see quite a few libvirt related things, are they all stuff you want to block the release on?
14:12:25 <ndipanov> dansmith, um it's in the bug no?
14:12:31 <ndipanov> https://review.openstack.org/121887
14:12:34 <dansmith> ndipanov: yeah, I'd moved on
14:13:08 <johnthetubaguy> right, anyways, help getting this list in order would be awesome, feel free to make your case in bug comments if you like
14:13:11 <johnthetubaguy> #topic Bugs
14:13:19 <johnthetubaguy> well we kinda flogged that horse already
14:13:21 <johnthetubaguy> but
14:13:31 <johnthetubaguy> #link http://54.201.139.117/nova-bugs.html
14:13:53 <johnthetubaguy> usual tools help, lets try catch any release blockers we haven't spotted in the pile, if possible
14:13:59 <johnthetubaguy> #topic Gate status
14:14:02 <johnthetubaguy> hows things?
14:14:14 <mriedem> ssh failures, wsgi worker timeouts, etc
14:14:14 <johnthetubaguy> there are gate related bugs without owners it seems
14:14:15 <mriedem> same old
14:14:38 <johnthetubaguy> yeah, no specifics this week I guess?
14:14:59 <ndipanov> mriedem, who is looking into that wsgi thing?
14:15:03 <ndipanov> jaypipes?
14:15:22 <dansmith> yeah and sdague
14:15:27 <johnthetubaguy> #topic Open Discussion
14:15:29 <johnthetubaguy> cools
14:15:33 <johnthetubaguy> #link https://etherpad.openstack.org/p/kilo-nova-summit-topics
14:15:35 <danpb> johnthetubaguy: which bugs ?  i've not really considered any blockers myself - so any proposed were by someone else
14:16:22 <johnthetubaguy> danpb: just looking at the juno-rc1 page, and seeing numa stuff, etc, targeted at RC-1, I was more checking to see if there are any other that need to blocks, and trying to get help clearing out the blocker list
14:16:36 <johnthetubaguy> so the link, please submit ideas for summit sessions
14:16:49 <johnthetubaguy> there was an email, tagged with [all] about the process
14:17:12 <bauzas> johnthetubaguy: do you have any idea of what will consist Day 4 ?
14:17:15 <johnthetubaguy> if there is nothing else, we can go back to reviewing, bug fixing, and triage
14:17:30 <johnthetubaguy> bauzas: do you mean the meet up style bit?
14:17:31 <bauzas> Day 2 and Day 3 are covered by the ethperad
14:17:37 <bauzas> johnthetubaguy: yup
14:17:59 <johnthetubaguy> bauzas: I think the plan is to extract the big themes from that etherpad, and discuss "big issues", like at the mid-cycle
14:18:02 <bauzas> johnthetubaguy: because IIUC, the etherpad will allow us to define which sessions to run by the day 2 and 3
14:18:15 <johnthetubaguy> bauzas: I thought it was going to do both
14:18:31 <bauzas> johnthetubaguy: ok, so I assume it's just the format which will change then
14:18:57 <bauzas> johnthetubaguy: meaning it will timeslots for the first 2 days and then a meetup for the day 4
14:19:13 <johnthetubaguy> bauzas: right thats correct
14:19:28 <bauzas> johnthetubaguy: ack
14:19:43 <johnthetubaguy> there will probably be a meetup etherpad eventually, but lets just gather everything in one place for now
14:19:53 <bauzas> johnthetubaguy: sure thanks
14:20:07 <johnthetubaguy> then we look at what really needs a meetup thing, like "project priorities" etc
14:20:14 <adrian_otto> looks complete from my perspective
14:20:32 <johnthetubaguy> anyways, appreciate the extra attention on that etherpad
14:20:36 <johnthetubaguy> are we all done?
14:20:38 <dansmith> wait
14:20:39 <dansmith> <baoli>	 https://review.openstack.org/#/c/121939/ needs another +2
14:20:44 <dansmith> someone please +W that ^
14:20:49 <dansmith> it's easy and important
14:21:09 <johnthetubaguy> sure, I can take a look in a sec
14:21:16 <johnthetubaguy> any more?
14:21:26 <mriedem> dansmith: i'm reviewing it now
14:21:31 <dansmith> thanks
14:21:53 <baoli> mriedem, thanks
14:22:02 <baoli> dansmith: thanks
14:22:12 <dansmith> johnthetubaguy: go
14:22:20 <johnthetubaguy> cool, all done
14:22:35 <johnthetubaguy> code change looks good, just a bit of the tests looks a bit too relaxed
14:22:40 <johnthetubaguy> anyways, we are done
14:22:43 <adrian_otto> that was short and sweet
14:22:43 <johnthetubaguy> thanks all
14:22:49 <johnthetubaguy> #endmeeting