Thursday, 2014-10-02

*** hurgleburgler has quit IRC00:01
*** mikedillion has quit IRC00:04
*** cjellick has quit IRC00:08
*** mikedillion has joined #openstack-meeting-300:08
*** igordcard has quit IRC00:11
*** SridharRamaswamy has quit IRC00:12
*** ivar-laz_ has quit IRC00:24
*** ivar-lazzaro has joined #openstack-meeting-300:25
*** ivar-lazzaro has quit IRC00:25
*** ivar-lazzaro has joined #openstack-meeting-300:26
*** chuckC_ has quit IRC00:26
*** ivar-lazzaro has quit IRC00:28
*** ivar-lazzaro has joined #openstack-meeting-300:28
*** reed has quit IRC00:30
*** lcheng has quit IRC00:30
*** dconde has joined #openstack-meeting-300:34
*** ChuckC has quit IRC00:36
*** yamahata has quit IRC00:41
*** shwetaap has joined #openstack-meeting-300:45
*** mestery has quit IRC00:54
*** armax has left #openstack-meeting-300:57
*** yamamoto has joined #openstack-meeting-300:59
*** lcheng has joined #openstack-meeting-301:01
*** lcheng has quit IRC01:02
*** lcheng has joined #openstack-meeting-301:02
*** reed has joined #openstack-meeting-301:03
*** sarob is now known as sarob_away01:06
*** mikedillion has quit IRC01:08
*** ChuckC has joined #openstack-meeting-301:09
*** bpokorny has quit IRC01:11
*** bpokorny has joined #openstack-meeting-301:11
*** chuckC_ has joined #openstack-meeting-301:11
*** alexsyip has quit IRC01:12
*** SumitNaiksatam has quit IRC01:16
*** bpokorny has quit IRC01:16
*** yamahata has joined #openstack-meeting-301:26
*** ivar-lazzaro has quit IRC01:31
*** vkmc has joined #openstack-meeting-301:31
*** jacalcat has joined #openstack-meeting-301:36
*** lcheng has quit IRC01:37
*** lcheng has joined #openstack-meeting-301:38
*** shwetaap has quit IRC01:41
*** jamiehannaford has joined #openstack-meeting-301:42
*** lcheng has quit IRC01:42
*** jacalcat has left #openstack-meeting-301:43
*** yamamot__ has joined #openstack-meeting-301:54
*** reed has quit IRC01:55
*** yamamoto has quit IRC01:56
*** shwetaap has joined #openstack-meeting-301:57
*** amotoki has joined #openstack-meeting-302:03
*** eghobo has quit IRC02:11
*** shwetaap has quit IRC02:22
*** lcheng has joined #openstack-meeting-302:39
*** jamiehannaford has quit IRC02:43
*** pballand has quit IRC02:43
*** lcheng has quit IRC02:44
*** shwetaap has joined #openstack-meeting-302:53
*** flaviof_zzz is now known as flaviof02:53
*** vkmc has quit IRC02:59
*** lcheng has joined #openstack-meeting-302:59
*** yamamot__ has quit IRC03:01
*** zz_jgrimm is now known as jgrimm03:01
*** yamamoto has joined #openstack-meeting-303:02
*** sarob_away is now known as sarob03:09
*** shwetaap has quit IRC03:11
*** sarob is now known as sarob_away03:18
*** SumitNaiksatam has joined #openstack-meeting-303:24
*** sarob_away has quit IRC03:28
*** flaviof has quit IRC03:30
*** shwetaap has joined #openstack-meeting-303:56
*** carl_baldwin has joined #openstack-meeting-304:11
*** flaviof_zzz has joined #openstack-meeting-304:30
*** sarob_away has joined #openstack-meeting-304:31
*** lcheng has quit IRC04:55
*** lcheng has joined #openstack-meeting-304:55
*** lcheng has quit IRC05:00
*** SridharRamaswamy has joined #openstack-meeting-305:04
*** carl_baldwin has quit IRC05:05
*** sarob_away is now known as sarob05:06
*** jgrimm is now known as zz_jgrimm05:14
*** sarob is now known as sarob_away05:16
*** lcheng has joined #openstack-meeting-305:17
*** lcheng has quit IRC05:17
*** lcheng has joined #openstack-meeting-305:17
*** lcheng has quit IRC05:44
*** lhcheng has joined #openstack-meeting-305:46
*** lhcheng_ has joined #openstack-meeting-305:47
*** lhcheng has quit IRC05:50
*** Daisy has joined #openstack-meeting-305:50
*** Daisy has quit IRC05:51
*** lhcheng_ has quit IRC05:53
*** lhcheng has joined #openstack-meeting-305:53
*** lhcheng has quit IRC05:54
*** lhcheng has joined #openstack-meeting-305:56
*** mrunge has joined #openstack-meeting-306:01
*** shwetaap has quit IRC06:06
*** jtomasek has joined #openstack-meeting-306:07
*** lhcheng has quit IRC06:07
*** lhcheng has joined #openstack-meeting-306:07
*** flaper87|afk is now known as flaper8706:14
*** lhcheng has quit IRC06:15
*** lhcheng has joined #openstack-meeting-306:17
*** lhcheng has quit IRC06:29
*** lhcheng has joined #openstack-meeting-306:31
*** jtomasek has quit IRC06:33
*** SridharRamaswamy has quit IRC06:37
*** safchain has joined #openstack-meeting-306:44
*** pkoniszewski has joined #openstack-meeting-306:48
*** lhcheng has quit IRC06:49
*** lhcheng has joined #openstack-meeting-306:50
*** lhcheng has quit IRC06:55
*** yamamoto has quit IRC06:58
*** ttrifonov_zZzz is now known as ttrifonov07:07
*** matrohon has joined #openstack-meeting-307:08
*** MaxV has joined #openstack-meeting-307:27
*** Daisy has joined #openstack-meeting-307:28
*** yamamoto_ has joined #openstack-meeting-307:28
*** jcoufal has joined #openstack-meeting-307:29
*** yamamoto_ has quit IRC07:36
*** iovadia has joined #openstack-meeting-307:37
*** SUNGJINKANG has joined #openstack-meeting-307:58
*** jamiehannaford has joined #openstack-meeting-307:59
*** SUNGJINKANG has quit IRC07:59
*** ujuc has joined #openstack-meeting-307:59
*** ujuc has quit IRC08:00
*** ujuc has joined #openstack-meeting-308:00
*** ujuc has left #openstack-meeting-308:01
*** lsmola has joined #openstack-meeting-308:02
*** mfer has joined #openstack-meeting-308:04
*** yamamoto_ has joined #openstack-meeting-308:05
*** mfer has quit IRC08:09
*** yamamoto_ has quit IRC08:12
*** flaper87 is now known as flaper87|afk08:25
*** yamamoto_ has joined #openstack-meeting-308:43
*** yamamoto_ has quit IRC08:48
*** alexpilotti has joined #openstack-meeting-308:51
*** Daisy has quit IRC08:54
*** flaper87|afk is now known as flaper8708:59
*** zz_johnthetubagu is now known as johnthetubaguy09:08
*** yamamoto has joined #openstack-meeting-309:19
*** Longgeek has joined #openstack-meeting-309:22
*** Longgeek has quit IRC09:22
*** Longgeek has joined #openstack-meeting-309:24
*** Longgeek has quit IRC09:26
*** yamamoto has quit IRC09:27
*** Longgeek has joined #openstack-meeting-309:28
*** sarob_away is now known as sarob09:29
*** jtomasek has joined #openstack-meeting-309:31
*** Longgeek_ has joined #openstack-meeting-309:39
*** sarob is now known as sarob_away09:41
*** Longgeek has quit IRC09:42
*** yamahata has quit IRC10:31
*** yamahata has joined #openstack-meeting-311:30
*** yamahata has quit IRC11:39
*** yamahata has joined #openstack-meeting-311:40
*** Daisy has joined #openstack-meeting-311:45
*** Daisy has left #openstack-meeting-311:54
*** jacalcat has joined #openstack-meeting-312:05
*** Munish_ has joined #openstack-meeting-312:15
*** jacalcat has left #openstack-meeting-312:16
*** vkmc has joined #openstack-meeting-312:18
*** vkmc has quit IRC12:18
*** vkmc has joined #openstack-meeting-312:18
*** Adri2000 has quit IRC12:43
*** Adri2000 has joined #openstack-meeting-312:47
*** Adri2000 is now known as Guest1081112:47
*** vkmc has quit IRC12:51
*** vkmc has joined #openstack-meeting-312:52
*** jacalcat has joined #openstack-meeting-313:05
*** jacalcat has left #openstack-meeting-313:05
*** alexpilotti has quit IRC13:27
*** pkoniszewski has quit IRC13:33
*** nelsnelson has joined #openstack-meeting-313:34
*** igordcard has joined #openstack-meeting-313:39
*** mfer has joined #openstack-meeting-313:41
*** sigmavirus24_awa is now known as sigmavirus2413:49
*** amotoki has quit IRC13:50
*** amotoki has joined #openstack-meeting-313:51
*** sarob_away has quit IRC13:52
*** flaviof_zzz has quit IRC13:52
*** Guest10811 is now known as Adri200013:58
*** Adri2000 has joined #openstack-meeting-313:58
*** salv-orlando has quit IRC13:58
*** pkoniszewski has joined #openstack-meeting-314:01
*** thangp has joined #openstack-meeting-314:04
*** woodm1979 has joined #openstack-meeting-314:06
*** mestery has joined #openstack-meeting-314:07
*** mestery has quit IRC14:20
*** sandr8 has quit IRC14:22
*** mrunge has quit IRC14:23
*** mrunge has joined #openstack-meeting-314:24
*** gholler has joined #openstack-meeting-314:27
*** flaviof_zzz has joined #openstack-meeting-314:29
*** thinrichs has joined #openstack-meeting-314:31
*** otherwiseguy has joined #openstack-meeting-314:32
*** david-lyle has joined #openstack-meeting-314:37
*** hurgleburgler has joined #openstack-meeting-314:39
*** marun has joined #openstack-meeting-314:39
*** jacalcat has joined #openstack-meeting-314:39
*** carl_baldwin has joined #openstack-meeting-314:40
*** tteggel has quit IRC14:44
*** sarob_away has joined #openstack-meeting-314:45
*** tteggel has joined #openstack-meeting-314:46
*** jschwarz has joined #openstack-meeting-314:47
*** zz_jgrimm is now known as jgrimm14:48
*** mrunge has quit IRC14:49
*** armax has joined #openstack-meeting-314:50
*** jrist has quit IRC14:53
*** pkoniszewski has quit IRC14:54
*** devvesa has joined #openstack-meeting-314:56
*** lhcheng has joined #openstack-meeting-314:56
*** pkoniszewski has joined #openstack-meeting-314:56
*** tidwellr has joined #openstack-meeting-314:56
*** reed has joined #openstack-meeting-314:56
*** tidwellr has quit IRC14:57
*** tidwellr has joined #openstack-meeting-314:58
*** cjellick has joined #openstack-meeting-314:59
carl_baldwinhi all14:59
*** woodm1979 has left #openstack-meeting-314:59
devvesahi carl_badwin15:00
armaxyello15:00
carl_baldwindevvesa: hi15:00
*** pcm__ has joined #openstack-meeting-315:00
carl_baldwinarmax: hi15:00
pcm__hi15:00
carl_baldwinpcm__: hi15:00
carl_baldwinamuller, safchain: ping15:01
safchainhi15:01
carl_baldwinyamamoto: ping15:01
carl_baldwinI’m sure I’m leaving some out.  Sorry.15:01
carl_baldwin#startmeeting neutron_l315:01
openstackMeeting started Thu Oct  2 15:01:54 2014 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:01
openstackThe meeting name has been set to 'neutron_l3'15:01
carl_baldwin#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:02
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam#Agenda15:02
carl_baldwinI don’t know yet if RC1 has been cut.  Anyone know for sure?15:02
*** pawels has joined #openstack-meeting-315:03
armaxcarl_baldwin: not yet but we should be in lock down mode now15:03
armaxcarl_baldwin: so that ttx and mestery can do it15:03
*** seizadi has joined #openstack-meeting-315:03
armax#link https://launchpad.net/neutron/+milestone/juno-rc115:03
carl_baldwinarmax: Makes sense.  I know there were a few bug fixes they had their eye on last night.15:03
armaxnothing else should be approved at this point15:04
armaxcarl_baldwin: afaik we’re the last project standing ;)15:04
carl_baldwinYeah, it looks like all of the bugs are marked “fix committed”.  Shouldn’t be long then.15:04
carl_baldwin#topic Bugs15:05
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:05
*** bpokorny has joined #openstack-meeting-315:05
*** cjellick has quit IRC15:05
carl_baldwinActually, the subteam bugs are looking pretty good.  I have gotten behind on triage though.15:05
*** cjellick has joined #openstack-meeting-315:06
carl_baldwinAre there any bugs that need to be brought up?15:06
carl_baldwin#action carl_baldwin will triage new bugs this week15:06
carl_baldwinAt Swami’s request, I’m going to move the DVR report to later in the meeting.15:07
carl_baldwin#topic l3-high-availability15:08
*** openstack changes topic to "l3-high-availability (Meeting topic: neutron_l3)"15:08
carl_baldwinamuller, safchain:  What is the news here?15:08
safchainI submitted a fix about a potential lock wait15:09
safchainhttps://review.openstack.org/#/c/124408/15:09
ttxarmax: I need mestery to approve https://review.openstack.org/#/c/125081/15:09
safchainnothing else this week15:10
ttxthen I branch from there15:10
armaxttx: I’ll reach out to him15:10
carl_baldwinsafchain: I did notice that as a new bug.15:10
ttxI already sent him an email15:10
*** salv-orlando has joined #openstack-meeting-315:11
*** amuller has joined #openstack-meeting-315:11
carl_baldwinsafchain: anything else?  How about reviews in progress?15:11
amullerSorry I'm late =/15:11
safchaincarl_baldwin, that is the only one I have about the HA15:12
carl_baldwinamuller: hi15:12
amullerworking on https://bugs.launchpad.net/neutron/+bug/136545315:12
amullersome patches up15:12
amullerearly feedback is welcome15:12
amullermore patches on the way15:13
jschwarzcarl_baldwin, I'm also working with amuller on the HA functional tests patch15:14
*** lhcheng has quit IRC15:14
carl_baldwinamuller: I will have a look at them.15:14
carl_baldwinjschwarz: do you have a link?15:14
jschwarzit's on hold until some 4 minor patches gets through that the functional tests require (123434, 124752)15:15
jschwarzthe functional tests patch is https://review.openstack.org/#/c/117994/15:15
*** lhcheng has joined #openstack-meeting-315:15
jschwarzafter these are done we'll go on to writing the integration tests framework (there are some patches there also but they can wait)15:16
carl_baldwinjschwarz: I will have a look at those.  117994 was on my radar but the other two somehow were not on there yet.15:17
carl_baldwinAnything else for L3 HA?15:18
jschwarzcarl_baldwin, quite alright since we were waiting for RC1 to push them anyway :)15:18
amullerNothing on my end15:18
*** lhcheng has quit IRC15:18
*** pkoniszewski has quit IRC15:19
*** lhcheng has joined #openstack-meeting-315:19
carl_baldwinThanks, all.15:19
carl_baldwin#topic bgp-dynamic-routing15:20
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:20
carl_baldwindevvesa: ping15:20
devvesahi15:20
carl_baldwinYou have posted the spec against Kilo.15:20
devvesayes15:20
carl_baldwindo you have a link handy?15:21
*** alexpilotti has joined #openstack-meeting-315:21
carl_baldwinFound it.15:21
carl_baldwin#link https://review.openstack.org/#/c/125401/15:21
devvesaoh, 2 seconds faster than me :)15:21
carl_baldwin:)15:21
devvesaI've read your comments15:22
carl_baldwinI wrote them late, I hope they make sense.15:22
devvesaThe first one about register the gateway router as a neutron router makes me think a lot15:22
devvesaI think is a great idea, but it is too early to express my crazy conclusions15:23
carl_baldwinthat comment came out of my thoughts to associate advertisedroutes with a router.  Those, in turn, came from my thoughts about advertising floating ips which are already associated with a router.15:23
*** lhcheng has quit IRC15:24
carl_baldwinCould we find some time early next week to discuss it more?15:24
devvesaanytime15:24
carl_baldwinI’ll be in touch.  Until then, we can add discussion to the proposed blueprint.15:25
devvesaI'm starting to think that we may not a new kind of agent, but extend the l3 one15:25
devvesathat will apply to some 'edge' routers15:25
carl_baldwinThat sounds like a whole discussion in itself but I think I see where you’re going.  Let’s discuss more outside the meeting and then work it in to the proposal.15:26
devvesas/may not /may not need15:26
devvesagreat15:26
carl_baldwindevvesa: Anything else?15:27
devvesaNothing else from me15:28
carl_baldwindevvesa: Thanks.15:28
carl_baldwin#topic L3 Agent cleanup, refactoring, and possible restructuring.15:29
*** Swami has joined #openstack-meeting-315:29
*** openstack changes topic to "L3 Agent cleanup, refactoring, and possible restructuring. (Meeting topic: neutron_l3)"15:29
carl_baldwinamuller: still there?15:29
amulleryeppers15:29
carl_baldwinI know you mentioned some interest here.15:29
Swamicarl_baldwin: hi15:29
amullerI did15:30
carl_baldwinSwami: hi, welcome.15:30
Swamimike smith was also interested in the this topic15:30
carl_baldwinmrsmith: ping15:30
Swamimike is away today and will not be able to join15:30
*** bpokorny has quit IRC15:30
carl_baldwinSwami: Right, he’s still out.  I knew that.15:30
carl_baldwinSwami: I’ll bring him in the loop here when he’s back.15:30
*** jrist has joined #openstack-meeting-315:30
Swamiok15:30
carl_baldwinI got started looking at the l3 agent yesterday.  Some low hanging fruit popped out quickly that I will post for review when I’ve run tests.  But, I haven’t really gotten to the meat of the project.15:32
*** pballand has joined #openstack-meeting-315:32
amullerI gave it a fair bit of thought, trying to find a design pattern that would fit the requirements and would get rid of the endless if ha, if distributed conditions. I don't have anything too concrete. It's difficult to design something like this without trying it out in limited scale. Also, we have to consider a router that's both HA and distributed, which the code doesn't support right now.15:32
amullerSo while it makes sense to refactor the code before we enable HA + DVR routers, it makes it more difficult15:32
Swamiamuller: In the case of the distributed routers, the HA is only valid for the snat scenario.15:33
amullercorrect15:33
SwamiSo we can't tie the HA to the routers by itself.15:33
carl_baldwinSwami: makes sense15:33
amullerIf someone comes up with a concrete suggestion we can schedule a video chat over it15:35
SwamiIn this case we have rely on the l3_agent mode and if it is running in dvr_snat mode and if HA is enabled for a router that has snat enabled, then we have to apply the HA for the snat for the dvr_snat nodes.15:35
carl_baldwinamuller: Swami:  I’d like to be iterative on this.  Hopefully, we can get some early work in the review/merge queue soon and make continual progress toward goodness.  However, it will make sense to have an end goal in mind.15:35
amullerI suspect the earliest would be at Paris15:35
Swamiamuller: let us work together to come out with a plan for the HA with distributed router support15:36
carl_baldwinWhat will be the best way to collaborate on the overall goal?15:36
carl_baldwinWiki?  etherpad?15:36
carl_baldwinSomething else?15:36
SwamiDo we want to start with a design doc that states the flows and makes sure everyone is on the same page.15:37
amullerAhh, 1 point I wanted to make, is that HA routers have functional testing, so I'm pretty confident in butchering the l3 agent code without ruining something basic. I'd love it if someone could implement functional testing for distributed routers before we make major changes to the agent.15:37
SwamiWiki would be a fine.15:37
pcm__Was wondering if there was info on the goals - for the uninitiated15:37
*** bpokorny has joined #openstack-meeting-315:37
*** sigmavirus24 has left #openstack-meeting-315:38
carl_baldwinpcm__: I fear that different people may have different goals in mind.15:38
pcm__carl_baldwin: sounds like a good first step is to come to consensus on goals15:39
Swamicarl_baldwin: I will create a wiki for the DVR and HA15:39
SwamiJust to capture all our thoughts in a single page.15:40
carl_baldwinI’d like to arrive at a sensible architecture which allows different types of routers, DVR, HA, DVR + HA and works in FWaaS without all of the special cases we have sprinkled throughout the code.  Better use of inheritence and composition than there is now.15:40
amullercarl_baldwin: I think we have the same idea. I'd like to support all 4 permutations of routers (legacy, HA, DVR, both) via inheritence and composition, without conditionals all over the place.15:41
carl_baldwinThe agent needs to be split up too.  The one class in one file is doing too much.  We need some clean separation of concerns.15:42
amullerAlso, the 'RouterInfo' class as it is is just a struct with no meat15:42
amullerand the agent has all the brains15:42
carl_baldwinamuller: Agreed 100% about RouterInfo.  I was looking at it last night.15:42
amullerthe agent should be orchestrating, and routers should be configuring themselves15:42
carl_baldwinamuller: yes.  My thoughts are along the same lines.15:42
amulleralso the way we have RouterInfo hold a 'router' attribute in it, which is the one in the update, but the other attributes of RouterInfo are the 'old' routers...15:42
amullerholy crap that's awful15:42
carl_baldwinawful only begins to describe it.15:43
amullerWe should have two 'Router' instances, one is the 'old' one that the agent has, and one is the 'new' one in the update15:43
amullerRouters should be able to diff themselves15:43
amullerfigure out what's changed15:43
*** pawelss has joined #openstack-meeting-315:43
* haleyb likes this suggestion to not have conditionals everywhere15:44
carl_baldwinI do want to stress an iterative approach with this.  Learning from history, if we make this effort too monolithic, it will likely not be merged in this cycle (maybe never).15:44
amullerLuckily there's so much crap to change it shouldn't be a problem doing it piece by piece :)15:45
pcm__Right now FW is a superclass, and VPN a subclass of L3 agent too. Seems messy15:45
*** pawels has quit IRC15:45
*** shwetaap has joined #openstack-meeting-315:45
*** jcoufal has quit IRC15:45
carl_baldwinpcm__: Yes, not the best use of inheritence.  We’ll need to evaluate that and decide what a better pattern will be.15:45
*** yamahata has quit IRC15:46
carl_baldwinThese notes should get us started.  Let’s translate them to the wiki page and keep the discussion going.  Right now, though, we’ve got a little more to get to in this meeting.15:46
carl_baldwinIs everyone okay if I move on to another topic?15:46
*** yamahata has joined #openstack-meeting-315:47
pcm__+1. good stuff though.15:47
carl_baldwin#topic neutron-ovs-dvr15:48
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:48
carl_baldwinSwami: I moved dvr to later to accomodate.15:48
carl_baldwinSwami: what do you have for us?15:48
Swamicarl_baldwin: thanks for getting the dvr later.15:49
SwamiRight now we are working on fixing bugs and working on back_log items.15:49
SwamiThere are patches out there for review15:49
Swamirouter_migration patch is out there for review.15:50
Swami#link https://review.openstack.org/#/c/105855/15:50
Swami#link https://review.openstack.org/#/c/123273/15:50
SwamiThese two patches addresses the migration of legacy routers to distributed routers.15:51
*** thinrichs has left #openstack-meeting-315:51
carl_baldwinSwami: Thanks for the links.15:51
*** pawels has joined #openstack-meeting-315:52
SwamiThere is a "DB lockwait issue" with DVR delete_ports which I am trying to fix.15:52
*** dconde has joined #openstack-meeting-315:53
SwamiBut this one I thin carl you have already reviewed it.15:53
carl_baldwinSwami: Is there a bug for that?  Do you have a link handy?15:53
Swamis/thin/think15:53
SwamiI will check it out, I don't think there was a bug on the launchpad, if not I will create one.15:53
carl_baldwinI do recall seeing the patch but I can’t find it in the bugs.  When you create it, be sure it has the dvr tag on it.  I’ll watch for it.15:54
SwamiThe problem is occassionally we see a "db lockwait timeout" when we clear snat or remove an interface.15:54
*** pawelss has quit IRC15:54
Swami#link https://review.openstack.org/#/c/124849/15:55
SwamiIn both cases it is caused when "delete_port" is called from delete_csnat_router_interface.15:55
carl_baldwinSwami: Thanks for the link.  That one needs a bit more discussion.15:55
SwamiI will work on today to see if there is any other way to fix this problme.15:56
carl_baldwinAlso, a rebase because half of it was merged in to RC1.15:56
Swamibecause I do see even in delete port, there are rpc calls from within the db transaction for the l2pop mechanism drivers.15:56
carl_baldwinCould you point them out?  There are some we’ve been looking at.  I’d be interested to know if you’ve found some that I haven’t seen yet.15:57
SwamiI will keep you posted if I find anything concrete.15:57
carl_baldwinMaybe you could reference them in the review or in the bug report that you create.15:57
*** bpokorny_ has joined #openstack-meeting-315:58
SwamiAlso there was a patch that was abandoned that we did for VPN.15:58
carl_baldwinSwami: Anything else?15:58
SwamiSo I am also working on fixing the VPN with DVR.15:58
SwamiI am almost halfway through, once I have the patch I will post a quick WIP for review.15:58
Swamithat's all from me.15:58
carl_baldwinSwami: Thanks for the update.15:59
carl_baldwin#topic Open Discussion15:59
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:59
carl_baldwinWe have 45 seconds…  :)15:59
carl_baldwinThanks everyone.  We got a lot accomplished in Juno and I’m looking forward to improving on it and getting more accomplished in Kilo.16:00
carl_baldwinUntil next time.16:00
carl_baldwin#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu Oct  2 16:00:30 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
*** pcm__ has left #openstack-meeting-316:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-10-02-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-10-02-15.01.txt16:00
*** devvesa has quit IRC16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-10-02-15.01.log.html16:00
amullerThanks Carl :)16:00
amullerThanks everyone, ttyl16:01
*** bpokorny has quit IRC16:01
*** seizadi has quit IRC16:02
*** matrohon has quit IRC16:03
*** carl_baldwin has quit IRC16:11
*** sarob_away is now known as sarob16:17
*** lhcheng has joined #openstack-meeting-316:18
*** iovadia has quit IRC16:20
*** pballand has quit IRC16:21
*** MaxV has quit IRC16:23
*** sandr8 has joined #openstack-meeting-316:23
*** pawelss has joined #openstack-meeting-316:25
*** AndChat-656304 has joined #openstack-meeting-316:25
*** sarob is now known as sarob_away16:26
*** sandr8 has quit IRC16:28
*** pawels has quit IRC16:29
*** pawelss has quit IRC16:29
*** alexpilotti has quit IRC16:32
*** carl_baldwin has joined #openstack-meeting-316:43
*** s3wong has joined #openstack-meeting-316:46
*** safchain has quit IRC16:47
*** lsmola has quit IRC16:48
*** jtomasek has quit IRC16:48
*** carl_baldwin has quit IRC16:49
*** lhcheng has quit IRC16:50
*** lhcheng has joined #openstack-meeting-316:50
*** alexpilotti has joined #openstack-meeting-316:51
*** lhcheng_ has joined #openstack-meeting-316:52
*** lhcheng__ has joined #openstack-meeting-316:52
*** lhcheng has quit IRC16:55
*** tidwellr has left #openstack-meeting-316:55
*** lhcheng_ has quit IRC16:56
*** Longgeek_ has quit IRC16:57
*** lhcheng__ has quit IRC16:58
*** lhcheng has joined #openstack-meeting-316:58
*** lhcheng_ has joined #openstack-meeting-317:00
*** lhcheng has quit IRC17:03
*** jschwarz has quit IRC17:09
*** ivar-lazzaro has joined #openstack-meeting-317:09
*** armax has quit IRC17:10
*** jrist has quit IRC17:10
*** ivar-lazzaro has quit IRC17:10
*** ivar-lazzaro has joined #openstack-meeting-317:11
*** mestery has joined #openstack-meeting-317:11
*** yamahata has quit IRC17:14
*** armax has joined #openstack-meeting-317:14
*** kashyap has joined #openstack-meeting-317:18
*** pkoniszewski has joined #openstack-meeting-317:21
*** bpokorny has joined #openstack-meeting-317:23
*** bpokorny_ has quit IRC17:26
*** amuller has quit IRC17:26
*** igordcard has quit IRC17:28
*** ndipanov has quit IRC17:32
*** david-lyle has quit IRC17:35
*** kashyap has quit IRC17:37
*** rkukura has joined #openstack-meeting-317:37
*** mestery has quit IRC17:44
*** terryw has joined #openstack-meeting-317:47
*** otherwiseguy has quit IRC17:48
*** bpokorny has quit IRC17:48
*** bpokorny has joined #openstack-meeting-317:51
*** seizadi has joined #openstack-meeting-317:56
*** rms_13 has joined #openstack-meeting-317:57
*** johnthetubaguy is now known as zz_johnthetubagu17:59
*** AndChat-656304 has quit IRC17:59
SumitNaiksatamhi17:59
*** mestery has joined #openstack-meeting-318:00
*** ctracey_ has joined #openstack-meeting-318:00
*** pkoniszewski has quit IRC18:00
s3wonghello18:00
SumitNaiksatamrkukura: s3wong ivar-lazzaro kevinbenton: there?18:01
SumitNaiksatams3wong: hi18:01
ivar-lazzaroSumitNaiksatam: hi18:01
*** ctracey_ is now known as ctracey18:01
SumitNaiksatamokay lets get started18:01
SumitNaiksatam#startmeeting networking_policy18:01
openstackMeeting started Thu Oct  2 18:01:41 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: networking_policy)"18:01
openstackThe meeting name has been set to 'networking_policy'18:01
SumitNaiksatam#info agenda: https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy18:01
SumitNaiksatambanix mentioned earlier that he cannot make it due to personal reasons18:02
SumitNaiksatamhope everything is fine at his end18:02
s3wongyes, banix will likely miss some more meetings, and possibly the K-Summit18:02
*** sigmavirus24 has joined #openstack-meeting-318:03
SumitNaiksatam#chairs s3wong ivar-lazzaro ivar-lazzaro rms_13 rkukura kevinbenton18:03
rms_13Hi18:03
SumitNaiksatam#topic StackForge Process18:03
*** openstack changes topic to "StackForge Process (Meeting topic: networking_policy)"18:03
SumitNaiksatamso i believe most of us have been pretty busy either pushing code to the stackforge repos or reviewing the patches18:04
SumitNaiksatamjust wanted to take a minute here to make sure that everyone is in sync with the process we are following18:05
SumitNaiksatamessentially the process is that same as was with Neutron or any other OpenStack project18:05
*** david-lyle has joined #openstack-meeting-318:06
SumitNaiksatamwe create the blueprint in Launchpad: #link https://launchpad.net/group-based-policy18:06
SumitNaiksatamthen submit a spec for review in gerrit: #link http://git.openstack.org/cgit/stackforge/group-based-policy-specs18:06
SumitNaiksatamonce spec is reviewed, approved and merged, we push patches for review: #link http://git.openstack.org/cgit/stackforge/group-based-policy18:07
SumitNaiksatammake sure you mention the blueprint ID in the implementation patches18:07
*** LouisF has joined #openstack-meeting-318:07
*** jrist has joined #openstack-meeting-318:07
SumitNaiksatamalso, bugs should be reported here: #link https://bugs.launchpad.net/group-based-policy18:07
SumitNaiksatamthere is no deviation from the standard process, just need to be aware of the relevant launchpad projects and the git repos18:08
SumitNaiksatamany questions?18:08
ivar-lazzaroSumitNaiksatam: great!18:09
s3wongSumitNaiksatam: sounds good18:09
rms_13SumitNaiksatam: Thanks for the recap18:09
SumitNaiksatamivar-lazzaro: thanks for boostrapping the gbp repo!18:09
rms_13Good stuff18:09
SumitNaiksatamrms_13: s3wong: sure18:09
SumitNaiksatam#topic Summary of relevant links for code and specs18:10
*** openstack changes topic to "Summary of relevant links for code and specs (Meeting topic: networking_policy)"18:10
SumitNaiksatamI have been trying to capture everything in this one page: #link https://wiki.openstack.org/wiki/GroupBasedPolicy/StackForge/repos18:10
SumitNaiksatamplease feel free to edit and/or correct18:10
*** david-lyle has quit IRC18:10
SumitNaiksatamthe idea was to provide a dashboard kind of a view18:10
SumitNaiksatamsince we have a number of repos to deal with18:11
SumitNaiksatamthat brings to the next topic on reviews18:11
SumitNaiksatam#topic Patches in review18:11
*** openstack changes topic to "Patches in review (Meeting topic: networking_policy)"18:11
SumitNaiksatam#link https://review.openstack.org/#/q/status:open+project:stackforge/group-based-policy+branch:master,n,z18:11
SumitNaiksatamwe have a large number of patches in review now18:12
SumitNaiksatamalso the above link is for the server side patches18:12
*** dconde has quit IRC18:12
SumitNaiksatamthere are patches in review in the client heat and horizon as well18:12
*** mestery has quit IRC18:12
SumitNaiksatamrequesting you to please review the patches at the earliest18:12
SumitNaiksatamanything that we need to discuss about the current patches?18:13
s3wongSumitNaiksatam: no cli patches?18:14
SumitNaiksatamyeah, see my earlier comment :-)18:14
SumitNaiksatams3wong: cli patches: #link https://review.openstack.org/#/q/status:open+project:stackforge/group-based-policy-client+branch:master,n,z18:14
s3wongSumitNaiksatam: which is "none"18:15
SumitNaiksatamdoh!18:15
SumitNaiksatamnot sure what happened there18:15
SumitNaiksatams3wong: corrected link: #link https://review.openstack.org/#/q/status:open+project:stackforge/python-group-based-policy-client+branch:master,n,z18:16
SumitNaiksatami will fix the wiki (repo name was wrong)18:16
SumitNaiksatami need to fix the UTs on this patch18:16
s3wongSumitNaiksatam: cool --- that makes more sense. Hard to believe we have Heat and Horizon patches but no neutron-python-client :-)18:17
SumitNaiksatams3wong: :-) yeah my bad18:17
SumitNaiksatami spent quite a bit of time on this, but still the UTs are failing18:17
SumitNaiksatamthe issue is with trying to eliminate duplication code from neutron client18:17
SumitNaiksatamanyway18:17
SumitNaiksatamany thoughts questions on the reviews?18:18
*** jacalcat has left #openstack-meeting-318:18
SumitNaiksatamokay moving on18:18
SumitNaiksatamour favorite topic -18:19
*** hemanthravi has joined #openstack-meeting-318:19
SumitNaiksatam#topic Resource renaming - finalize18:19
*** openstack changes topic to "Resource renaming - finalize (Meeting topic: networking_policy)"18:19
LouisFSumitNaiksatam: did you see my comments on groupbasedpolicy.py?18:19
SumitNaiksatam#undo18:19
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x27f2cd0>18:19
SumitNaiksatamLouisF: on the client?18:19
LouisFyes18:19
SumitNaiksatamLouisF: i did notice that you had commented, however i was caught up with fixing the UT issue18:20
LouisFSumitNaiksatam: ok18:20
SumitNaiksatamLouisF: i mean to address the comments after i get the UTs to run18:20
SumitNaiksatamLouisF: apologies for the delay18:20
LouisFSumitNaiksatam: np18:20
SumitNaiksatamLouisF: and thanks for the review18:20
SumitNaiksatam: #topic Resource renaming - finalize18:20
SumitNaiksatam#topic Resource renaming - finalize18:21
*** openstack changes topic to "Resource renaming - finalize (Meeting topic: networking_policy)"18:21
SumitNaiksatamso to recap, in this meeting we had earlier agreed to rename Endpoint -> Policy Target, and Endpoint Group -> Policy Target Group18:21
SumitNaiksatamthere are a couple of other changes that were proposed in the past, and we discussed last week18:22
LouisFSumitNaiksatam: +118:22
SumitNaiksatamContract -> Policy Rule Set18:22
s3wongSumitNaiksatam: oops, I just merged the API-1 patch without these terminology/naming changes :-)18:22
*** sigmavirus24 has left #openstack-meeting-318:22
SumitNaiksatam* Contract -> Policy Rules Set18:22
SumitNaiksatams3wong: no worries18:22
ivar-lazzaros3wong: it's ok, I think it's better to apply those changes on top anyway18:22
SumitNaiksatams3wong: we did not mean to change the names right away18:22
SumitNaiksatamivar-lazzaro: +118:22
SumitNaiksatamand Policy Labels -> Policy Tags18:23
s3wongSumitNaiksatam, ivar-lazzaro: sure :-)  I didn't expect them anyway18:23
SumitNaiksatamso anyone object to Policy Rules Set, and Policy Tags ?18:23
LouisFSumitNaiksatam: I preferred contract18:23
SumitNaiksatamLouisF: okay, and i know rkukura preferred that as well18:24
s3wongSumitNaiksatam: so do I18:24
*** sandr8 has joined #openstack-meeting-318:24
SumitNaiksatamLouisF: however lots of people also prefer Policy Rule Set, their justification being that since Contract is a collecton of Policy Rules, so Policy Rules Set is more intuitive18:25
SumitNaiksatams3wong: ^^^18:25
SumitNaiksatamto some extent we also socialized this new terminology in the Policy Summit18:25
s3wongthough Policy-Rules-Set gives rkukura another chance to make another acronym in PRS18:25
SumitNaiksatamand i did not hear any pushback18:25
SumitNaiksatams3wong: absolutely! :-)18:26
SumitNaiksatamfor the record, i personally prefer our older terminology, but anyway18:26
SumitNaiksatamso i understand that we have preferences, but is there any objection to Policy Rule Set and Policy Tags?18:26
LouisFSumitNaiksatam: i'm ok if that is a majority decision18:27
*** david-lyle has joined #openstack-meeting-318:27
SumitNaiksatamokay so can we have a show of hands at least here, if people are okay with the renaming?18:27
SumitNaiksatamivar-lazzaro: rms_13 hemanthravi ?18:27
SumitNaiksatams3wong: ?18:27
rms_13Fine by me18:28
ivar-lazzaroSumitNaiksatam: +118:28
hemanthraviok with me18:28
SumitNaiksatamsandr8: ;-P18:28
s3wongSumitNaiksatam: I am OK with it --- just finalize so we don't do this over again :-)18:28
SumitNaiksatams3wong: exactly, we cant be in this limbo, since we have quite a few things to catch up on in terms of implementation18:29
*** sandr8 has quit IRC18:29
LouisFSumitNaiksatam: contract is a stronger concept than prs18:30
SumitNaiksatamLouisF: agree18:30
SumitNaiksatamLouisF: would you strongly object to PRS though?18:30
LouisFjust a -118:31
SumitNaiksatamLouisF: :-)18:31
SumitNaiksatamokay lets do this, lets send this out to the ML today, and see if anyone has objections, and if not we can roll with this (perhaps a bit reluctantly)18:32
SumitNaiksatamLouisF: sound okay?18:32
LouisFSumitNaiksatam: ok18:32
SumitNaiksatamokay thanks all18:32
*** dconde has joined #openstack-meeting-318:33
s3wongend of meeting already?18:33
*** mestery has joined #openstack-meeting-318:34
ivar-lazzaros3wong: the end of the model renaming discussion is a great milestone per se :)18:34
SumitNaiksatam#agreed tentative agreement in the team to rename resources to Policy Rules Set and Policy Tags (will move forward if there are no further major objections)18:34
SumitNaiksatamivar-lazzaro: :-)18:34
s3wongivar-lazzaro: well, i see a "thanks all" -- which is usually an indicator that the meeting is over :-)18:34
SumitNaiksatambtw, i think based on the merging of the first patch, we seemed to have decided that we will implement the renaming as a follow up18:35
SumitNaiksatams3wong: ivar-lazzaro: good catch :-) , we still have a few more agenda items18:35
s3wongSumitNaiksatam: my apology as I was the one giving it the second +2 (and workflow +1) :-)18:35
SumitNaiksatams3wong: no worries, that was actually the thinking (at least in my mind)18:36
s3wongSumitNaiksatam: though I did put a question there somewhere asking if we want to do renaming on the patch18:36
SumitNaiksatams3wong: so no harm done18:36
*** jamiehannaford has quit IRC18:36
SumitNaiksatams3wong: Subrah had put the question18:36
SumitNaiksatami saw that18:36
SumitNaiksatam#topic Cross project dependency on neutron package18:37
*** openstack changes topic to "Cross project dependency on neutron package (Meeting topic: networking_policy)"18:37
SumitNaiksatamso the issue is that we are currently referring to a neutron package in our requirements18:37
SumitNaiksatamand this is currently in the form of a pypi package that ivar-lazzaro has created18:37
SumitNaiksatamrkukura had suggested that we replace this with a pointer to the neutron repo18:37
SumitNaiksatamhowever, ivar-lazzaro tried it but couldnt get it to work18:38
SumitNaiksatamivar-lazzaro: please correct me if i am wrong, just trying to quickly summarize here18:38
SumitNaiksatambeyond that, my suggested is to actually remove this from the requirements.txt and put it in the test-requriements.txt18:39
SumitNaiksatamor else it breaks the devstack install18:39
ivar-lazzaroSumitNaiksatam: I think moving the requirement in test-requirements should be fine as long as neutron is installed always before GBP18:39
ivar-lazzaroSumitNaiksatam: which will happen anyway18:39
SumitNaiksatamivar-lazzaro: true18:39
ivar-lazzaroSumitNaiksatam: so if everyone is fine I'll go ahead and change it18:39
*** pkoniszewski has joined #openstack-meeting-318:40
SumitNaiksatamivar-lazzaro: okay18:40
SumitNaiksatamivar-lazzaro: as i was mentioning, the requirements seem to get processed twice and that creates duplicate entrypoints18:40
SumitNaiksatamivar-lazzaro: as soon as i removed the neutron package from the requirements, the issue went away18:40
ivar-lazzaroSumitNaiksatam: yeah makes sense18:40
SumitNaiksatamit would be helpful if someone from this team has prior experience on the packaging stuff, and if so please reach out to either me or ivar-lazzaro or rkukura18:41
SumitNaiksatam#link DB migrations18:41
SumitNaiksatamoops18:42
SumitNaiksatam#topic DB migrations18:42
*** openstack changes topic to "DB migrations (Meeting topic: networking_policy)"18:42
SumitNaiksatamivar-lazzaro: you want to summarize the issue?18:42
ivar-lazzaroSumitNaiksatam: sure18:42
ivar-lazzaroSo as is now, we are running our migration on top of Neutron's18:42
ivar-lazzaroBy doing this, we are changing the HEAD value on alembic_version table in the neutron Database18:43
ivar-lazzaroProblem is, when your version is polluted in this fashion you will be unable to upgrade Neutron anymore18:43
ivar-lazzaroso if you are using Neutron Juno + GBP, you won't be able to migrate to Kilo without some manual steps (downgrading GBP for instance)18:44
SumitNaiksatamivar-lazzaro: nice summary!18:44
ivar-lazzaroLong story short, I would like create a separate DB schema for our project... Which will share the same connection18:44
SumitNaiksatamso the options on the table are (as summarized by rkukura): “Do we use separate DBs with separate chains? Do we use separate chains in the same same DB? Does the GBP migration chain always effectively splice to the end of the neutron migration chain, or do they need to somehow be interleaved?”18:45
SumitNaiksatamivar-lazzaro: yeah that is one of the options (perhaps the only viable one right now)18:45
ivar-lazzaroSumitNaiksatam: there are other viable and maybe faster options18:45
SumitNaiksatambtw, I forgot to mention earlier, rkukura had a doctor’s appointment, so he could not join today18:46
*** mestery has quit IRC18:46
ivar-lazzaroSumitNaiksatam: but they don't solve the main problem18:46
SumitNaiksatamivar-lazzaro: okay18:46
SumitNaiksatamHenryG: hi18:46
ivar-lazzaroSumitNaiksatam: for instance, in alembic is possible to configure a different version table. With Neutron and GBP having different version tables the problem is mitigated18:47
*** bpokorny has quit IRC18:47
HenryGo/18:47
SumitNaiksatamHenryG: sorry for pinging you out of the blue18:47
SumitNaiksatamHenryG: but thought that it might interest you18:47
HenryGSumitNaiksatam: np18:47
ivar-lazzaroSumitNaiksatam: but even in this case, if in the future Neutron tries to create a table named gp_endpoints everything will break again18:47
SumitNaiksatamHenryG: if you back scroll to the current topic on “DB migrations” in the context of our stackforge GBP effort18:48
SumitNaiksatamHenryG: would love to hear your input18:48
SumitNaiksatamivar-lazzaro: true18:48
SumitNaiksatamHenryG: we can discuss offline18:48
SumitNaiksatamany other DB migration gurus out there, would love to get your input18:49
SumitNaiksatamivar-lazzaro: thanks again for the summary and trying to work through this tricky issue18:49
ivar-lazzaroSumitNaiksatam: np18:49
HenryGWill GBP be packaged separately from neutron?18:49
SumitNaiksatam#topic refactoring of resource mapping driver18:49
*** openstack changes topic to "refactoring of resource mapping driver (Meeting topic: networking_policy)"18:49
SumitNaiksatamHenryG: yes18:49
*** bpokorny has joined #openstack-meeting-318:50
SumitNaiksatamHenryG: at least for Juno, since its not in the trunk18:50
SumitNaiksatamon the topic of resource mapping driver, per rkukura: “What should be factored out of the resource_mapping driver for use by other drivers?”18:50
SumitNaiksatamso anyone writing GBP vendor drivers, please reach out to rkukura with thoughts on this18:51
*** bpokorny_ has joined #openstack-meeting-318:51
ivar-lazzaroSumitNaiksatam: I have a couple of suggestions on this matter18:51
SumitNaiksatamor just start an email thread18:51
SumitNaiksatamivar-lazzaro: yes sure18:51
SumitNaiksatamrms_13: you will be writing GBP driver as well, right?18:52
ivar-lazzaroSumitNaiksatam: first we should gather all the useful and possibly common code out of the resource mapping driver to a more generic superclass18:52
SumitNaiksatamivar-lazzaro: yes, we had discussed that earlier as well18:52
SumitNaiksatamivar-lazzaro: i believe the suggestion is that we do this after the current patches merge?18:52
ivar-lazzaroSumitNaiksatam: and then we should probably think of a way for each driver to define their own mapping18:52
SumitNaiksatamivar-lazzaro: okay18:52
ivar-lazzaroSumitNaiksatam: that I always give for granted :D18:53
SumitNaiksatamivar-lazzaro: lets start an email thread on this18:53
s3wongSumitNaiksatam, ivar-lazzaro: for this, rkukura and I talked about it during the hackathon18:54
SumitNaiksatams3wong: yes18:54
SumitNaiksatamokay so it seems like lots of people have ideas18:54
s3wonghe thinks EPG, L2/3-policy, implicit drivers are items that should be fairly common across all the vendors18:54
SumitNaiksatammight require more offline discussion18:54
LouisFSumitNaiksatam: can you copy me on that18:54
SumitNaiksatams3wong: implicit driver, yes18:54
s3wongand he wants to factor out that from the contract mapping piece and make it into another mapping driver18:55
SumitNaiksatamLouisF: yes sure, the whole team18:55
*** bpokorny has quit IRC18:55
s3wongobviously, as we discussed, I couldn't do it before Juno feature freeze18:55
SumitNaiksatams3wong: yeah, no18:55
SumitNaiksatam*np18:55
s3wongbut in my mind, I believe rkukura would want to put that as an item for Kilo cycle18:55
ivar-lazzaros3wong: implicit is definitively common, but each plugin may want its own resource mapping18:55
*** pkoniszewski has quit IRC18:56
s3wongL2Policy mapping to Neutron network, and L3Policy mapping to a router --- even in case of non-implicit, seems useful for more than one driver18:56
s3wongivar-lazzaro: I definitely see that contract=>SG mapping to mostly NOT be too useful for most vendors :-)18:57
SumitNaiksatams3wong: ivar-lazzaro: good points18:57
*** bpokorn__ has joined #openstack-meeting-318:57
ivar-lazzaros3wong: even l2_context -> network or anything else.... Endpoint -> Port is the only one I feel is mandatory18:57
SumitNaiksatamsince rkukura is not around, lets going to the ML for this18:57
ivar-lazzaroSumitNaiksatam: +118:58
s3wongSumitNaiksatam: sure18:58
SumitNaiksatamivar-lazzaro: s3wong thanks18:58
SumitNaiksatam#topic Open Discussion18:58
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:58
SumitNaiksatamanything we missed?18:58
SumitNaiksatamrms_13: we need to start porting code to the GBP Horizon repo18:58
SumitNaiksatamrms_13: we will have help on this, but it will help to get your reviews18:59
SumitNaiksatamrms_13: among other things ;-)18:59
SumitNaiksatamanything else folks?18:59
*** jacalcat has joined #openstack-meeting-319:00
SumitNaiksatamokay thanks everyone for joining19:00
s3wongthanks19:00
*** bpokorny_ has quit IRC19:00
SumitNaiksatamkeep up the good work!19:00
ivar-lazzaroCiao!19:00
SumitNaiksatam#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Thu Oct  2 19:00:20 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-10-02-18.01.html19:00
SumitNaiksatambye19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-10-02-18.01.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-10-02-18.01.log.html19:00
*** SumitNaiksatam has quit IRC19:02
*** jrist has quit IRC19:03
*** sarob_away is now known as sarob19:06
*** david-lyle has quit IRC19:07
*** hemanthravi has quit IRC19:08
*** terryw has quit IRC19:20
*** carl_baldwin has joined #openstack-meeting-319:22
*** pballand has joined #openstack-meeting-319:25
*** armax has quit IRC19:31
*** marun has quit IRC19:32
*** jrist has joined #openstack-meeting-319:32
*** dconde has quit IRC19:38
*** LouisF has quit IRC19:39
*** rkukura has left #openstack-meeting-319:42
*** david-lyle has joined #openstack-meeting-319:54
*** alexpilotti has quit IRC19:54
*** mwagner_lap has quit IRC19:54
*** david-lyle_ has joined #openstack-meeting-319:56
*** MaxV has joined #openstack-meeting-319:59
*** david-lyle has quit IRC19:59
*** thangp has quit IRC20:05
*** mestery has joined #openstack-meeting-320:06
*** seizadi has quit IRC20:13
*** seizadi has joined #openstack-meeting-320:13
*** david-lyle_ is now known as david-lyle20:15
*** dconde has joined #openstack-meeting-320:16
*** mwagner_lap has joined #openstack-meeting-320:17
*** mestery has quit IRC20:24
*** sandr8 has joined #openstack-meeting-320:25
*** otherwiseguy has joined #openstack-meeting-320:28
*** sandr8 has quit IRC20:30
*** SumitNaiksatam has joined #openstack-meeting-320:34
*** seizadi has quit IRC20:41
*** jacalcat has left #openstack-meeting-320:41
*** mestery has joined #openstack-meeting-320:43
*** SridharRamaswamy has joined #openstack-meeting-320:48
*** seizadi has joined #openstack-meeting-320:48
*** jaypipes has quit IRC20:49
*** igordcard has joined #openstack-meeting-320:49
*** lhcheng_ has quit IRC20:52
*** lhcheng has joined #openstack-meeting-320:52
*** HenryG has quit IRC20:55
*** lhcheng has quit IRC20:57
*** bpokorn__ has quit IRC20:58
*** lhcheng has joined #openstack-meeting-321:01
*** alexsyip has joined #openstack-meeting-321:09
*** flaper87 is now known as flaper87|afk21:11
*** jacalcat has joined #openstack-meeting-321:17
*** jacalcat has left #openstack-meeting-321:17
*** MaxV has quit IRC21:25
*** mfer has quit IRC21:26
*** otherwiseguy has quit IRC21:37
*** terryw has joined #openstack-meeting-321:37
*** garyduan has quit IRC21:37
*** dconde has quit IRC21:37
*** SridharRamaswamy has quit IRC21:38
*** garyduan has joined #openstack-meeting-321:38
*** dconde has joined #openstack-meeting-321:38
*** corvus has quit IRC21:40
*** corvus has joined #openstack-meeting-321:41
*** terryw has quit IRC21:42
*** otherwiseguy has joined #openstack-meeting-321:43
*** shwetaap has quit IRC21:46
*** bpokorny has joined #openstack-meeting-321:50
*** carl_baldwin has quit IRC21:52
*** SridharRamaswamy has joined #openstack-meeting-321:55
*** shwetaap has joined #openstack-meeting-321:59
*** Youcef_ has quit IRC22:01
*** bpokorny_ has joined #openstack-meeting-322:01
*** carl_baldwin has joined #openstack-meeting-322:01
*** mestery has quit IRC22:01
*** Youcef has joined #openstack-meeting-322:02
*** mestery has joined #openstack-meeting-322:03
*** SridharR_ has joined #openstack-meeting-322:03
*** bpokorny has quit IRC22:04
*** hurgleburgler has quit IRC22:05
*** hurgleburgler has joined #openstack-meeting-322:06
*** Sridhar__ has joined #openstack-meeting-322:06
*** seizadi has quit IRC22:06
*** SridharRamaswamy has quit IRC22:06
*** SridharR_ has quit IRC22:07
*** seizadi has joined #openstack-meeting-322:08
*** seizadi1 has joined #openstack-meeting-322:08
*** seizadi has quit IRC22:08
*** otherwiseguy has quit IRC22:08
*** marun has joined #openstack-meeting-322:15
*** sandr8 has joined #openstack-meeting-322:26
*** sarob is now known as sarob_away22:26
*** mestery has quit IRC22:27
*** jgrimm is now known as zz_jgrimm22:28
*** bpokorny has joined #openstack-meeting-322:28
*** bpokorny has quit IRC22:29
*** sandr8 has quit IRC22:31
*** bpokorny_ has quit IRC22:31
*** bpokorny has joined #openstack-meeting-322:34
*** shwetaap has quit IRC22:35
*** david-lyle has quit IRC22:51
*** carl_baldwin has quit IRC23:01
*** marun has quit IRC23:01
*** yamahata has joined #openstack-meeting-323:05
*** HenryG has joined #openstack-meeting-323:10
*** s3wong has quit IRC23:16
*** bpokorny_ has joined #openstack-meeting-323:23
*** bpokorny has quit IRC23:26
*** yamahata has quit IRC23:27
*** sarob_away is now known as sarob23:27
*** Sridhar__ has quit IRC23:34
*** sarob is now known as sarob_away23:37
*** igordcard has quit IRC23:37
*** garyduan has quit IRC23:37
*** garyduan has joined #openstack-meeting-323:38
*** Swami has quit IRC23:39
*** SridharRamaswamy has joined #openstack-meeting-323:41
*** markmcclain has joined #openstack-meeting-323:44
*** jacalcat has joined #openstack-meeting-323:52
*** jacalcat has left #openstack-meeting-323:52

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!