22:00:46 <danwent> #startmeeting
22:00:47 <openstack> Meeting started Tue Nov  8 22:00:46 2011 UTC.  The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:00:48 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic.
22:01:00 <danwent> Ok, netstack meeting
22:01:17 <danwent> #info: agenda http://wiki.openstack.org/Network/Meetings
22:01:32 <danwent> Quantum focus will mainly be on essex-1
22:01:38 <danwent> troy, still around?
22:02:00 <medberry> troytoman, ?
22:02:12 <troytoman> yes
22:02:21 <danwent> #topic melange status
22:02:35 <troytoman> Melange was just approved as an incubated project
22:02:48 <danwent> congrats :)
22:02:53 <danwent> one thing troy and I talked about is the official location for the melange code
22:03:02 <salv> congratulations troy!
22:03:05 <troytoman> while that's a good thing, it means we will be focused on getting the project infrastructure setup
22:03:34 <troytoman> hopefully, by tomorrow, we'll have the launchpad project setup with much of the key information about location etc.
22:03:43 <medberry> yep, I checked launchpad for membership &c a few min.s ago and found nothing.
22:03:44 <troytoman> I'll also be working on gerrit, etc.
22:03:55 <mtaylor> troytoman: ++
22:04:05 <troytoman> salv: thx
22:04:16 <troytoman> medberry: working on that
22:04:38 <troytoman> otherwise, we are making some adjustments to the Melange API to streamline the interaction with the Nova Quantum Manager
22:04:50 <bhall> yeehaw
22:04:52 <troytoman> and working on adding notifications
22:04:55 <danwent> troytoman: those improvements will be very welcome
22:05:41 <danwent> ok, anything else?
22:05:44 <danwent> questions on melange?
22:06:05 <troytoman> i don't think so. except that we're looking for more devs to get involved!
22:06:07 <danwent> #info melange is incubated.  working on API streamlining for quantummanager, and notifications
22:06:15 <danwent> #topic quantum status
22:06:31 <danwent> Ok, we should be branching for essex-1 tonight (ideally)
22:06:47 <danwent> #info essex-1 milestone: https://launchpad.net/quantum/+milestone/essex-1
22:06:59 <danwent> please open up the link so we can go over outstanding issues.
22:07:10 <danwent> dhcp work for QuantumManager, brad?
22:07:15 <salv> I think the important bits for this release are in master now
22:07:24 <danwent> still in nova review?
22:07:38 <bhall> danwent: still in nova review.. we've got multiple +1's so far but having to rebase erases them
22:07:48 <bhall> I need to track down tr3buchet today and ask for another +1
22:08:06 <bhall> hopefully it will go in today
22:08:08 <salv> bhall: I've been there. Chasing the trunk might be hard
22:08:17 <danwent> yes, please ping him now, if he's still online
22:08:25 <tr3buchet> bhall: it's just been given
22:08:37 <bhall> tr3buchet: gracias :)
22:08:42 <danwent> thanks trey!
22:09:00 <tr3buchet> let me know if you want the +2, i think we've got enough  +1s on it
22:09:11 <bhall> yes that would be nice :)
22:09:11 <salv> bhall: what changes in the QuantumManager with this changeset?
22:09:33 <bhall> salv: it adds dhcp support
22:10:23 <danwent> #info dhcp nova-parity changes are actively being merged into nova
22:10:45 <salv> salv: I wanted a few more dirty details, such as are we doing it with dnsmasq as nova-network or are we using a different strategy? I'm sorry but I did not look at the code.
22:11:09 <bhall> salv: ah, yeah, it's using dnsmasq
22:11:17 <tr3buchet> yep
22:11:20 <bhall> salv: pretty much the same as the other nova nework managers
22:11:34 <danwent> this is just for nova parity
22:11:57 <danwent> will expand on it once we get parity.  I think carlp was talking about doing a true DHCP service in the future
22:12:07 <danwent> Ok, next open issue:  the python-novaclient changes have been rebased, but I need to test them again before asking sandy to pull them in.
22:12:38 <danwent> #info Ok, the python-novaclient changes have been rebased, but I need to test them again before asking sandy to pull them in.
22:13:01 <danwent> salv: update on quantum middleware for keystone?  last I saw it was blocked on pylint?
22:13:21 <salv> Blocked on pylint violations. Code has been fixed and updated 6 hours ago.
22:13:34 <danwent> #info quantum.conf changes to document how to enable keystone middleware is already in quantum
22:13:46 <salv> got a another Jenkins stop now
22:14:18 <dolphm> salv: the pylint blocker is actually project wide, so fixing pylint violations anywhere will get it back under the threshold
22:15:02 <salv> I got that dolphm, I tried to fix a few violations earlier on but those were not enough
22:15:08 <salv> is the thresold actually 32?
22:15:30 <dolphm> salv: it's around ~500 for the whole project
22:16:06 <salv> okay my changeset put the total number to 497, maybe fixing 20-30 violations should be enough
22:16:12 <salv> I will push again right after the meeting
22:16:15 <danwent> salv: great
22:16:17 <salv> dolphm: thanks!
22:16:34 <dolphm> salv: didn't realize this was openstack-meeting lol, ping me if you need help!
22:16:45 <danwent> #info: quantum middleware pushed keystone over project-wide pylint threshold.  salv will do a bit of clean-up to try to get it back down.
22:16:48 <salv> dolphm: sure
22:17:01 <dolphm> my apologies for crashing whatever meeting this is =)
22:17:07 <salv> on another note I'm still trying to merge bp/api-framework-essex
22:17:22 <danwent> read my mind (or the milestone list)....
22:17:44 <danwent> pep8 issues?
22:17:45 <salv> I think it would be better to have it in essex-2
22:18:14 <salv> danwent: some bits of code which apparently are not in the right place
22:18:47 <danwent> salv: Ok, I'd prefer not to jam it in if you don't think it is ready.  Hopefully we can get it in right away for essex-2?
22:18:49 <salv> Since this bp does not actually add any functionality, I think we can slip it to essex-2, so I will be able to see some TV or a movie tonight :)
22:19:10 <danwent> I know of a few people that were holding off on doing API-related work with the goal of avoiding conflicts with this framework change
22:19:26 <danwent> tv or movie sounds like a good choice :)
22:19:30 <salv> can be merged in the next few days
22:19:40 <danwent> great.  let's untarget
22:19:44 <salv> I just reckon we don't have a need for essex-1
22:20:15 <danwent> yeah, I think its more important that the dev work got done in essex-1 period, not necessarily that code was in essex-2 deliverable
22:20:22 <danwent> essex-2 -> essex-1
22:20:47 <danwent> #info: delyaing API framework code until early essex-2.  No impact on features.
22:20:55 <danwent> on to the bugs.
22:21:20 <danwent> I still need to rework the README.  have been viewing this as lower priority than code changes.
22:21:53 <danwent> README changes will just try to get rid of duplicate + out-dated references to things that are now covered in main quantum documentation.  will include a pointer to docs instead.
22:21:59 <danwent> will have a review out later this afternoon.
22:22:20 <danwent> #info README changes to point to new Quantum docs will still be in essex-1.  available for review later today
22:22:29 <danwent> bhall: want to comment on your two bugs?
22:22:41 <bhall> sure
22:22:48 <danwent> both are listed as in progress, not code review?
22:22:55 <bhall> they will go in as soon as the cisco folks run the tests against the update() call patch
22:23:13 <danwent> ah… no "code review" state for bugs
22:23:16 <bhall> danwent: there is no code review status for bugs ;)
22:23:17 <danwent> I always forget that.
22:23:36 <bhall> I think tyler said he'll have tim ethis afternoon
22:23:41 <danwent> OK.  any other essex-1 issues we need to be coordinating on?
22:24:11 <danwent> what about the new patch sent to the list?
22:24:53 <danwent> is ghe around?
22:25:06 <bhall> I tihnk that went in?
22:25:10 <Ghe_Rivero> tep
22:25:18 <Ghe_Rivero> here i am
22:25:44 <danwent> wow, got to refresh I guess
22:25:59 <danwent> the world moves by pretty quickly… yes, that was already reviewed and merged.  thanks bhall :)
22:26:12 <bhall> no prob.. thanks to Ghe for doing it
22:26:44 <Ghe_Rivero> you are welcome
22:26:50 <danwent> ideally we would have opened a bug on that are targeted it to essex-1, given how late it was coming in, but I didn't tell Ghe to do that, so its my fault :)
22:27:27 <danwent> Ok, so sounds like essex-1 will be in good shape.  Will probably branch tonight.
22:28:06 <danwent> #info: decided to delay patch to combine plugins.ini into quantum.conf to avoid breaking automated testing environments right before a milestone.  this will go in early essex-2
22:28:20 <danwent> here is the patch for reference: https://review.openstack.org/#change,1415
22:28:48 <danwent> ok, great work on the reviews folks, especially with the compressed schedule.
22:29:20 <danwent> please keep a look out for any remaining reviews… anything going in at this point should be both small and important
22:29:29 <danwent> otherwise we'll push it to essex-2
22:29:35 <danwent> Ok, is carlp here?
22:30:30 <danwent> Along with nova-parity our other big short-term goal is better functional and system test.
22:30:53 <danwent> #todo: #danwent will contact #carlp and have him send something out on next steps there.
22:31:22 <danwent> final note for quantum, essex-2 milestone is now essentially open: https://launchpad.net/quantum/+milestone/essex-2
22:31:54 <danwent> we got a bit of a late start on essex-1 due to planning, so will be hounding people to get things in for essex-2 to make sure its a nice plump release :)
22:32:06 <danwent> any general questions/concerns about quantum?
22:32:25 <danwent> #info: please now target blueprints for essex-2: https://launchpad.net/quantum/+milestone/essex-2
22:32:42 <danwent> at next tuesday's meeting I would like to cover what we plan to get done for essex-2.
22:33:00 <danwent> #topic open discussion
22:33:02 <salv> sounds reasonable
22:33:19 <danwent> salv: does the DST change help you at all, or is it still midnight when this meeting ends for you?
22:33:32 <salv> it's 11
22:33:36 <salv> not bad :)
22:33:40 <danwent> sweet, practically the middle of the day :)
22:33:58 <danwent> Ok, sounds like no other open discussion.  have a good day folks!
22:34:03 <danwent> #endmeeting