21:02:09 <russellb> #startmeeting nova
21:02:10 <openstack> Meeting started Thu Oct 24 21:02:09 2013 UTC and is due to finish in 60 minutes.  The chair is russellb. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:02:11 <russellb> hello, everyone!
21:02:11 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:02:14 <openstack> The meeting name has been set to 'nova'
21:02:19 <mriedem> hi
21:02:21 <beagles> bonjour
21:02:24 <melwitt> hi
21:02:26 <dansmith> o/
21:02:29 <yjiang5> hi
21:02:38 <hartsocks> \o
21:02:50 <russellb> just a couple of things to cover today ...
21:02:52 <russellb> #topic design summit
21:02:58 <cyeoh_> hi
21:03:00 <russellb> technically the deadline for session proposals was a week ago
21:03:13 <russellb> we have the schedule mostly completed in an etherpad, and i'll be finalizing it tomorrow
21:03:20 <russellb> so ... last call for anything that's missing
21:03:52 <russellb> i think it's going to be a really good set of sessions
21:04:06 <russellb> we (the group doing the schedule) decided we wanted to try something a little different this time
21:04:13 <russellb> we're having some nova unconference time slots
21:04:29 <russellb> for people with shorter topics to get up and talk for a few minutes (10 minutes each)
21:04:50 <russellb> i'll post something to the ML about that to start accepting sign-ups for that next week
21:05:09 <russellb> they'll all be the session right after lunch
21:05:18 <russellb> or at least that's the plan right now
21:05:26 <russellb> any questions about design summit stuff?
21:05:44 <russellb> should have the first cut at the schedule published sometime tomorrow
21:05:46 <yjiang5> russellb: seems still some proposal marked un revirewed, are they reviewed already?
21:06:06 <russellb> most of the review has been done in an etherpad and hasn't been applied to the site yet, sorry
21:06:11 <russellb> which session are you wondering about?
21:06:14 <yjiang5> russellb: got it.
21:06:39 <yjiang5> russellb: my seeion of the enhance for the resource tracker.
21:06:48 <russellb> let me check
21:07:14 <yjiang5> russellb: if not accepted, don't rush for it :)
21:07:15 <russellb> http://summit.openstack.org/cfp/details/251
21:07:31 <russellb> alaski left a comment, we were planning to not have that one because of the reason he said
21:07:40 <yjiang5> russellb: thanks, will have a look
21:07:42 <russellb> basically we just thought it was a good idea, and nothing to really debate
21:07:59 <russellb> you could use a nova unconference slot if you'd like to discuss it briefly though
21:08:14 <dansmith> yjiang5: I thought you weren't going to be at summit?
21:08:20 <yjiang5> russellb: great then I can begin work on it, with next level details.
21:08:32 <yjiang5> dansmith: yes, but my colleague can help me on it.
21:08:45 <dansmith> okay
21:08:57 <russellb> anyone else itching to know about their session?
21:09:50 <russellb> when the schedule gets published, it will show up on http://icehousedesignsummit.sched.org/
21:09:53 <russellb> so watch there for updates
21:10:26 <russellb> #topic icehouse blueprints
21:10:29 <russellb> #link http://lists.openstack.org/pipermail/openstack-dev/2013-October/017290.html
21:10:33 <russellb> we spoke about this topic last week
21:10:56 <russellb> that message is pretty much putting the details in writing more officially
21:11:11 <russellb> haven't seen any big requests for change, so we'll proceed with that process
21:11:55 <russellb> any more comments or questions about it?
21:11:56 * mriedem waits for 11/22
21:12:05 <russellb> we'll also discuss it in a design summit session
21:12:13 <russellb> http://summit.openstack.org/cfp/details/341
21:12:20 <russellb> "Nova Project Structure and Process"
21:12:26 <russellb> among other things
21:12:45 <russellb> generally, project scaling issues from an organization / process perspective
21:13:16 <yjiang5> russellb: So review priority is mostly based on the blueprint priority, and blueprint priority is based on core sponsor, right?
21:13:29 <russellb> yes
21:13:45 <dansmith> so, be sending your gifts to core members starting very soon
21:13:47 <dansmith> (kidding)
21:13:56 <russellb> core sponsor to get above Low
21:14:04 <yjiang5> dansmith: that's what I'm considering :)
21:14:08 <russellb> Medium/High/Essential will still be at the discretion of nova-drivers
21:14:26 <russellb> based on how important it is to the release
21:14:28 <dansmith> yjiang5: I like beer and expensive electronics, FYI
21:14:34 <yjiang5> dansmith: lol
21:15:09 <russellb> corruption in the system already ... sheesh
21:15:21 <dansmith> heh, for the record I am JUST KIDDING
21:15:48 <russellb> i don't think it really changes much, but it will make our blueprint list a more realistic reflection of reality
21:15:53 <russellb> as far as priorities go
21:15:58 <yjiang5> russellb: agree.
21:16:01 <dansmith> that is gift enough for me :)
21:16:08 <russellb> so we'll see how it goes
21:16:22 <russellb> hopefully it doesn't result in a bunch more nagging of "please sponsor my blueprint"
21:16:44 <russellb> but we'll work it out :)
21:16:52 <russellb> any blueprint process questions?
21:16:59 <russellb> please get your icehouse blueprints in asap!
21:17:10 <cyeoh_> russellb: so where we have a fairly large hierarchy of blueprints (like the nova-v3-api)
21:17:15 <russellb> after summit is fine though, i expect a majority will get put together the week after
21:17:30 <cyeoh_> are we expected to get sponsors for all the fairly small ones or just the "head" blueprint
21:17:43 <russellb> cyeoh_: good question.
21:18:10 <russellb> in theory, each sub-blueprint should represent a subset of the work
21:18:15 <russellb> so it makes the most sense to get the sponsors on those
21:18:17 <dansmith> I think we have to take that on a case-by-case basis, sponsoring the top nova-v3-api one might be too large,
21:18:23 <russellb> yeah
21:18:28 <dansmith> but for much smaller ones I can see just doing the head BP
21:18:44 <russellb> but with blueprint priorities, we can't bump something under the top level one > Low without doing the same to the top one
21:19:04 <russellb> it sets of ttx's blueprint consistency checking alarms
21:19:17 <dansmith> hmm, I'm not sure if that makes sense, actually
21:19:31 <dansmith> maybe we'll just have to split things up accordingly,
21:19:55 <dansmith> because I can expect to merge some objects work as very important, while others are not so much, all of which are under the icehouse-objects BP
21:20:06 <russellb> actually it's the other way around, sorry
21:20:13 <russellb> you can't call v3-api High, with pre-reqs at Low
21:20:17 <russellb> sorry.
21:20:20 <dansmith> okay
21:20:26 <beagles> yeah, that makes more sense
21:20:28 <dansmith> yeah :)
21:20:31 <russellb> oops
21:20:58 <cyeoh_> ok that sounds fine, I guess we should mark the very small blueprints in some way that says we think it should take the priority of its parent?
21:21:09 <cyeoh_> or at least in terms of sponsors...
21:21:46 <dansmith> I think that's fine and nova-drivers can make the call
21:22:03 <russellb> makes sense.  the majority of blueprints are not a hierarchy
21:22:18 <dansmith> cyeoh_: and if I catch you trying to cheat, I mark everything you've got as wishlist :D
21:22:27 <cyeoh_> hey! :-)
21:22:28 <russellb> ha
21:22:33 <russellb> no wishlist for blueprints :)
21:22:37 <dansmith> I know
21:22:38 <russellb> though there is a priority of "Not"
21:22:42 <russellb> which i find kinda funny
21:22:47 <dansmith> targeted: Zebra Release
21:22:58 <russellb> dansmith: or leave something targeted to "next"
21:22:59 <dims> lol
21:23:08 <russellb> it's like a permanent target of later
21:23:17 <dansmith> russellb: no, cyeoh_ gets Zebra, or Zimbabwe or something
21:23:26 * dansmith stops distracting the meeting
21:23:31 <russellb> :)
21:23:33 <russellb> #topic open discussion
21:23:35 <russellb> beagles: hi!
21:23:39 <beagles> ohi
21:23:49 <russellb> beagles: do you happen to know about nova-network / neutron session scheduling?
21:23:58 * beagles feels like a deer caught in the headlights all of the sudden
21:24:00 <russellb> i haven't caught up with markmcclain to ask
21:24:02 <russellb> :)
21:24:15 <beagles> Crap, no I don't
21:24:17 <russellb> ok
21:24:20 <russellb> session proposed?
21:24:31 <beagles> yes and "preapproved"?
21:24:36 <russellb> perfect
21:24:47 <russellb> i just need to look out for when that gets scheduled for
21:24:50 <russellb> i really want to be there
21:24:53 <russellb> conflicts are tough
21:24:59 * beagles nods
21:25:39 <russellb> any other topics for today?
21:25:42 <beagles> I'll see what's up and get back to y'all asap
21:25:51 <cyeoh_> I have one question about bugs
21:25:52 <russellb> beagles: cool sounds good
21:26:01 <yjiang5> Does anyone know why we create the migration object in resource tracker? It's really should be outside of this. (is this meeting for tech discussion also?)
21:26:02 <russellb> oh yes, bugs, we have those don't we
21:26:15 <russellb> yjiang5: yes, tech discussion is fine in open discussion time
21:26:23 <cyeoh_> I've been going through all the api tagged bugs and noticed there are quite few which are assigned to people, but either have abandoned patches or no patches with no activity > 1 month
21:26:36 <comstud> yjiang5: so that it's done inside of the lock
21:26:43 <cyeoh_> just wondering at what point it is ok to move those back to unassigned?
21:26:46 <comstud> oops, not open disc time yet!
21:26:49 <russellb> cyeoh_: https://wiki.openstack.org/wiki/BugTriage#Task_5:_Review_stale_In_Progress_bugs_.28anyone.29
21:27:00 <russellb> cyeoh_: that basically qualifies as that category in the triage tasks
21:27:12 <yjiang5> comstud: it's open discussion already .
21:27:31 <russellb> cyeoh_: usually i think it's nice to leave one comment saying "are you still intending to work on this?" or something
21:27:32 <comstud> so it is
21:27:47 <russellb> cyeoh_: then come back later and unassign and mark not inprogress
21:28:29 <cyeoh_> russellb: ok, thanks, will do that.
21:28:53 <yjiang5> comstud: I will check why migration requries lock, especially per compute node lock. May back to you in nova channel. Thanks.
21:29:00 <russellb> cyeoh_: great, thanks!
21:29:53 <russellb> anything else?
21:30:00 <mriedem> guess i have a question about blueprints
21:30:03 <russellb> mriedem: sure
21:30:15 <mriedem> we have an old db2 blueprint, but it's going to depend on db2 support in sqlalchemy-migrate
21:30:35 <mriedem> if my migrate patches aren't merged by 11/22, or whenever the nova bp house cleaning happens, am i screwed?
21:31:01 <mriedem> i'll already admit that the existing db2 blueprints need a lot of work, they were from late grizzly / early havana
21:31:17 <russellb> no, you're not screwed :)
21:31:21 <russellb> as long as we know they're not abandoned
21:31:30 <russellb> ideally you can still target the nova one for someting like ... icehouse-2 or whatever
21:31:44 <russellb> with a note saying it's dependent on this other thing getting done in time
21:31:53 <mriedem> russellb: ok, yeah, i know the nova bp definitely won't be done in icehouse-1, probably not even 2
21:31:59 <russellb> ok, icehouse-3!
21:32:10 <mriedem> i meant to get the migrate patches up like 3 weeks ago but things tend to pile up around here...
21:32:12 <russellb> but you know what i mean?  you should still be able to estimate completion of the nova work and ge it targeted
21:32:19 <mriedem> russellb: yup
21:32:22 <mriedem> ok
21:32:22 <russellb> cool
21:32:51 <russellb> one last thing from me ... any objections to canceling next week?
21:33:02 <mriedem> halloween party?
21:33:15 <russellb> heh, yeah, it's a holiday in the US, and I know some of start travel the next day
21:33:47 <mriedem> no objections
21:34:00 <russellb> ok, well meeting canceled next week ... and the week after
21:34:04 <russellb> we'll resume week after summit
21:34:20 <russellb> thanks everyone!
21:34:29 <russellb> #endmeeting