21:00:49 <danwent> #startmeeting quantum
21:00:51 <openstack> Meeting started Mon Oct  8 21:00:49 2012 UTC.  The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:00:52 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:53 <openstack> The meeting name has been set to 'quantum'
21:01:08 <zykes-> Aloha.
21:01:08 <danwent> #info agenda: http://wiki.openstack.org/Network/Meetings
21:01:12 <SumitNaiksatam> Hello!
21:01:33 <danwent> Ok, should be a pretty short meeting
21:01:35 <garyk> hi
21:01:38 <danwent> summit in next week
21:01:46 <markvoelker> \o/
21:01:56 <danwent> but before we talk about that, wanted to talk a bit about folsom release
21:01:58 <salv-orlando> hello!
21:02:26 <danwent> garyk is going to be point on working with the openstack stable-maint team
21:02:49 <danwent> we should all help garyk by making sure bugs that are relevant to folsom are marked with folsom-backport-potential
21:02:55 <danwent> here is the current list: https://bugs.launchpad.net/quantum/+bugs?field.tag=folsom-backport-potential
21:03:13 <danwent> A recently filed issue that I wanted to call attention to is https://bugs.launchpad.net/quantum/+bug/1062046
21:03:15 <uvirtbot> Launchpad bug 1062046 in quantum "There is a lot of cases that API with an invalid parameter returns 500." [High,Confirmed]
21:03:36 <danwent> basically, there are a lot of cases, particularly around IPAM stuff, were we don't perform proper validation
21:03:49 <danwent> causing exceptions where we should return 400s
21:04:08 <danwent> would be great if someone could take on doing some validation clean-up… free brownie points :P
21:04:24 <garyk> danwent: i can take a look at it.
21:04:31 <danwent> garyk: great, thx
21:04:32 <salv-orlando> I'll do that if you give me a real brownie
21:04:41 <danwent> salv-orlando: sorry, virtual brownies only
21:04:46 <nati_ueno> heyyo
21:04:56 <danwent> are there other folsom bug issues we need to talk about?
21:05:38 <arosen> hi
21:05:41 <danwent> at this point, the biggest issues seem to be a need to expand the docs, so please try to keep filing and fixing issues within openstack-manuals (search for tags 'quantum' and 'netconn-api')
21:05:53 <garyk> danwent: 1060559
21:06:17 <garyk> i have seen a number of issues here.
21:06:23 <danwent> https://bugs.launchpad.net/quantum/+bug/1060559
21:06:25 <uvirtbot> Launchpad bug 1060559 in quantum "l3_agent not disabling namespace use" [High,Fix committed]
21:07:02 <garyk> some are related to documentation. others need to be discussed a bit more - for example i have managed to reproduce a case where the tag was not assigned to a device.
21:07:31 <garyk> this happens when the provider networks do not find matching devices - for example after reboot.
21:07:38 <garyk> i'll try and sum it up tomorrow
21:07:59 <danwent> garyk: interesting.  is it related to the issue you mention above?
21:08:04 <danwent> https://bugs.launchpad.net/quantum/+bug/1060559
21:08:05 <danwent> ?
21:08:06 <uvirtbot> Launchpad bug 1060559 in quantum "l3_agent not disabling namespace use" [High,Fix committed]
21:08:44 <garyk> danwent: no. i was just following mails and trying to reproduce the problems found. i stumbled on the tag issue and connectivity problems
21:09:01 <danwent> ah, ok.
21:09:43 <rkukura> garyk: is there a bug filed for this tag issue?
21:09:55 <garyk> rkukura: not yet. i'll open it tomorrow
21:10:20 <danwent> ok, it sounds significant, so this may be the first issue that really requires us to do a stable release.  let's track this via email.
21:10:39 <danwent> or better yet, get a placeholder bug that we can send out a link to now
21:10:52 <gongysh> I think we already filed one but we cannot reproduce it before.
21:11:00 <danwent> so that everyone can subscribe that cares about it.
21:11:22 <garyk> the bug has most of the details. some are not related most are documentation issues
21:11:32 <amotoki> gongysh: which one?
21:11:35 <danwent> gongysh: yes, we used to, though we thought that it was due to something else.
21:11:39 <salv-orlando> gongysh: I think you filed it a few days before RC-1, is that correct?
21:11:46 <gongysh> yes
21:11:58 <danwent> my guess is that there have been multiple bugs, all that result in the same behavior of a port not being properly tagged
21:12:04 <danwent> let's open a fresh bug for this one
21:12:24 <gongysh> fine with ne wone.
21:12:27 <gongysh> one
21:12:51 <garyk> i'll provide the details tomorrow
21:12:58 <danwent> ok, garyk, can you file a place holder so we can all register as watchers, and provide details tomorrow?
21:13:10 <garyk> danwent: ok
21:13:22 <danwent> ok, last call for folsom release follow-up
21:13:39 <danwent> #topic grizzly summit
21:13:43 <danwent> #link http://www.openstack.org/summit/san-diego-2012/
21:14:02 <danwent> summit is next week, hope to see as many of you there as possible
21:14:20 <danwent> we wanted to take a survey of how many folks will be available sunday night if we organize a quantum team hang-out
21:14:25 <garyk> danwent: https://bugs.launchpad.net/quantum/+bug/1064070
21:14:26 <uvirtbot> Launchpad bug 1064070 in quantum "tap device added to integration bridge without tag" [Undecided,New]
21:14:37 <danwent> and if so, what time you think you'd get to the hotel and be available to meet up
21:14:41 <danwent> garyk: thx
21:15:14 <gongysh> I will be back on the 19 morning
21:15:20 <garyk> danwent: i arrive at 7pm. need to get through immigration and from the airport. i'll be happy to meet up after i am trhough
21:15:43 <danwent> yeah, trying to figure out if we should do a dinner, or just later drinkts
21:15:50 <markmcclain> I'm there starting at lunch time
21:15:54 <gongysh> I arrive on 14
21:16:00 <mnewby> 16h
21:16:03 <rkukura> I get in at ~ 1:00 PM
21:16:08 <markvoelker> danwent: I'm arriving Sunday night and might be able to make it for drinks
21:16:23 <mestery> 19h
21:16:34 <arosen> I get in ~6:14pm sunday
21:16:45 <nati_ueno> I'm get in 6pm sunday
21:17:04 <danwent> ok, so maybe we do something 8pm…
21:17:06 <amotoki> around 6pm sunday.
21:17:08 <salv-orlando> I am on the 3PM flight from SJC
21:17:37 <salv-orlando> danwent: 8pm would be awesome
21:18:00 <danwent> ok, let's shoot for that.  I'll look for some bar/restaruant walking distance from the hotel
21:18:00 <mestery> danwent: 8PM sounds pretty awesome.
21:18:15 <danwent> we'll have food to nibble on, but not a formal sit-down meal
21:18:18 <salv-orlando> garyk: I promise I will wait for you for the first drink!
21:18:22 <danwent> and of course, drinks :)
21:18:28 <garyk> salv-orlando: great
21:18:32 <danwent> salv-orlando: i bet I can get you to drink first...
21:18:38 <danwent> :P
21:19:14 <danwent> ok, sounds like fun.  I'll plan for maybe ~15 people.
21:19:44 <mestery> danwent: Please provide enough drinks for 20 though. :)
21:19:48 <danwent> ok, other summit topics (apparently its not all about eating/drinking/hanging-out)
21:19:58 <danwent> mestery: you count for 5? P
21:20:03 <danwent> :P
21:20:20 <mestery> danwent: Ha! Is that a challenge? :)
21:20:26 <danwent> so quantum sessions are monday/tuesday/wed only
21:20:33 * markvoelker vouches for mestery's virtual drinking ability
21:20:51 <danwent> info: at the request of the people who are participating but mainly focused on the load-balancing, those sessions will all be on tues/wed
21:21:15 <danwent> #info There is a rough quantum schedule pushed to sched.org: http://www.openstack.org/summit/san-diego-2012/openstack-summit-sessions/
21:21:24 <danwent> #info: at the request of the people who are participating but mainly focused on the load-balancing, those sessions will all be on tues/wed
21:21:43 <danwent> some sessions needed to be squeezed to half-sessions
21:21:47 <danwent> for those, assume 20 minutes
21:21:52 <danwent> a full session is 40 minutes
21:22:07 <danwent> if you see your content scheduled as a full session, but think it might work as only a half-session, let me know
21:22:16 <danwent> its always nice to have scheduling flexibility.
21:22:39 <danwent> Also, there's no NEED to fill up all 40 minutes… its ok if you end early and we have some time to chat.
21:23:09 <danwent> the expectation is that if you are in charge of a session, you at least have an outline of what you'd like to discussion, and a set of goals about what you'd like to achieve by the end of the session.
21:23:53 <danwent> you'll want to reserve time at the end of the session for questions/discussion as well as a chance to identify the group of people who may be interested in coordinating on future work.
21:24:33 <danwent> a lot of people are sending me session presos / outlines for feedback.  That's cool and I'll try to respond, but its a lot of content to review, so apologies if I don't get back to you quickly.
21:24:50 <danwent> if you have a scheduling conflict, let me know ASAP.
21:25:07 <mestery> danwent: Do you need help spreading the review load?
21:25:10 <danwent> realize that there are main sessions (not just other design summit tracks) on tues/wed
21:25:47 <danwent> mestery: i actually encourage folks to send out proposals more broadly to the team for feedback… probably more efficient
21:26:12 <danwent> certainly doesn't hurt to have more eyeballs before the summit itself
21:26:16 <mestery> danwent: agreed, looking to free your cycles and spreading the load is #ftw
21:26:23 <salv-orlando> mestery, danwent: presentation could just be put on slideshare or any other public site before the summit - this will be useful for all attendees
21:26:37 <danwent> mestery: yeah, heaven forbid I should have time to think about my own sessions :P
21:26:46 <danwent> salv-orlando: that's a good idea.
21:27:11 <mestery> salv-orlando: Great idea for sure! And folks will want the slides post-summit anyways, so this is the way to go.
21:27:14 <danwent> salv-orlando: can you work to put together an etherpad as well?
21:27:34 <danwent> if peole could link to their slides on the etherpad, that would be nice
21:28:05 <danwent> there are a couple sessions that are technically "owned" by one person, but another person will be presenting.
21:28:22 <danwent> i'll be sending folks emails later this week to make it very clear who is presenting in those cases.
21:29:27 <danwent> ok… please get concerns about the schedule to me sometimes before start of day tuesday, so we can finalize the schedule
21:29:41 <danwent> and remember that no single schedule is going to make everyone happy...
21:30:08 <danwent> Ok, anything else on the summit?
21:30:25 <rkukura> danwent: did you schedule anything on extensions?
21:31:09 <danwent> unfortunately, the thursday deadline for scheduling new official sessions applies to everyone, including me, so I wasn't able to make an official new session.  I think i tacked it on to another session though, let me check
21:31:49 <danwent> salv-orlando: ah, i think we talked about that being a part of your API improvements session?
21:31:55 <salv-orlando> rkukura: it could be part of the API session
21:32:06 <salv-orlando> danwent: yep
21:32:10 <rkukura> ok
21:32:12 <danwent> yeah, i had added this: "Note: we will also discuss improvements to the internal DB model layer to better handle extensions. "
21:32:18 <salv-orlando> rkukura: happy to let you lead the discussion
21:32:27 <rkukura> maybe that small bit
21:32:51 <danwent> rkukura: another option would be stealing time from your module plugin slot, but I figured it was more API related, so I stuck it there
21:33:42 <rkukura> I'll put together a slide or two for the API session, or any other opportunity
21:33:45 <danwent> ok… also one note that there will be a quantum + horizon session on the horizon track
21:34:09 <danwent> and the first sesion (tempest + quantum) is subject to the availability of tempest folks, which I still need to confirm
21:34:16 <danwent> ok, anything else on summit schedule?
21:34:32 <nati_ueno> who owns' tempest+quantum session?
21:34:57 <nati_ueno> ah sorry
21:34:58 <danwent> nati_ueno: you do!
21:34:58 <nati_ueno> typo
21:35:00 <mnewby> you :)
21:35:09 <danwent> with help from mnewby :)
21:35:09 <nati_ueno> horizon + quantum session
21:35:15 <garyk> danwent: nati_ueno - it would be great if we can get dan prince in on this - he has smokestack running with nova.
21:35:18 <nati_ueno> Sorry I do owns the session
21:35:30 <garyk> this could be a great tool to test quantum running agents etc
21:35:45 <nati_ueno> My quantum was 'who own's horizon + quantum session ? '
21:36:02 <danwent> nati_ueno: akihiro was going to help with the horizon + quantum stuff, but others are welcomed to pitch in too.
21:36:03 <amotoki> nati_ueno: I can arrange it.
21:36:11 <nati_ueno> garyk: Thanks! I'll keep in touch with that
21:36:23 <garyk> nati_ueno: TX
21:36:28 <garyk> thanks
21:36:28 <nati_ueno> I implemented router pane. So I wanna demo it too
21:36:32 <nati_ueno> for horizon session
21:36:52 <danwent> nati_ueno: cool.  that's definitely one of the key areas to discuss
21:37:01 <danwent> ok, anything else on summit scheduling?
21:37:05 <sharis> danwent: I missed out on where to find the schedule - would like to schedule a short 20 mins for my preso
21:37:12 <nati_ueno> THis is poc https://github.com/nttmcl/horizon/tree/quantum-l3
21:37:47 <danwent> sharis: sorry, submission of new sessions has been closed since thurs.
21:37:55 <danwent> you should be able to grab some unconference time though
21:37:57 <sharis> ok
21:38:25 <nati_ueno> akihiro: OK I'll ping you later
21:38:43 <danwent> sharis: ping me and i'll see if there's a related session you may be able to fit into.
21:38:54 <sharis> ok. thx. will do.
21:38:55 <danwent> #topic open discussion
21:39:07 <arosen> for open discussion  nati_ueno and I have been working on the security group implementation which I'll upload shortly. These were targeted for folsom but were pushed out to grizzly.
21:39:09 <danwent> anyone?
21:39:26 <gongysh> any one on multi-host feature?
21:39:36 <zykes-> mini ish announcement for puppet folks: https://github.com/ekarlso/puppet-vswitch https://github.com/EmilienM/openstack-quantum-puppet
21:39:45 <danwent> gongysh: was going to cover that in the quantum/nova gaps section
21:39:49 <nati_ueno> I'm on multi-host
21:39:57 <danwent> i think nachi's "scheduler" session may touch on it as well.
21:39:59 <nati_ueno> danwent: Ah OK I got it
21:39:59 <zykes-> happy automagication with puppet for vswitches / quantum
21:40:20 <danwent> gongysh: if you want to talk about multi-host in particular though, I could give you a portion of of the quantum/nova gaps session
21:40:54 <danwent> ok, well, whomever is working on multi-host, let me know if you want to present on your thoughts during the quantum/nova gaps session
21:40:56 <gongysh> I will talk with nati_neno first
21:41:10 <danwent> gongysh: great… please cordinate and then ping me
21:41:15 <gongysh> ok
21:41:23 <danwent> i'm looking for anyone who wants to talk about metadata with overlapping Ips as well
21:41:31 <danwent> as that is another item we'll cover in that session
21:41:55 <danwent> ok, anything else?
21:42:19 <markmcclain> danwent: I'll take metadata
21:42:44 <danwent> #info we will NOT have an IRC meeting next week due to summit
21:43:04 <danwent> markmcclain: cool.  can you put together a few slides with thoughts on this?
21:43:17 <danwent> ok, thanks folks.  see you in person next week!
21:43:20 <danwent> #endmeeting