21:01:27 <russellb> #startmeeting nova
21:01:28 <openstack> Meeting started Thu Nov 14 21:01:27 2013 UTC and is due to finish in 60 minutes.  The chair is russellb. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:01:30 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:01:32 <openstack> The meeting name has been set to 'nova'
21:01:32 <russellb> hello, everyone!  who's around?
21:01:38 <n0ano> o/
21:01:41 <MikeSpreitzer> o/
21:01:41 <mrodden> hi
21:01:41 <mriedem> hi
21:01:42 <alaski> hi
21:01:43 <dansmith> o/
21:01:43 <jog0> o/
21:01:44 <cyeoh> hi
21:01:44 <melwitt> hi
21:01:46 <shane-wang> hi
21:01:48 <rohitk> hi
21:01:54 <ryanpetrello> hullo
21:01:55 <russellb> awesome, let's get going then
21:02:04 <russellb> #topic general announcements
21:02:10 <russellb> #link https://wiki.openstack.org/wiki/Meetings/Nova
21:02:12 <russellb> that's our meeting page
21:02:16 <russellb> i'll be keeping an agenda on there each week
21:02:22 <russellb> if you have something to add, feel free to edit the page, or ping me
21:02:23 <dims> o/
21:02:30 <russellb> also, if you have ideas for things that we should hit every week, let me know
21:02:45 <mikal> Hi
21:02:52 <russellb> the other general thing for today is making sure everyone has seen the icehouse schedule
21:02:58 <russellb> #link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule
21:03:07 <russellb> #note icehouse-1 release is 3 weeks from today
21:03:16 <russellb> the release will fly by :)
21:03:35 <russellb> so, 66 blueprints targeted at icehouse-1, and 0 to the other milestones isn't terribly realistic, but that's another topic :)
21:03:37 <dansmith> holy crap
21:03:41 <russellb> dansmith: exactly
21:04:21 <russellb> so as you're planning your blueprints, please look closely at the schedule and figure out what's realistic for your work
21:04:26 <mriedem> i'll go ahead and say instance type flavor dedup is probably I2
21:04:26 <jog0> so we have to merge 33 BPs a  week
21:04:28 <mikal> russellb: how firm is that May 15th week for the next summit?
21:04:38 <jog0> err 22
21:04:40 <russellb> mikal: contract signed AFAIK
21:04:48 <russellb> mikal: so very firm
21:04:52 <mikal> russellb: cool
21:04:58 <mikal> russellb: its nice to be able to plan
21:05:14 <russellb> so, week of May 12-16
21:05:22 <russellb> i think they have 5 days booked
21:05:26 <russellb> and we may offset design summit by a day
21:05:34 <russellb> so something like, conf mon-thurs, design summit tues-fri
21:05:38 <russellb> or something, not positive yet
21:05:39 <mikal> Cool
21:05:40 <russellb> but very likely
21:05:55 <mikal> Do you have dates for the mid-cycle meetup? It seems like that might be the week of icehouse-2?
21:05:56 <russellb> "they" being the foundation, that organizes these things
21:06:15 <russellb> ok, so mid-cycle meetup, good question
21:06:34 <russellb> i gave some possible dates to the sponsors (bluehost), and last week they told me to just pick and week and they'll make it work
21:06:38 <russellb> so now it's back on me
21:06:39 <russellb> or us
21:06:44 <mikal> Pick me!
21:06:47 <mikal> I can be the decider
21:07:08 <russellb> heh
21:07:14 <russellb> ok, so based on the poll i did a while back
21:07:21 <russellb> good weeks looked like either january 13th
21:07:34 <russellb> or feb 17
21:07:50 * dansmith votes for the latter
21:07:50 <mikal> Jan 13 will clash with the ATC meetup in Australia
21:07:53 <russellb> feb 17 is a bit more "mid cycle"
21:08:13 <alaski> I'm in favor of Feb as well
21:08:15 <mriedem> location?
21:08:20 <russellb> in the US somewhere
21:08:21 <mikal> Are you thinking an entire week?
21:08:24 <russellb> depends on the date we tell them
21:08:29 <mikal> Or like three days?
21:08:33 <russellb> mikal: sounds like they're willing to host more like 3 days max
21:08:36 <russellb> 2 or 3 days
21:08:45 * beagles votes for St. John's
21:08:46 <russellb> provide us space, and lunches
21:08:50 <dansmith> I think that's more realistic anyway
21:08:53 <dansmith> in terms of travel
21:08:57 <mikal> Oh, so somethign like Feb 17 to 19?
21:08:58 <MikeSpreitzer> Atlanta
21:09:05 <russellb> geekinutah: around by chance?
21:09:05 <MikeSpreitzer> sorry,
21:09:08 <geekinutah> yep
21:09:16 <russellb> possible locations sounded like Boston, or Phoenix
21:09:24 * russellb doesn't really care
21:09:25 <geekinutah> yeah Boston Phoenix or Provo
21:09:32 * mikal wanted Utah
21:09:32 <mriedem> phoenix, warm
21:09:40 <russellb> Provo means possible ski trip :)
21:09:42 <dansmith> I vote provo, phoenix, boston, in that order
21:09:46 <geekinutah> this is true :-)
21:09:56 <mikal> Where is Provo?
21:09:59 <russellb> i haven't been snowboarding in years
21:09:59 <ryanpetrello> Atlanta in Jan/Feb == coooooooold
21:10:01 <russellb> mikal: utah
21:10:17 <russellb> but any would be good :)
21:10:23 <beagles> wondering if staying away from the east coast in that time of year would be a good idea ... for that kind of thing anyways
21:10:39 <russellb> OK, so week of feb 17?
21:10:39 <mikal> Oh yeah, airport closures
21:10:41 <beagles> snowstorms messing with travel, etc
21:10:42 <MikeSpreitzer> Atlanta was typo, sorry
21:10:43 <dims> yay to boston :)
21:11:02 <mikal> russellb: my chances of getting you to run it a week earlier are zero, right?
21:11:04 <MikeSpreitzer> Provo or Pheonix would be my suggestion
21:11:17 <russellb> mikal: a week earlier hits valentines day, which some people care about
21:11:22 <mikal> russellb: I have a probably clash depending on how long the meetup is for
21:11:41 <mikal> What are the dates for Valentine's day?
21:11:42 <russellb> unless we did a monday-tuesday meetup, perhaps
21:11:44 <russellb> feb 14
21:11:46 <mikal> (Don't tell my wife I asked that)
21:11:53 * russellb doesn't care about it, but some do
21:11:53 <shane-wang> :D
21:11:56 <dripton> +1 for avoiding valentine's day
21:11:58 <russellb> comstud told me he'd get shot
21:12:03 <cyeoh> mikal: that comment goes on facebook ;-)
21:12:03 <russellb> for example :)
21:12:05 <dansmith> yeah and we need comstud
21:12:06 <mikal> Well, 10 - 12 Feb would let people get back in time for the 14th
21:12:13 <dripton> changing +1 to -1 to avoid getting comstud shot
21:12:14 <mikal> And then I would miss my kids birthday...
21:12:27 <russellb> mikal: what would make you miss it?
21:12:32 <mikal> s/would/wouldn't/
21:12:37 <russellb> oh, i see
21:12:47 <russellb> anyone *against* feb 10?
21:12:49 <mikal> I need to be back in AU by 21 Feb, which makes the week of the 17th tight
21:13:05 <russellb> mikal: 17-18 meetup?
21:13:10 <russellb> would get you back ... barely
21:13:21 <mikal> 17 - 19 would get me back on the 21st
21:13:25 <russellb> dansmith: i know you had some conflicts, feb 10 work for ou?
21:13:33 <mikal> So tight but doable
21:13:37 * russellb nods
21:13:39 <dansmith> russellb: it would be tight for me, I'm looking
21:13:42 <russellb> k
21:14:09 <dansmith> yeah, I could do it
21:14:15 <russellb> ok, well, right now it's either feb 10 or feb 17, leaning toward feb 10, but i'll wait for anything further last minute "please no" comments, and i will re-review the poll results
21:14:25 <russellb> from there i'll confirm it with bluehost, and report back
21:14:26 <mikal> Cool
21:14:29 <dansmith> mikal: any chance you won't get funding, or will you definitely be there?
21:14:30 <russellb> i know this needs to get firmed up asap for planning
21:14:34 <russellb> sorry i'm terrible at this
21:14:38 <mikal> I personally think three days would be better than two by the way
21:14:50 <russellb> mikal: OK
21:14:52 <mikal> dansmith: I need to check... I can do that today though.
21:15:02 <mikal> Do we have a mail thread for this I can let people know on?
21:15:04 <russellb> mikal: i know 2 is quick for how far you're traveling ...
21:15:13 <dansmith> mikal: okay, if it's unlikely, then maybe we could push for the later, and if not, then the earlier
21:15:24 <russellb> but maybe a smaller group can hang out another day, i dunno
21:15:24 <russellb> i don't want to overextend our welcome
21:15:28 <geekinutah> I think the mean consensus for length was 3 days also
21:15:32 <russellb> mikal: no thread right now, please ping me
21:15:39 <mikal> russellb: sure
21:15:56 <russellb> geekinutah: yeah, but jsmith acted like 3 might be a bit much
21:16:04 <jaybuff> i expect my employeer to sign the stupid CCLA.  if they do i hope to be more involved and I will attend.  I would love a snowboarding the weekend after with whomever is up for it.
21:16:06 <geekinutah> we should check with him on that
21:16:13 <geekinutah> I think it can be done
21:16:19 <russellb> jaybuff: awesome
21:16:22 <geekinutah> we just need to move schedules around
21:16:25 <russellb> geekinutah: OK
21:16:39 <melwitt> snowboarding fun
21:16:41 <jog0> we are 15 min into the meeting and 3 weeks away from I-1 ...
21:16:42 <dansmith> geekinutah: do we get a tour of facilities?
21:16:49 <geekinutah> certainly
21:16:51 <russellb> so ... to firm this up, i'm leaning toward feb 10 based on mikals conflict
21:16:53 <dansmith> sweet
21:16:56 <russellb> and will ask for 3 days, but we'll happily take 2
21:17:04 <jaybuff> +1 provo, feb 10, 3 days
21:17:07 <russellb> going to wait a day for mikal to get back to me
21:17:13 <russellb> and then will push forward
21:17:22 <russellb> sound good?
21:17:42 <mikal> Thanks guys
21:17:45 * russellb nods
21:17:49 <russellb> ok, onward
21:17:50 <russellb> #topic bugs
21:18:02 <russellb> one thing i've mentioned by mail, and in the design summit, is that we need a bug czar
21:18:15 <russellb> because it's one thing that i drop the ball on trying to do everything
21:18:22 <russellb> lifeless spoke up at the design summit as willing to start helping with this
21:18:43 <russellb> for reference, here is our current triage process:
21:18:48 <russellb> #link https://wiki.openstack.org/wiki/Nova/BugTriage
21:18:52 <russellb> however, 82 bugs are untagged
21:19:01 <russellb> and 100 tagged bugs are untriaged (181 total untriaged)
21:19:05 <russellb> so, we aren't doing great at it
21:19:27 <mriedem> one person owning triage gets hard, i've done that before on projects and we had to start rotating it
21:19:29 <russellb> lifeless: around?  thoughts for how we can improve on our bug queue handling?
21:19:33 <lifeless> hi
21:19:38 <lifeless> nuts, today is a public holiday
21:19:40 <russellb> well i envision a person leading the effort, building a team
21:19:52 <lifeless> the bug thing is at the top of my todo list but I vagued on it cause I wasn't going to be here.
21:19:58 <lifeless> I do have a plan!
21:20:07 <russellb> lifeless: ok, all good, shall we revisit next week?
21:20:10 <lifeless> three second over view
21:20:17 <russellb> i like plans
21:20:21 <russellb> k!
21:20:25 <lifeless> get some metrics that I think are valuable to game
21:20:30 <lifeless> ask people to join and game them
21:20:46 <lifeless> don't mention the mile wide holes that can be driven through this plan in IRC
21:20:49 <lifeless> *oops*
21:20:54 <russellb> +1
21:21:00 <russellb> a solid start to many things
21:21:07 * russellb points at reviewstats
21:21:20 <lifeless> also avoid the pathology of bad metrics that Ubuntu has seared in my consciousness
21:21:44 <russellb> heh
21:22:27 <russellb> k, well let's dig into it more next week
21:22:29 <russellb> enjoy your holiday :)
21:22:31 <russellb> #topic sub-teams
21:22:45 <russellb> alright, each week we also hit on status of some sub-team efforts within nova (or the compute program in general)
21:22:56 <russellb> one that i'd like to start checking in on regularly this cycle is novaclient
21:23:06 <russellb> multiple people have expressed interest in helping, some of which i still need to follow up with
21:23:17 <russellb> but melwitt is one, and she has stepped up to help bring some status info to our weekly meeting :-)
21:23:28 <russellb> melwitt: i know we're just getting started, but any thoughts for today?
21:23:53 <melwitt> yes, I have gathered a few metrics for the novaclient bugs and reviews
21:23:58 <russellb> awesome
21:24:37 <melwitt> there are 107 open bugs, i.e. bugs that are not status 'fix released'. 40 bugs in new status, 2 high importance bugs (I don't remember how to link LP bugs here)
21:25:11 <melwitt> there are 10 patch reviews up, all of which are being actively looked at/updated/reviewed, a couple of them are WIP
21:25:38 <russellb> OK, so definitely need some help doing triage
21:25:38 <russellb> you can just paste bug links
21:25:38 <russellb> but sure we have a fancy bot in here for bug numbers ...
21:25:53 <russellb> so the two High priority bugs, being looked at?
21:25:54 <melwitt> oh ok. https://bugs.launchpad.net/python-novaclient/+bug/1039572
21:26:02 <russellb> let's try ... bug 1039572
21:26:14 <russellb> no bug bot.
21:26:28 <dripton> lp:1039572
21:26:28 <dripton> nope
21:26:43 <russellb> that first one looks fixed now
21:26:51 <russellb> joe linked to a patch that has since been merged
21:26:55 <melwitt> the other is https://bugs.launchpad.net/python-novaclient/+bug/1116593
21:26:57 <russellb> melwitt: do you have permissions to close bugs?
21:27:06 <russellb> melwitt: you just need to join the nova-bugs team on launchpad
21:27:07 <russellb> in theory
21:27:25 <melwitt> russellb: oh, yes I'm part of nova-bugs team
21:27:35 <russellb> melwitt: basically, change "Confirmed" to "Fix Committed"
21:27:58 <melwitt> russellb: ah ok. thanks. I missed that it had been merged, I hadn't clicked on it
21:28:10 <russellb> all good :)
21:28:13 <russellb> that's why we're talking through them!
21:28:14 <russellb> progress
21:28:25 <russellb> ok, so the other one ... depends on a nova feature, and we have the nova feature as wishlist
21:28:31 <russellb> so i think i'd change the novaclient bug to wishlist, as well
21:28:51 <melwitt> ok. will do that.
21:29:09 <russellb> and like magic, no more High bugs :-p
21:29:14 <mikal> Heh
21:29:21 <russellb> thanks for bringing the info!
21:29:22 <melwitt> I never knew it could be so simple! thanks for the help
21:29:49 <russellb> if anyone would like to help with novaclient metrics, or help clean up the novaclient bug queue, please talk to melwitt !  (and you all can talk to me, too)
21:29:56 <russellb> sounds like the bug queue is the biggest area in need of cleanup
21:30:01 <dripton> fyi: the magic that closes bugs in launchpad fails if there's a dot after the bug number.  So tag maintainers need to look for bugs to manually mark fixed.
21:30:16 <russellb> dripton: that seems like an oversight :)
21:30:29 <russellb> in the magic
21:30:38 <rohitk> russellb: Can we form a subteam for third party compatibility efforts? I know atleast 5 folks who're interested
21:30:39 <mikal> dripton: sounds like a bug needing fixing
21:30:48 <dripton> russellb: there's a regex somewhere in the git magic that needs fixing.  I'll look for it.
21:30:56 <russellb> rohitk: that was next on my list!
21:30:58 <russellb> dripton: great!
21:31:02 <russellb> ok, next sub-team ...
21:31:08 <russellb> we had a session on AWS (EC2) compatibility
21:31:13 <mikal> dripton: probably openstack-infra/jeepyb ?
21:31:22 <russellb> the outcome was basically that those interested needed to coordinate efforts in a subteam
21:31:28 <russellb> rohitk: that was your session, right?
21:31:34 <rohitk> russelb: right
21:31:38 <russellb> OK, great
21:31:52 <russellb> so some thoughts on how to get started ... poll the openstack-dev mailing list for those that would like to join
21:31:59 <russellb> aim to have at least a few people working together regularly
21:32:10 <russellb> and then find a time that is reasonable convenient for everyone to meet once a week
21:32:15 <russellb> and schedule an IRC meeting
21:32:32 <russellb> and then hopefully one person out of that group can come here and give some status to the rest of the nova community
21:32:56 <russellb> once you have a group, work to divide and conquer work, baby steps
21:33:07 <russellb> increase some test coverage, close feature gaps, whatever you guys think is important
21:33:16 <russellb> from a high level anyway :-)
21:33:21 <rohitk> russellb: sounds good, will get started on this
21:33:25 <russellb> ok, awesome
21:33:31 <russellb> please let me know if you want to discuss further or need any help
21:33:35 <russellb> i'm happy to see this get going
21:33:43 <rohitk> russellb: absolutely, thanks
21:34:02 <russellb> and i can try to attend the first meetings at least to help talk about how the work integrates back into nova
21:34:04 <russellb> processes and such
21:34:46 <russellb> one other thing that we need a sub-team going on is containers
21:34:52 <russellb> we had a big discussion on the future of docker
21:35:02 <russellb> and it sounds like we may go with a separate project completely
21:35:13 <russellb> step 1 being come up with a straw man API for what such a project would expose
21:35:26 <russellb> to help us really decide if it needs to be separate, or continue to be an extension to nova
21:35:45 <russellb> samalba: around by chance?
21:36:06 <russellb> i'm not sure we identified concretely who was going to run with this idea
21:36:06 <russellb> but samalba did the docker driver :)
21:36:13 <russellb> so i'm hoping he does!
21:36:40 <russellb> for reference ...
21:36:42 <russellb> #link https://etherpad.openstack.org/p/docker-nova-hkg
21:37:01 <russellb> big list of people on there interested
21:37:03 <samalba> russellb: I am here
21:37:13 <russellb> samalba: just trying to identify next steps on our containers discussion
21:37:13 <samalba> (reading the backlog)
21:37:30 <russellb> samalba: are you (or someone) going to start organizing that?  drawing up an API?
21:37:45 <samalba> yes, I was planning to start the spec this week-end
21:37:50 <russellb> perfect!
21:37:57 <samalba> and involve the people from the etherpad early
21:38:03 <russellb> sounds great, let me know how it goes
21:38:08 <russellb> and i'll also try to check in with you
21:38:16 <samalba> mainly draft the API + requirements for starting the implem
21:38:21 * russellb nods
21:38:26 <russellb> sounds like a good place to start
21:38:43 <samalba> I guess etherpad is the right place to draft
21:38:44 <russellb> another key bit is some architecture ... specifically, the interaction with existing openstack services
21:38:52 <samalba> exactly, it's included
21:38:53 <russellb> such as, is it built on top of nova exclusively?
21:38:59 <russellb> ok, so you're all over it :)
21:39:13 <russellb> yeah, etherpad or wiki, whichever
21:39:26 <russellb> or a git repo
21:39:27 <jog0> russellb: do we want this to be part of the openstack compute project (not sure if I got terminology right there), as in we would have nova and x
21:39:28 <samalba> yes, just did not have the chance to start yet... but it's planned for short term :-)
21:39:29 <russellb> with just docs
21:39:38 <samalba> ok
21:39:42 <jog0> russellb: I guess I am jumping the gun, never mind
21:39:47 <russellb> jog0: no, it's a good question
21:40:00 <russellb> my opionion is that containers are a part of nova right now, so this effort should start as a sub-project of the compute program
21:40:26 <jog0> program ooh thats the word I was looking for
21:40:27 <russellb> if this moves forward far enough that it becomes a new project, we'll re-evaluate
21:40:27 <russellb> programs are largely about groups of people
21:40:32 <russellb> if the people working on it are largely separate from those doing nova, it would probably make sense to have a new program
21:40:40 <russellb> if there's significant overlap, i would keep it under compute
21:40:49 <russellb> from a technical standpoint, i think we could argue it either way
21:40:52 <russellb> but it really comes down to the people
21:41:12 <russellb> on a related note, every program is supposed to have a mission statement that helps capture the scope
21:41:15 <russellb> i don't think we have one :)
21:41:21 <mikal> "To not suck"
21:41:23 <russellb> "compute" is our mission statement
21:41:24 <russellb> :-p
21:41:26 <russellb> mikal: and that
21:41:34 <mikal> "To not suck at compute"
21:41:40 <jog0> mikal: ++
21:41:49 <russellb> so anyway, let's start with an effort of the compute program to bootstrap
21:41:51 <russellb> make sense?
21:42:07 <samalba> russellb: I have to leave IRC for a bit, but I'll keep you in the loop for specing this containers service
21:42:13 <russellb> samalba: sounds good!
21:42:16 <russellb> ok, other subteams
21:42:21 <russellb> scheduling, vmware, xenapi, hyper-v
21:42:28 <russellb> anyone want to provide updates on those?
21:42:35 <russellb> all had a session, or multiple sessions last week
21:42:38 <n0ano> scheduling - no meeting this week (recovering from the summit)
21:42:49 <russellb> n0ano: sounds good, i'm still recovering too :)
21:43:05 <n0ano> lots of sessions from the summit, we'll start going over them next week.
21:43:10 <russellb> sounds good
21:43:19 <russellb> #topic blueprints
21:43:29 <russellb> so we had a thread about blueprint process here
21:43:36 <russellb> #link http://lists.openstack.org/pipermail/openstack-dev/2013-October/017290.html
21:43:51 <russellb> I've started integrating our process tweaks into the main blueprints page
21:43:53 <russellb> #link https://wiki.openstack.org/wiki/Blueprints
21:43:58 <mriedem> was just going to ask about that
21:44:01 <russellb> if there is anything about the blueprint process not clear from that page, it needs love
21:44:08 <russellb> (as of the last couple hours)
21:44:32 <russellb> so, we need to start reviewing these things
21:44:34 <russellb> #link https://blueprints.launchpad.net/nova/+milestone/icehouse-1
21:44:38 <russellb> 66 blueprints, all on icehouse-1
21:44:42 <russellb> <glare>
21:44:45 <russellb> none on 2 or 3
21:44:55 <mriedem> i can make that 65
21:45:01 <russellb> cool :)
21:45:12 <russellb> if you have something that you don't think will be merged by 3 weeks from today, please go ahead and update
21:45:27 <mriedem> instance type / flavor rename is just a lot of busy work, so taking a while
21:45:29 <russellb> i'd like to spend tomorrow starting a big push to catch up on blueprint reviews
21:45:47 <russellb> so if you're on nova-drivers, or would like to help (anyone can help), please hang around #openstack-nova tomorrow
21:45:54 <russellb> and we'll see how far we get
21:45:57 <russellb> depending on how well it goes, we may have another day next week
21:46:36 <russellb> any particular ones you guys want to talk about right now?
21:46:48 <shane-wan1> russellb: can you approve bp https://blueprints.launchpad.net/nova/+spec/pci-api-support?
21:46:55 <russellb> heh
21:47:04 <shane-wan1> we are confident for icehourse-1
21:47:10 <dansmith> haha
21:47:13 <russellb> we will be reviewing blueprints tomorrow :)
21:47:21 <russellb> there are probably 50 that need to be looked at
21:47:26 <shane-wan1> ok
21:47:29 <geekinutah> +1, I just added one :-)
21:47:31 <russellb> so you're not alone
21:47:53 <russellb> we just need to firm up our process, and then talk about it at the summit
21:47:57 <russellb> and this week has been a bit of recovery
21:48:00 <shane-wan1> is there a review meeting, which everyone  can join?
21:48:00 <jog0> russellb: I like https://wiki.openstack.org/wiki/Blueprints#Blueprint_Review_Criteria
21:48:03 <russellb> so i think we're finally to where we can catch up on this
21:48:21 <russellb> shane-wan1: no specific time, just going to do it tomorrow on IRC
21:48:23 <russellb> "tomorrow"
21:48:24 <dansmith> shane-wan1: please read the scroll back from like three minutes ago
21:48:26 <russellb> jog0: cool thanks
21:48:42 <shane-wan1> ok, just disconnected, sorry
21:48:44 <shane-wan1> :D
21:48:55 <russellb> let's start pasting this wiki link everywhere
21:49:14 <russellb> a majority of people seem to screw up step 1
21:49:14 <russellb> (targeting to a milestone)
21:49:14 <russellb> targeting a milestone is a trigger to get review ...
21:49:17 <jog0> russellb: that may help make it easier to review them tomorrow
21:49:17 <russellb> and then i get emails "why isn't my thing reviewed yet"
21:49:19 <russellb> because you missed step 1
21:49:36 <russellb> jog0: yeah hope so, and we can tweak that criteria as we go
21:49:46 <russellb> another thing .... while we have 66 on icehouse, we probably have a couple hundred others
21:49:59 <russellb> i'd like to do a mass close of others after another week or so
21:50:05 <russellb> next friday was the date i put on the ML a while back
21:50:06 <shane-wan1> ideally, icehouse-3 will be busy
21:50:18 <russellb> i'll post a reminder
21:50:34 <russellb> https://blueprints.launchpad.net/nova/
21:50:34 <russellb> 358 total blueprints
21:50:44 <russellb> need to identify what's actually active work, so close them all :)
21:50:44 <shane-wan1> oh, my god
21:50:49 <russellb> and see what gets reopened i guess
21:50:55 <russellb> close with a comment linking to process info
21:50:58 <shane-wan1> blueprints look like bugs
21:51:07 <russellb> nova is busy :)
21:51:28 <mrodden> implement all the thigns
21:52:01 <russellb> OK, I think that's all for now!
21:52:04 <russellb> #topic open discussion
21:52:10 <russellb> a few minutes for any other topics
21:52:26 <geekinutah> I have a random topic
21:52:30 <mikal> So, I'm approved for Utah
21:52:37 <russellb> mikal: nice work
21:52:44 * beagles notes "fast work"
21:52:53 <russellb> mikal: we decided it's only for people in the northern hemisphere though, sorry
21:53:04 <shane-wan1> mikal: for meetup, so quick?
21:53:37 <geekinutah> I don't know if anyone here uses libvirt hooks to tray and track state changes
21:53:47 <geekinutah> s/tray/try/
21:54:17 <geekinutah> we are starting down that road and I'm wondering if this is something that would belong in nova
21:54:22 <mikal> russellb: doh!
21:54:27 <russellb> the power state notification hook thing that nova has started using?
21:54:42 <geekinutah> uhhhhh, probably similar, first I've heard of it though
21:54:49 <russellb> ok, well take a look ...
21:54:52 <dansmith> geekinutah: yeah, some work has been done there
21:54:56 <russellb> we have a thing now where nova gets notified of VM power state changes
21:55:00 <russellb> instead of nova polling in a periodic task
21:55:11 <geekinutah> omg
21:55:15 <russellb> uses a libvirt hook
21:55:19 <russellb> :)
21:55:20 <geekinutah> so that's awesome, I'll check it out
21:55:25 <russellb> was merged into grizzly IIRC
21:55:37 <russellb> like last minute grizzly
21:55:46 <russellb> though i think it may have been broken until recently ...
21:56:10 <geekinutah> anyone remember the blueprint?
21:56:18 <russellb> geekinutah: search "virtevent" in nova/compute/manager.py
21:56:24 <russellb> geekinutah: and git blame / log from there
21:56:25 <russellb> best i got
21:56:45 <russellb> actually blueprint is compute-driver-events
21:57:01 <russellb> https://blueprints.launchpad.net/nova/+spec/compute-driver-events
21:57:12 <geekinutah> thank you much, I will investigate
21:57:15 <russellb> np
21:57:50 <russellb> anything else?
21:57:53 <beagles> mmmm
21:58:45 <russellb> beagles: neutron parity notes?  :)
21:58:46 <beagles> fwiw there will be some activity in the next bit in the bit of neutronv2 code
21:58:57 <russellb> excellent
21:59:00 <beagles> (sorry dog just tipped computer over)
21:59:03 <russellb> ha
21:59:08 <russellb> work from home life
21:59:24 <shane-wan1> :D
21:59:31 <shane-wan1> admire
21:59:47 <russellb> alright, everyone, about out of time
21:59:49 <beagles> as it is in the nova tree the reviews are going to show up on that side of things,I'm going to be hauling neutron folks over to review
21:59:51 <beagles> but ...
21:59:52 <russellb> biggest thing this week, let's get these blueprints in shape
22:00:12 <russellb> beagles: OK, if you can help identify which ones need priority that'd be great
22:00:17 <beagles> I may ask some questions regarding assumptions where the API might be a ambiguous
22:00:17 <russellb> report them in this meeting is a good time
22:00:27 <beagles> agreed and will do
22:00:46 <russellb> or ML threads as needed
22:00:47 <russellb> tagged with [Nova][Neutron]
22:00:51 <russellb> hopefully that will get the right attention
22:01:09 * beagles nods
22:01:20 <russellb> thanks everyone!
22:01:22 <russellb> #endmeeting