Wednesday, 2014-08-20

*** emagana has quit IRC00:01
*** emagana has joined #openstack-meeting-300:02
*** emagana has quit IRC00:06
*** banix has quit IRC00:07
*** sankarshan_away is now known as sankarshan00:10
*** sankarshan is now known as sankarshan_away00:10
*** MarkAtwood has quit IRC00:12
*** SumitNaiksatam has quit IRC00:16
*** otherwiseguy has quit IRC00:19
*** jcoufal has quit IRC00:22
*** mwagner_lap has joined #openstack-meeting-300:35
*** SumitNaiksatam has joined #openstack-meeting-300:35
*** cjellick has quit IRC00:47
*** cjellick has joined #openstack-meeting-300:48
*** rudrarugge has quit IRC00:49
*** cjellick has quit IRC00:52
*** chuckC_ has quit IRC00:56
*** clu_ has quit IRC00:57
*** markmcclain has joined #openstack-meeting-300:59
*** alexsyip has quit IRC01:01
*** banix has joined #openstack-meeting-301:04
*** SumitNaiksatam has quit IRC01:09
*** SumitNaiksatam has joined #openstack-meeting-301:09
*** banix has quit IRC01:12
*** rcleere has joined #openstack-meeting-301:14
*** stanzgy has joined #openstack-meeting-301:15
*** otherwiseguy has joined #openstack-meeting-301:17
*** mtreinish has quit IRC01:19
*** bradjones has quit IRC01:20
*** mtreinish has joined #openstack-meeting-301:22
*** mtreinish has quit IRC01:23
*** mtreinish has joined #openstack-meeting-301:23
*** bradjones has joined #openstack-meeting-301:25
*** bradjones has quit IRC01:25
*** bradjones has joined #openstack-meeting-301:25
*** thangp has joined #openstack-meeting-301:35
*** mtreinish has quit IRC01:38
*** jaypipes has quit IRC01:41
*** jaypipes has joined #openstack-meeting-301:42
*** shwetaap has joined #openstack-meeting-301:48
*** rcleere has quit IRC01:49
*** celttechie_ has joined #openstack-meeting-301:50
*** baohua has joined #openstack-meeting-301:55
*** shakamunyi has quit IRC02:01
*** banix has joined #openstack-meeting-302:09
*** banix has quit IRC02:15
*** seizadi has joined #openstack-meeting-302:21
*** markmcclain has quit IRC02:22
*** thangp has quit IRC02:23
*** chuckC_ has joined #openstack-meeting-302:29
*** pballand has quit IRC02:30
*** julim has joined #openstack-meeting-302:30
*** shakamunyi has joined #openstack-meeting-302:34
*** julim has quit IRC02:37
*** vkmc has quit IRC02:38
*** mfer has joined #openstack-meeting-302:39
*** markmcclain has joined #openstack-meeting-302:40
*** mfer has quit IRC02:40
*** shakamunyi has quit IRC02:41
*** armax has left #openstack-meeting-302:42
*** shakamunyi has joined #openstack-meeting-302:42
*** alexpilotti has quit IRC02:48
*** seizadi has quit IRC02:58
*** banix has joined #openstack-meeting-303:11
*** ivar-lazzaro1 has quit IRC03:12
*** banix has quit IRC03:16
*** markmcclain has quit IRC03:20
*** SridharRamaswamy has quit IRC03:21
*** eghobo has joined #openstack-meeting-303:48
*** seizadi has joined #openstack-meeting-304:08
*** seizadi has quit IRC04:10
*** banix has joined #openstack-meeting-304:13
*** banix has quit IRC04:17
*** lcheng has joined #openstack-meeting-304:22
*** lcheng has quit IRC04:23
*** banix has joined #openstack-meeting-304:31
*** eghobo has quit IRC04:31
*** eghobo has joined #openstack-meeting-304:32
*** nelsnelson has quit IRC04:32
*** celttechie_ has quit IRC04:32
*** banix has quit IRC04:33
*** nelsnelson has joined #openstack-meeting-304:36
*** banix has joined #openstack-meeting-304:43
*** tomoe_ has joined #openstack-meeting-304:46
*** MarkAtwood has joined #openstack-meeting-304:59
*** MarkAtwood has quit IRC04:59
*** shwetaap has quit IRC05:10
*** eguz has joined #openstack-meeting-305:10
*** eghobo has quit IRC05:10
*** SumitNaiksatam has quit IRC05:15
*** otherwiseguy has quit IRC05:20
*** otherwiseguy has joined #openstack-meeting-305:21
*** otherwiseguy has quit IRC05:27
*** seizadi has joined #openstack-meeting-305:28
*** tmazur has joined #openstack-meeting-305:32
*** eguz has quit IRC05:53
*** rudrarugge has joined #openstack-meeting-305:56
*** reed has quit IRC06:09
*** seizadi has quit IRC06:15
*** jtomasek has joined #openstack-meeting-306:24
*** baohua has quit IRC06:28
*** baohua has joined #openstack-meeting-306:30
*** jcoufal has joined #openstack-meeting-306:31
*** pkoniszewski has joined #openstack-meeting-306:34
*** flaper87|afk is now known as flaper8706:35
*** jcoufal has quit IRC06:38
*** shakamunyi has quit IRC06:43
*** shakamunyi has joined #openstack-meeting-306:44
*** shakamunyi has quit IRC06:47
*** shakamunyi has joined #openstack-meeting-306:48
*** banix has quit IRC06:48
*** jtomasek has quit IRC06:58
*** dulek has joined #openstack-meeting-307:00
*** rudrarugge has quit IRC07:09
*** jcoufal has joined #openstack-meeting-307:27
*** tomoe_ has quit IRC07:41
*** bradjones has quit IRC07:41
*** tomoe_ has joined #openstack-meeting-307:41
*** MaxV has joined #openstack-meeting-307:42
*** mfer has joined #openstack-meeting-307:44
*** bradjones has joined #openstack-meeting-307:44
*** bradjones has quit IRC07:44
*** bradjones has joined #openstack-meeting-307:44
*** tomoe_ has quit IRC07:46
*** tomoe_ has joined #openstack-meeting-307:47
*** mfer has quit IRC07:48
*** MaxV has quit IRC08:15
*** MaxV has joined #openstack-meeting-308:16
*** MaxV has quit IRC08:20
*** shakamunyi has quit IRC08:25
*** MaxV has joined #openstack-meeting-308:33
*** igordcard has joined #openstack-meeting-308:44
*** Longgeek has joined #openstack-meeting-308:46
*** Longgeek has quit IRC08:48
*** Longgeek has joined #openstack-meeting-308:48
*** shakamunyi has joined #openstack-meeting-308:52
*** shakamunyi has quit IRC08:56
*** jtomasek has joined #openstack-meeting-309:04
*** mtreinish has joined #openstack-meeting-309:10
*** obondarev has joined #openstack-meeting-309:15
*** jtomasek has quit IRC09:26
*** baohua has quit IRC09:27
*** jtomasek has joined #openstack-meeting-309:32
*** zz_johnthetubagu is now known as johnthetubaguy09:37
*** shakamunyi has joined #openstack-meeting-309:53
*** shakamunyi has quit IRC09:57
*** igordcard has quit IRC10:03
*** tmazur has quit IRC10:16
*** yamahata has quit IRC10:28
*** jaypipes has quit IRC10:39
*** jaypipes has joined #openstack-meeting-310:40
*** robcresswell has joined #openstack-meeting-310:57
*** igordcard has joined #openstack-meeting-311:08
*** tomoe__ has joined #openstack-meeting-311:18
*** alexpilotti has joined #openstack-meeting-311:18
*** tomoe_ has quit IRC11:20
*** baohua has joined #openstack-meeting-311:23
*** tomoe__ has quit IRC11:34
*** tomoe_ has joined #openstack-meeting-311:37
*** tomoe_ has quit IRC11:39
*** alexpilotti has quit IRC11:48
*** alexpilotti has joined #openstack-meeting-312:03
*** vkmc has joined #openstack-meeting-312:13
*** alexpilotti has quit IRC12:16
*** tomoe_ has joined #openstack-meeting-312:21
*** alexpilotti has joined #openstack-meeting-312:37
*** lblanchard has joined #openstack-meeting-312:41
*** harrisonkelly has joined #openstack-meeting-312:50
*** robcresswell has quit IRC12:50
*** mfer has joined #openstack-meeting-313:02
*** thomasem has joined #openstack-meeting-313:04
*** mwagner_lap has quit IRC13:04
*** julim has joined #openstack-meeting-313:09
*** banix has joined #openstack-meeting-313:21
*** peristeri has joined #openstack-meeting-313:26
*** armax has joined #openstack-meeting-313:42
*** baohua has quit IRC13:44
*** carl_baldwin has joined #openstack-meeting-313:45
*** celttechie_ has joined #openstack-meeting-313:54
*** eghobo has joined #openstack-meeting-313:55
*** Longgeek has quit IRC13:55
*** Longgeek has joined #openstack-meeting-313:56
*** mwagner_lap has joined #openstack-meeting-313:57
*** seizadi has joined #openstack-meeting-313:58
*** nelsnelson has quit IRC14:01
*** shwetaap has joined #openstack-meeting-314:02
*** nelsnelson has joined #openstack-meeting-314:02
*** markmcclain has joined #openstack-meeting-314:06
*** mestery has joined #openstack-meeting-314:07
*** mestery has quit IRC14:07
*** mestery has joined #openstack-meeting-314:08
*** rcleere has joined #openstack-meeting-314:08
*** carl_baldwin has quit IRC14:12
*** carl_baldwin has joined #openstack-meeting-314:16
*** harrisonkelly has quit IRC14:19
*** otherwiseguy has joined #openstack-meeting-314:20
*** thangp has joined #openstack-meeting-314:24
*** yamahata has joined #openstack-meeting-314:25
*** jlibosva has joined #openstack-meeting-314:26
*** david-lyle has joined #openstack-meeting-314:30
*** WormMan has joined #openstack-meeting-314:31
*** david-lyle has quit IRC14:31
*** marun has joined #openstack-meeting-314:31
*** david-lyle has joined #openstack-meeting-314:31
*** harrisonkelly has joined #openstack-meeting-314:33
*** Sukhdev has joined #openstack-meeting-314:33
*** jtomasek has quit IRC14:34
*** eghobo has quit IRC14:36
*** banix has quit IRC14:39
*** celttechie_ has quit IRC14:44
*** celttechie_ has joined #openstack-meeting-314:46
*** reed has joined #openstack-meeting-314:48
*** jtomasek has joined #openstack-meeting-314:49
*** harrisonkelly has left #openstack-meeting-314:53
*** shakamunyi has joined #openstack-meeting-315:00
*** WormMan has left #openstack-meeting-315:00
*** mwagner_lap has quit IRC15:03
*** seizadi has quit IRC15:05
*** pkoniszewski has quit IRC15:10
*** Longgeek_ has joined #openstack-meeting-315:14
*** yamahata has quit IRC15:16
*** jcoufal has quit IRC15:17
*** Longgeek has quit IRC15:17
*** marun has quit IRC15:21
*** marun has joined #openstack-meeting-315:21
*** mestery has quit IRC15:23
*** celttechie_ has quit IRC15:25
*** cjellick has joined #openstack-meeting-315:25
*** markmcclain has quit IRC15:27
*** jtomasek has quit IRC15:30
*** stanzgy has quit IRC15:31
*** eghobo has joined #openstack-meeting-315:31
*** nelsnelson has quit IRC15:31
*** eghobo has quit IRC15:33
*** MaxV has quit IRC15:36
*** MaxV has joined #openstack-meeting-315:37
*** MaxV has quit IRC15:41
*** mestery has joined #openstack-meeting-315:42
*** mestery has quit IRC15:42
*** mestery has joined #openstack-meeting-315:43
*** marun has quit IRC15:44
*** marun has joined #openstack-meeting-315:47
*** emagana has joined #openstack-meeting-315:48
*** rkukura has joined #openstack-meeting-315:50
*** rkukura has left #openstack-meeting-315:50
*** marun has quit IRC15:51
*** marun has joined #openstack-meeting-315:52
*** nelsnelson has joined #openstack-meeting-315:55
*** ivar-lazzaro has joined #openstack-meeting-315:55
*** mestery has quit IRC15:56
*** marun has quit IRC16:06
*** marun has joined #openstack-meeting-316:11
*** celttechie_ has joined #openstack-meeting-316:14
*** flaviof is now known as flaviof_zzz16:15
*** markmcclain has joined #openstack-meeting-316:16
*** mestery has joined #openstack-meeting-316:19
*** mestery has quit IRC16:21
*** mestery has joined #openstack-meeting-316:22
*** SumitNaiksatam has joined #openstack-meeting-316:24
*** k4n0 has quit IRC16:25
*** mestery has quit IRC16:27
*** dulek has quit IRC16:28
*** MaxV has joined #openstack-meeting-316:28
*** rudrarugge has joined #openstack-meeting-316:33
*** Sukhdev has quit IRC16:33
*** jlibosva has left #openstack-meeting-316:33
*** Sukhdev has joined #openstack-meeting-316:34
*** mestery has joined #openstack-meeting-316:38
*** MaxV has quit IRC16:38
*** mspreitz has joined #openstack-meeting-316:38
*** alexsyip has joined #openstack-meeting-316:42
*** jcoufal has joined #openstack-meeting-316:46
*** mestery_ has joined #openstack-meeting-316:51
*** mestery has quit IRC16:51
*** otherwiseguy has quit IRC16:52
*** flaviof_zzz is now known as flaviof16:55
*** mestery has joined #openstack-meeting-316:55
*** mestery_ has quit IRC16:58
*** mestery has quit IRC16:59
*** harrisonkelly has joined #openstack-meeting-317:07
*** jpomero has quit IRC17:08
*** alexpilotti has quit IRC17:12
*** pballand has joined #openstack-meeting-317:12
*** markmcclain has quit IRC17:12
*** Kanzhe_ has joined #openstack-meeting-317:15
*** anil_rao has joined #openstack-meeting-317:18
*** SumitNaiksatam has quit IRC17:19
*** s3wong has joined #openstack-meeting-317:19
*** SumitNaiksatam has joined #openstack-meeting-317:20
*** emagana has quit IRC17:21
*** emagana has joined #openstack-meeting-317:21
*** nelsnelson has quit IRC17:23
*** shwetaap has quit IRC17:25
*** SumitNaiksatam has quit IRC17:25
*** emagana has quit IRC17:26
*** songole has joined #openstack-meeting-317:27
*** vinay_yadhav has joined #openstack-meeting-317:30
*** SumitNaiksatam has joined #openstack-meeting-317:31
*** emagana has joined #openstack-meeting-317:32
*** LouisF has joined #openstack-meeting-317:32
SumitNaiksatamKanzhe_: s3wong songole: there?17:32
s3wongSumitNaiksatam: hello17:32
SumitNaiksatammy irc client acting up again17:32
SumitNaiksatamok lets get started17:32
songoleSumitNaiksatam: hello17:32
s3wongI noticed17:33
SumitNaiksatam#startmeeting Networking Advanced Services17:33
openstackMeeting started Wed Aug 20 17:33:07 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.17:33
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:33
*** openstack changes topic to " (Meeting topic: Networking Advanced Services)"17:33
openstackThe meeting name has been set to 'networking_advanced_services'17:33
*** cathy_ has joined #openstack-meeting-317:33
SumitNaiksatam#chairs s3wong Kanzhe_ songole dougwig17:33
SumitNaiksatamin case i get dropped17:33
*** pcm_ has joined #openstack-meeting-317:33
*** regXboi has joined #openstack-meeting-317:33
dougwigo/17:33
pcm_hi17:34
SumitNaiksatam#announcements Juno feature proposal freeze deadline is aug 21st17:34
SumitNaiksatamor that was more of an info!17:34
SumitNaiksatamwe already know it17:34
SumitNaiksatami tried to check mestery last couple of weeks in this IRC meeting about priorities, etc17:35
SumitNaiksatami -> we17:35
Kanzhe_SumitNaiksatam: I am here.17:35
SumitNaiksatamKanzhe_: welcome back! :-)17:35
SumitNaiksatami dont think mestery is around today either17:35
Kanzhe_SumitNaiksatam: thanks.17:35
SumitNaiksatamlets get started17:35
SumitNaiksatam#topic Flavors17:36
*** openstack changes topic to "Flavors (Meeting topic: Networking Advanced Services)"17:36
SumitNaiksatamenikanorov_ markmcclain there?17:36
enikanorov_hi17:36
enikanorov_i'm here17:36
SumitNaiksatamenikanorov_: any updates on the spec?17:36
SumitNaiksatam#link https://review.openstack.org/#/c/10272317:37
enikanorov_no17:37
enikanorov_unfortunately...17:37
*** badveli has joined #openstack-meeting-317:37
SumitNaiksatamenikanorov_: ok17:37
SumitNaiksatamenikanorov_: we are still pursuing the implementation patch #link https://review.openstack.org/#/c/105982?17:37
SumitNaiksatami see that dougwig and pcm_ reviewed, thats great, thanks!17:38
LouisFenikanorov_: is there going to a merge of the two specs?17:38
SumitNaiksatamenikanorov_: perhaps just needs a rebase17:38
enikanorov_LouisF: that's a question. I feel we're deffering whole thing to K17:38
dougwigi asked about flavors during the neutron meeting, and got an answer that it'd make J.17:39
*** emagana has quit IRC17:39
*** igordcard has quit IRC17:39
SumitNaiksatamdougwig: ok17:39
*** emagana has joined #openstack-meeting-317:39
enikanorov_dougwig: well, I'd be glad if someone help me pinging Mark :)17:40
dougwigi will.  :)17:40
SumitNaiksatamenikanorov_: any else to add? :-)17:41
enikanorov_the impl patch just needs a rebase bacause of migrations went ahead17:41
*** SridharRamaswamy has joined #openstack-meeting-317:41
*** harrisonkelly has quit IRC17:41
enikanorov_not really.17:41
SumitNaiksatamenikanorov_: yeah, i guessed as much17:41
SumitNaiksatamany questions for enikanorov_ apart from the ones already asked?17:41
cathy_which BP will be the one for flavor or it will be a merged one?17:41
SumitNaiksatamperhaps reviewing #link https://review.openstack.org/#/c/10598217:41
SumitNaiksatammight help17:41
*** alexpilotti has joined #openstack-meeting-317:42
SumitNaiksatamcathy_: #link https://review.openstack.org/#/c/10272317:42
SumitNaiksatamor some variant of it based on reviewer’s comments17:42
cathy_SumitNaiksatam: ok, tahnsk17:42
SumitNaiksatamenikanorov_: correct?17:42
enikanorov_SumitNaiksatam: yes17:42
SumitNaiksatamenikanorov_: thanks17:43
SumitNaiksatam#topic Service base and insertion implementation update17:43
*** openstack changes topic to "Service base and insertion implementation update (Meeting topic: Networking Advanced Services)"17:43
SumitNaiksatamKanzhe_: s3wong marios: hi17:43
s3wongSumitNaiksatam: hello17:43
Kanzhe_SumitNaiksatam: hi17:43
*** jcoufal has quit IRC17:44
SumitNaiksatamany updates?17:44
Kanzhe_We are making progress in implementation.17:44
SumitNaiksatamKanzhe_: good17:44
s3wongSo I had a meeting with blogan and dougwig last Thurs - and concluded that we won't  migrate LBaaS v1 to service insertion framework17:44
SumitNaiksatams3wong: okay17:44
s3wongand I met with Kanzhe_ and kevinbenton last Friday to divide up work17:45
s3wongthe conclusion is that we will only do an experimental migration on vpnaas only17:45
LouisFwill fwaas use service base?17:45
SumitNaiksatams3wong: yeah, my question too ^^^?17:45
s3wongLouisF: Not before Thursday deadline17:45
SumitNaiksatamis SridarK here?17:46
s3wong(technically once the change to ServicePluginBase is in, all services will be "using" it)17:46
SumitNaiksatams3wong: so you guys narrowed down on vpnaas because its easier?17:46
s3wongbut of course, none of them will do anything w.r.t. service interfaces17:46
SumitNaiksatamor rather limited in scope?17:46
s3wongSumitNaiksatam: yes :-)17:46
SumitNaiksatamin my opinion, fwaas was the one which would have benefited the most17:47
SumitNaiksatamso on vpnaas, is marios here17:47
SumitNaiksatam?17:47
s3wongSumitNaiksatam: certainly - but also the most work on the service (FWaaS) itself17:47
*** jtomasek has joined #openstack-meeting-317:47
SumitNaiksatams3wong: i believe SridarK had prepped for this, but we need to check with him17:47
Kanzhe_SumitNaiksatam, agree, based on the schedule, it is more realistic to do VPN at first.17:48
s3wongat this point, I think it is a stretch to expect SridarK to have it ready by tomorrow17:48
s3wong(also, we still don't have neutron python-client...)17:48
SumitNaiksatams3wong: i meant my understanding was that there was some prep already done on this front, but anyway we can check offline17:48
s3wongSumitNaiksatam: sure17:48
SumitNaiksatams3wong: the client is not bound by milestone constrains17:49
s3wongSumitNaiksatam: good to know! :-)17:49
SumitNaiksatamso there should be a little more flexibility there17:49
*** shwetaap has joined #openstack-meeting-317:49
SumitNaiksatamyeah, client code is released independently17:49
SumitNaiksatamanyway, on the technical aspects17:49
SumitNaiksatamKanzhe_ s3wong: any blockers?17:50
Kanzhe_SumitNaiksatam:  we will meet later today for initial integration.17:50
SumitNaiksatamanything we need to discuss in this meeting, or any course corrections we had to make?17:50
*** jpomero has joined #openstack-meeting-317:50
Kanzhe_we will know then. :-)17:50
SumitNaiksatamKanzhe_: ok good to know17:50
s3wongSumitNaiksatam: my patch will depend on Kanzhe_ 's, so technically that is a blocker :-)17:50
SumitNaiksatams3wong: :-)17:51
SumitNaiksatammarios had the vpnaas patch in place17:51
SumitNaiksatamso i am assuming you are coordinating with him?17:52
*** reed has quit IRC17:52
s3wongSumitNaiksatam: marios: yes, we will17:52
*** reed has joined #openstack-meeting-317:52
SumitNaiksatams3wong: you have the link to your WIP patch?17:53
s3wong#link https://review.openstack.org/#/c/113975/17:53
SumitNaiksatamand it would be helpful if you can update the wiki page: #link https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan17:53
s3wongSumitNaiksatam: sure17:53
*** tomoe_ has quit IRC17:53
SumitNaiksatams3wong: Kanzhe_: thanks17:53
SumitNaiksatamany questions for s3wong, Kanzhe_ ?17:54
SumitNaiksatam#topic Service Chaining17:55
*** openstack changes topic to "Service Chaining (Meeting topic: Networking Advanced Services)"17:55
SumitNaiksatamsongole: hi17:55
songoleSumitNaiksatam: hello17:55
SumitNaiksatamsongole: updates?17:55
SumitNaiksatami believe you have the CLI patch as well17:55
songoleWe are making progress on the implementation17:55
LouisFSumitNaiksatam: i had that question on direction at last meeting17:56
SumitNaiksatamsongole: links to the patches?17:56
songoleI will be uploading patches17:56
songolehttps://review.openstack.org/#/c/113737/17:56
songolehttps://review.openstack.org/#/c/113738/17:56
songole2nd link is CLI patch17:56
SumitNaiksatamsongole: thanks!17:57
SumitNaiksatamcan you update the wiki page: #link https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan17:57
songoleok17:57
SumitNaiksatamLouisF: sorry go ahead17:57
LouisFthere is a list of services but the order is not ambiguous17:58
LouisFremove not^17:58
SumitNaiksatamLouisF: you mean the order is ambigous?17:59
LouisFSumitNaiksatam: yes17:59
SumitNaiksatamLouisF: is this in the context of the return traffic?17:59
LouisFSumitNaiksatam: yes17:59
*** seizadi has joined #openstack-meeting-318:00
LouisFmy comment in the most recent patch describes a solution18:00
songoleLouisF: for Juno we are keeping it simple18:00
songoleLouisF: the order will be reversed for return traffic18:00
SumitNaiksatamLouisF: my understanding from the reading the spec and the comments was that there is only one order18:00
*** mandeep has joined #openstack-meeting-318:01
LouisFthe order is specified but with respect to what?18:01
*** emagana has quit IRC18:01
SumitNaiksatam#link https://review.openstack.org/#/c/9352418:01
cathy_SumitNaiksatam: I have given similar comments before and raise this in a previous meeting and there is an action item for this.18:01
*** hemanthravi has joined #openstack-meeting-318:01
*** emagana has joined #openstack-meeting-318:01
SumitNaiksatamcathy_: i thought that comment was responded to in the spec18:02
mandeepThe order of the services application is specified explicitly in the spec.18:02
*** harrisonkelly has joined #openstack-meeting-318:02
cathy_no AFAIK18:02
*** emagana has quit IRC18:02
SumitNaiksatamcathy_: ok so i might be confusing the responses18:02
hemanthraviSumitNaiksatam, i forgot to do that18:02
cathy_Let me descirbe the problem here again18:02
SumitNaiksatamhemanthravi: ah the action item was for hemanthravi :-)18:02
*** johnthetubaguy is now known as zz_johnthetubagu18:02
hemanthravithe order of the services is the reverse order for outgoing traffic18:03
SumitNaiksatamsongole: can you point to the line in the spec which mentions order clarification (just for the benefit of everyone here)?18:03
*** emagana has joined #openstack-meeting-318:03
*** celttechie_ has quit IRC18:03
SumitNaiksatamhemanthravi: line number in spec?18:03
LouisFSumitNaiksatam: line 207 208 mention ingress / egress traffic but they are undefined18:03
hemanthravi16218:04
songoleLouisF: correct :)18:04
SumitNaiksatamLouisF: ah yes, the example18:04
cathy_The service chain API specifies sequence of the service functions, eg. FW and IPS, Then it specifies a neutorn port for it. The neutron port is between a subnet and a router, so the quesiton is18:04
SumitNaiksatamhemanthravi: thanks, yeah 161 and 16218:04
mandeepLouisF: The example states the exact order.18:04
LouisFSumitNaiksatam: yes18:04
LouisFmandeep: yes there is an order but ingress/egress is undefined18:05
mandeepLouisF: Lines 181-18418:05
cathy_is the sequnce "subnet, fw, ips, router" or "router, fw, ips, subnet"18:05
cathy_?18:05
mandeepcathy_: What is subnet in this context? A service?18:06
mandeepcathy_: See lines 181-18418:06
cathy_That is the example in your spec, a neutorn port between a subnet and a router18:06
regXboihmm18:06
cathy_the subnet is a sub network18:06
mandeepWhy is that in the service chain?18:06
mandeepIt is not a service18:07
regXboiso I see the spec and it is very clear18:07
mandeepregXboi: Thanks18:07
regXboibut I'm not really happy about a service chain *requiring* mirror image on return traffic18:07
cathy_mandeep: could you refer to the example in your spec about the neutron port?18:07
regXboiI would have preferred that to be a parameter of the chain itself18:07
mandeepregXboi: This was for first stage of implementation (Juno)18:08
regXboimandeep: is there a blue print on loosening that up?18:08
mandeepregXboi: In future, we canallow different orders, but I wanted to harmonize that with traffic steering and hence avoided gerring into that now18:08
mandeep'getting'18:08
regXboimandeep: I liked gerriting :)18:08
SumitNaiksatamregXboi: :-)18:09
mandeepcathy_: I did not understand your question.18:09
mandeepregXboi: ;-)18:09
cathy_mandeep: no really. Ok, let me try again18:09
*** eghobo has joined #openstack-meeting-318:10
regXboiwe have an underlying implementation that already allows different orders - hence my question18:10
cathy_the neutorn port is between an externale network and a router18:10
regXboior not question - comment18:10
SumitNaiksatamcathy_: i believe the port is on a network18:10
SumitNaiksatami mean all “ports” are on a network18:10
LouisFmandeep: the direction traffic is not defined - the example imples the N1 - > E1 is egress - right?18:10
cathy_what is the sequence: "extenral network, FW, IPS, router" or "router, FW, IPS, external network"?18:10
mandeepregXboi: I agree that it is a nice feature to have, particularly for interoperation with NFV18:11
regXboiport is scoped by network, but if you look at the "device_owner" it's the router18:11
*** marun has quit IRC18:11
SumitNaiksatamregXboi: true18:11
mandeepregXboi: But I was worried that if we added it now, it might need to get updated when we have TS integrated18:11
cathy_regXboi: I already gave such comments twice before in the spec and raised it in a previous meeting18:11
hemanthraviLouisF, that's correct18:11
regXboimandeep: point taken18:11
mandeepregXboi: So I created a simpler spec for Juno, which can always evolve later if we need more control.18:12
regXboiok, so I think LouisF and cathy_ are asking the same thing, just in different ways18:12
mandeepcathy_: I will try to address that in an email18:13
LouisFhemanthravi: so between any two networks the direction is undefined  - right?18:13
hemanthravimandeep, on lines 207/28 for the chain [FW, LB] is the sequence correct or should it be reversed18:13
hemanthravithat should be 20818:13
SumitNaiksatamso is the difference in understanding with respect to the implicit convention (currently) versus explicit for specifying directions?18:13
regXboiSumitNaiksatam: it looks like it18:13
cathy_mandeep: Could you just provide an answer to my simple example? That will help calrify my simple question:-)18:14
*** marun has joined #openstack-meeting-318:14
SumitNaiksatamregXboi: okay, when we reviewed the spec it seemed that those concerns were addressed in the spec and was made explicit, but perhaps not as clear18:14
mandeepcathy_: I believe the problem is in the question, so the example will probably not address it.18:14
regXboiI'd say the implicit convention is that ingress is from network through port and egress is through port to network (based on the example)18:15
cathy_mandeep: just for my example, could you let us know what is the sequence?18:15
mandeephemanthravi: it is correct18:15
cathy_I think existing API is ambigous about that18:15
LouisFSumitNaiksatam: so convention internal network to external net = egress direction?18:15
mandeepcathy_: The error is that subnet is not a service and you are confusing data-path with service order18:16
regXboiLouisF: how did you get to that?18:16
LouisFregXboi: based on the example18:16
cathy_I am not saying a subnet is a service.18:16
cathy_It is never a service18:16
regXboiI don't see where internal network shows up in the example18:16
regXboiI see external network, router and port18:16
SumitNaiksatamcathy_: i believe what you are saying is the traffic originating on the internal network/subnet?18:17
mandeepLouisF: See lines 204-20918:17
regXboilet me restate that :)18:17
LouisFregXboi: 177 - 17918:17
regXboiyes, I see that the example talks about internal networks, but they are only window dressing and don't really matter18:17
cathy_SumitNaiksatam: Let me tyr again. I am using the example given in the service chain spec.18:17
SumitNaiksatamcathy_: sure18:18
mandeepcathy_: Line numbers?18:18
hemanthraviin this eg, the chain [FW, LB] is between ext-net and N1/N218:18
cathy_How about this? I am going to send an email to the alias18:19
mandeepcathy_: And the order there is specified on lines 204-209 exactly18:19
mandeepcathy_: OK18:19
* regXboi wonders if he's helping or not18:19
* mandeep is wondering the same thing18:20
* regXboi wonders if mandeep is wondering about self or about regXboi :)18:20
* mandeep about myself ;-)18:20
* regXboi quotes "join the club, we've got jackets"18:21
SumitNaiksatamok lets park this for now18:22
songolecathy_: it helps if you explain your implementation briefly as well in the mail.18:22
SumitNaiksatami think mandeep songole hemanthravi feel that this is clarified in the spec, but its not clear to cathy_ and LouisF18:22
cathy_regXboi: I see your reply "I'd say the implicit convention is that ingress is from network through port and egress is through port to network (based on the example)"18:22
LouisFmandeep: it would help if there was text stating the convention for traffic direction18:22
SumitNaiksatamso lets follow up to clarify that18:22
cathy_That is my question18:22
SumitNaiksatam#action SumitNaiksatam to reach out to cathy_ LouisF mandeep songole hemanthravi to clarify on the spec18:23
cathy_I think it is better to make it explict instead of guessing the "implicit"18:23
mandeepThe spec says - On port P1: FW->LB->R1 for ingress traffic18:23
mandeep R1->LB->FW for egress traffic.18:23
regXboimandeep: yes, and that makes the implicit convention that I stated above18:24
mandeepThe Port, the direction, the order are all exactly specified18:24
mandeephence my confusion on what is ambigious?18:24
*** blogan has joined #openstack-meeting-318:24
mandeepthat is why I am not able to parse the question18:24
SumitNaiksatammandeep: okay lets circle back on that18:24
cathy_Today Louis and I have the question on the "implicit", tomorrow other people might have same questions or needs to guess the "implicit". That is my whole purpose of raining this quesiton. Could we make it "explicit"?18:24
SumitNaiksatamcathy_: LouisF: lets circle back today itself, sounds okay?18:25
hemanthraviwould it be less confusing to say P1->FW->LB and LB->FW->P118:25
mandeephemanthravi: I disagree18:25
SumitNaiksatamokay, i think we have to yield to a couple of other sub-topics18:26
regXboimandeep: +118:26
SumitNaiksatam#topic Traffic Steering18:26
LouisFmandeep: that is in the example, would better if added to line 125, 14618:26
*** openstack changes topic to "Traffic Steering (Meeting topic: Networking Advanced Services)"18:26
regXboiSumitNaiksatam: +2 :)18:26
SumitNaiksatamcgoncalves: hi18:26
SumitNaiksatami know we are not pursuing this for Juno18:26
*** nelsnelson has joined #openstack-meeting-318:26
SumitNaiksatambut any quick updates?18:26
SumitNaiksatamor any feedback you need from the team?18:26
*** bradjones has quit IRC18:26
SumitNaiksatamperhaps cgoncalves is not around18:28
SumitNaiksatam#topic Tap18:28
*** openstack changes topic to "Tap (Meeting topic: Networking Advanced Services)"18:28
SumitNaiksatamanil_rao: vinay_yadhav: here?18:28
vinay_yadhavHi18:28
anil_raoHi18:28
vinay_yadhavWe will put up an updated version of the spec this week18:28
SumitNaiksatamvinay_yadhav anil_rao hi, sorry for making you wait for two meetings for this ;-(18:28
SumitNaiksatamvinay_yadhav: ok great18:29
*** banix has joined #openstack-meeting-318:29
vinay_yadhavwith some changes clarifiing some question18:29
*** celttechie_ has joined #openstack-meeting-318:29
SumitNaiksatamvinay_yadhav: thats good, and perhaps an email to the -dev mailing list will draw attention to this topic18:29
vinay_yadhavwe are also checking up on implementation parts of the spec18:30
vinay_yadhavsumit: sure18:30
SumitNaiksatamvinay_yadhav: oh good18:30
SumitNaiksatamvinay_yadhav: we still have the WIP patch?18:30
vinay_yadhavof the code u mean18:30
SumitNaiksatamvinay_yadhav: yeah18:30
vinay_yadhavsumit: we have not put it up18:30
vinay_yadhavbut would like to do it18:31
SumitNaiksatamvinay_yadhav: okay whenever you are ready18:31
SumitNaiksatamvinay_yadhav: anil_rao: thanks for the update18:31
SumitNaiksatam#topic Open Discussion18:31
*** openstack changes topic to "Open Discussion (Meeting topic: Networking Advanced Services)"18:31
SumitNaiksatamwe have hit the hour18:31
*** SridarK has joined #openstack-meeting-318:31
SumitNaiksatamso last week some of the cores mentioned in this meeting that we should reconsider the work here, based on priorities, and in the context of the “incubator” proposal18:32
*** vinay_yadhav has quit IRC18:32
*** harrisonkelly has left #openstack-meeting-318:32
SumitNaiksatamgiven that the direction came pretty late in the cycle, my understanding here is that the team at least wants to get a shot at the patches in J3, and hence we will try to meet the FPF deadline18:33
cathy_SumitNaiksatam: do you know which BP under this umbrella will go to J release?18:33
SumitNaiksatamif we dont meet that we are obviously out18:33
SumitNaiksatamcathy_: good question :-)18:33
s3wongSumitNaiksatam: any more discussion on this (within the cores)? service insertion got a lot of heat last week18:33
*** Sukhdev has quit IRC18:33
SumitNaiksatamcathy_: that said once we have a working implementation, we can decide where to go with it18:33
SumitNaiksatamcathy_: so as a team, we just got to keep working together18:34
cathy_SumitNaiksatam: sure18:34
SumitNaiksatamIMHO it does not matter whether its the main repo or not18:34
songoleSumitNaiksatam: +118:34
SumitNaiksatamas long as we can get the right implementation in, and have some users use it18:34
*** bradjones has joined #openstack-meeting-318:35
*** bradjones has quit IRC18:35
*** bradjones has joined #openstack-meeting-318:35
SumitNaiksatamin general i think it was already suggested in the past that adv services should be a separate service/project18:35
*** eghobo has quit IRC18:35
SumitNaiksatamso this might evolve in that direction, who knows18:35
*** anil_rao has quit IRC18:36
SumitNaiksatami believe our mission in this team was to have clean interfaces defined in neutron to be able to facilitate the integration of services18:36
*** eghobo has joined #openstack-meeting-318:36
SumitNaiksatammost of what we have discussed today is towards that end18:36
SumitNaiksatami dont think any that has changed, right?18:36
cathy_SumitNaiksatam: +118:37
SridarKSumitNaiksatam: +1 without that not sure how things can be even moved out18:37
mandeepSridarK: +118:37
SumitNaiksatamok we are well over18:37
mandeepSumitNaiksatam: +118:37
SumitNaiksatamany other parting thoughts?18:38
SumitNaiksatami am having a bad connection again18:38
SumitNaiksatamthanks all for joining18:38
*** regXboi has left #openstack-meeting-318:39
SumitNaiksatam#endmeeting18:39
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:39
openstackMeeting ended Wed Aug 20 18:39:11 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:39
s3wongbye18:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-08-20-17.33.html18:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-08-20-17.33.txt18:39
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-08-20-17.33.log.html18:39
SumitNaiksatambye18:39
*** cathy_ has quit IRC18:39
*** marun has quit IRC18:39
songolebye18:39
*** songole has left #openstack-meeting-318:39
*** hemanthravi has quit IRC18:39
SumitNaiksatam#startmeeting Networking FWaaS18:39
openstackMeeting started Wed Aug 20 18:39:42 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:39
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:39
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:39
openstackThe meeting name has been set to 'networking_fwaas'18:39
SumitNaiksatam#chairs SridarK badveli garyduan18:40
badvelihello all18:40
SridarKhi all18:40
*** s3wong has quit IRC18:41
SumitNaiksatamlets get started18:41
SumitNaiksatam#topic Action item review18:41
*** openstack changes topic to "Action item review (Meeting topic: Networking FWaaS)"18:41
SumitNaiksatamSridarK: badveli do we have the DVR wiki page?18:42
badveliyes we have some info on the wiki18:42
SridarKyes it is up18:42
SridarK#link https://wiki.openstack.org/wiki/Quantum/FWaaS/FWaaS-DVR18:42
SridarKbadveli: & i put in some basic info and pointers18:42
SridarKSumitNaiksatam: i think we can tweak this more - will do so18:43
*** mandeep has left #openstack-meeting-318:43
SumitNaiksatamSridarK: swee!18:43
SumitNaiksatam*sweet18:44
SridarKthanks to badveli as well18:44
badvelithanks18:44
SumitNaiksatambadveli: yes indeed, thanks!18:45
badvelithanks Sumit, Sridar18:45
SumitNaiksatami believe we didnt have any more action items18:45
SumitNaiksatamlast week that is (apart from the real work we had to do :-))18:45
SumitNaiksatam#topic Bugs18:46
*** openstack changes topic to "Bugs (Meeting topic: Networking FWaaS)"18:46
SumitNaiksatami tried to bug scrub a bit last week as well18:46
*** eghobo has quit IRC18:47
SumitNaiksatamso the highest priority pending bug is a medium one:18:47
SridarKSumitNaiksatam: yes sorry - i have been swamped and could not really take a look at any new bugs18:47
SumitNaiksatam#link https://bugs.launchpad.net/neutron/+bug/133498118:48
SumitNaiksatamSridarK: no worries18:48
SumitNaiksatamother bugs have patches in reviews18:48
*** otherwiseguy has joined #openstack-meeting-318:48
SumitNaiksatami checked with koteswara and i have not gotten a response yet18:48
SumitNaiksatamany other bugs that we shoud discuss here?18:50
SridarKSumitNaiksatam: nothing that i am aware of18:50
badveliSumit: we will wait for the armando fix regarding the router creation and the firewall18:51
SumitNaiksatamSridarK: yeah18:51
*** Sukhdev has joined #openstack-meeting-318:51
SumitNaiksatambadveli: yes, hopefully we can make progress with that issue with that patch18:51
SridarKSumitNaiksatam: have exchanged some comments with armando on that - i think that last review did not yield success18:52
badveliYes Sumit, hopefully the gate failures will not be seen lot of times18:52
SumitNaiksatamSridarK: ah ok, the last i looked i had not see the vote18:52
SumitNaiksatamSridarK: the last patch set you mean?18:53
SridarKyes18:53
SridarKwill experiment once i have my changes for dvr also18:53
badveliSridar: I also went through but not spend too much time18:53
SumitNaiksatamok so lets to the DVR discussion18:54
SumitNaiksatam#topic FWaaS support for DVR18:54
*** openstack changes topic to "FWaaS support for DVR (Meeting topic: Networking FWaaS)"18:54
SumitNaiksatamSridarK: thanks for initiating the WebEx call with the DVR team yesterday18:54
SridarKSumitNaiksatam: np at all18:55
SumitNaiksatamso if i have to summarize:18:55
SumitNaiksatam1. the DVR code will raise an exception if a migration is attempted from legacy to DVR or vice-versa if that tenant has a firewall18:56
SumitNaiksatam2. the FWaaS support will conditionally process the DVR and the legacy cases18:57
SumitNaiksatammeaning we will support both scenarios18:57
SumitNaiksatamthough, the approved spec does not commit to doing this in a concurrent manner18:58
SridarKSumitNaiksatam: we just rely on the basic support for DVR we are adding for (2)18:58
badveliI think with patch and the exception18:59
SumitNaiksatamso, the current PoA is to either support FWaaS for all routers in DVR or legacy mode, but not in mixed-mode18:59
SumitNaiksatameverybody agree with the above, or are there any other nuances?18:59
badveliSumit: Looks like with our patch we should be able to support both18:59
badvelimixed mode should be automatically taken care19:00
*** LouisF has quit IRC19:00
SumitNaiksatambadveli: okay, but we have not mentioned that in the spec19:00
SumitNaiksatambadveli: so we will claim that it works only after we have tested it19:00
SumitNaiksatammore of a question for the team19:00
badveliYes we have written down some thing like that on wiki19:00
SridarKSumitNaiksatam: on the PoA - from the discussion not sure that we can avoid the mixed mode from yesterday's discussion19:00
badveliSridar and myself will test it out and see19:00
SridarKSumitNaiksatam: the mixed mode - we need to consider what we were calling 2a & 2b19:01
SridarKWhen FWaaS comes after routers - we can check for this in the agent19:01
SumitNaiksatamSridarK: yes, 2a and 2b19:02
SridarKbut if a router comes after fwaas19:02
SumitNaiksatamSridarK: however, i dont think we can just support one and not the other19:02
SridarKthen the check has to be done on the dvr side19:02
SumitNaiksatamhence my suggestion is that we dont claim just yet that we support the mixed-mode19:02
SridarKSumitNaiksatam: ok we will not claim this19:02
SridarKSumitNaiksatam:  but we cannot prevent it19:03
SumitNaiksatamif the theory that the mixed-mode will be supported automatically on account of the FWaaS support for DVR is true, we are in good shape anyway19:03
badveliSridark: I am trying to understand with our patch we should not be in a worry state19:03
badvelisumit: that is what i am saying19:03
SridarKbadveli: hmm19:03
SumitNaiksatambadveli: i have not seen enough of the patch to make a confident assertion19:03
badveliit should be automatically taken care19:03
SridarKthe patch can handle both cases19:04
SridarKbut will not check for state of other routers19:04
SumitNaiksatamSridarK: badveli: i dont have a problem if you want to claim that we support both 2a and 2b, but then you are on the hook :-)19:04
SridarKso basically a router is added - we will check the mode of that router and add the rules in appropriate namespace19:05
SumitNaiksatammy thinking was that since this was not explicitly stated or requested in the blueprint spec, it was not a requirement19:05
badveliSridar: Right Sumit: We will check that and figure out19:05
SridarKbut we are not checking if this router also conforms with all the other routers in the tenant19:05
SridarKwe can do that19:05
badveliif what ever understanding with DVR team19:05
badveliis the way it is19:06
SridarKbut then DVR has to do that too which i think they did not want to do19:06
SridarKSumitNaiksatam: i think i am trying to say - we could land up in a mixed mode19:07
SridarKSumitNaiksatam: if we don't want to - we have to do something extra to prevent it19:07
badveliSridar: Atleast looks to me the DVR code should give proper triggers19:07
SridarKboth on our side and as well as DVR19:07
*** seizadi has quit IRC19:08
*** emagana has quit IRC19:08
badveliSridark: should we experiment with the patch19:08
SumitNaiksatamSridarK: talking to swami yesterday my understanding was that we do that “something” only if we have to19:08
badveliand see if we it is not sufficient?19:08
*** emagana has joined #openstack-meeting-319:08
SumitNaiksatamSridarK: and that is based on our experience from implementing the base support19:09
SumitNaiksatambadveli: yes, i think i am saying the same thing you are saying19:09
*** banix has quit IRC19:09
badveliYes Sumit19:09
SridarKSumitNaiksatam: yes correct -19:09
badveliWe should do something only if it is needed19:09
badvelithis we will have an idea once we have the patch and test it out19:09
SridarKSumitNaiksatam: i was just pointing out that we will not naturally avoid mixed mode19:10
*** seizadi has joined #openstack-meeting-319:10
SumitNaiksatamSridarK: ah yes19:10
badveliCorrect Sridar and Sumit19:10
SumitNaiksatamso lets discuss the mitigation plan19:10
SumitNaiksatamin case after implemeting the current patch, and experimenting the mixed-mode we realize that there is a hitch19:10
SumitNaiksatamand something that we cannot achieve in the J time frame19:11
SumitNaiksatamwhat is the mitigation?19:11
SumitNaiksatamSridarK: i believe that is what you want to bring up?19:11
SridarKSumitNaiksatam: yes hopefully no issues19:11
SumitNaiksatamSridarK: no, but if there are, what is our mitigation?19:11
SridarKSumitNaiksatam: but in case there is an issue on mixed mode - we can prevent it - for 2b19:12
SridarKSumitNaiksatam: but for full solution we need DVR to prevent it also19:12
SumitNaiksatamSridarK: yes prevent it from FwaaS to address 2b (which is that the firewall is created after the mixed mode routers)19:12
SumitNaiksatamSridarK: yes, which is 2a19:12
SridarKSumitNaiksatam: yes exactly19:12
SridarKSumitNaiksatam: when routers come fwaas19:12
SridarKthen dvr will need to prevent it19:13
*** emagana has quit IRC19:13
SridarKwhich Swami said may not be something easy to do for them19:13
*** emagana has joined #openstack-meeting-319:13
SridarKSumitNaiksatam: i am not sure how common the mixed mode scenario is19:14
SumitNaiksatamSridarK: lets do this19:14
SumitNaiksatamSridarK: lets send an email to swami and team about 2a stating what we propose as the mitigation plan19:14
SridarKSumitNaiksatam: sounds good19:15
SumitNaiksatamSridarK: and again, its a mitigation plan, not the main plan19:15
SridarKSumitNaiksatam: yes worst case scenario19:15
SumitNaiksatamSridarK: yes19:15
SridarKSumitNaiksatam: will do so19:15
SridarKSumitNaiksatam: meanwhile i am revising the changes and we will get more testing19:16
SumitNaiksatam#action SridarK badveli to send email to DVR team/Swami with a proposal on the mitigation plan for scenarion 2a (firewall is present, and then mixed-mode router creation is attempted)19:16
SridarKdone19:16
SumitNaiksatamSridarK: nice19:16
*** bradjones has quit IRC19:16
SumitNaiksatamso going back to 119:16
*** badveli has quit IRC19:16
SumitNaiksatamdo we need to support the get_firewalls()?19:17
*** bradjones has joined #openstack-meeting-319:17
SridarKSumitNaiksatam: yes we have something like get_firewall_count()19:17
*** bradjones has quit IRC19:17
*** bradjones has joined #openstack-meeting-319:17
SridarKSumitNaiksatam: Swami pinged me yesterday - i pointed him to plugin methods to see if that works19:17
SumitNaiksatamSridarK: ah cool19:17
*** badveli has joined #openstack-meeting-319:17
SumitNaiksatamSridarK: you are right, the count would work just fine19:17
SridarKSumitNaiksatam: u have added things earlier which should work19:17
badveliSorry i missed19:18
badvelinetwork was down19:18
SridarKSumitNaiksatam: worst case we can tweak one of these19:18
SumitNaiksatambadveli: no worries19:18
SridarKbadveli: no worries - will update u when we talk in the eve19:18
SumitNaiksatambadveli: SridarK mentioned that he reached out Swami yesterday19:18
SridarKSumitNaiksatam: rather Swami pinged me19:19
SumitNaiksatambadveli: my question was whether we need anything additional for supporting migration scenario 119:19
SumitNaiksatambadveli: SridarK’s suggestion is to use get_firewall_count()19:19
*** celttechie_ has quit IRC19:19
SumitNaiksatamSridarK: badveli can we document this on the wiki as well?19:19
SridarKSumitNaiksatam: sounds good19:19
SumitNaiksatamand perhaps point the DVR team to point to this19:20
SridarKSumitNaiksatam: ok19:20
SumitNaiksatamSridarK: thanks19:20
SridarKSumitNaiksatam: np at all19:21
badveliPlugin uses this to know about the firewall, right and raise exception19:21
SridarKbadveli: from the router plugin they will query the fwaas plugin19:21
badveliYes19:21
SumitNaiksatam#action SridarK to add scenarion 1 FWaaS support details to DVR wiki, the suggestion is for the DVR code to call get_firewall_count() function19:22
SumitNaiksatamSridarK: also, i think we should request the DVR team to cross reference our wiki page from their wiki page (if they have one)19:22
SridarKSumitNaiksatam: yes - they do have one - we can request Swami for that19:23
SumitNaiksatamthat will hopefully ensure propose visibility19:23
SumitNaiksatam#action SridarK to request Swami to cross link FWaaS DVR support wiki page from the DVR wiki page19:23
SumitNaiksatamok anything more to discuss on the DVR support?19:24
SridarKSumitNaiksatam: nothing more - badveli and i will continue on this19:24
SumitNaiksatamSridarK badveli thanks for the update on this19:25
SumitNaiksatambut do we have a working DVR setup now?19:25
badvelinothing major, i hope everything works as expected19:25
badveliWe have a single node setup19:25
SumitNaiksatambadveli: ah thats good19:26
SumitNaiksatamSridarK: we had plans to move to the two node setup as well?19:26
SridarKSumitNaiksatam: yes not been able to do this19:26
badvelisorry my other server was taken by some one elase19:26
badvelielse i have only one server as of now19:26
SridarKSumitNaiksatam: hoping after this Aug 21 deadline - can may be do that trip to Sacremento to get a handle on the multinode19:27
SumitNaiksatamSridarK: okay, perhaps good to socialize this plan with Swami as well19:27
SumitNaiksatami have a hard stop at 12.30 PDT19:28
SridarKSumitNaiksatam: but i too need to get another server and try this out19:28
SumitNaiksatamSridarK: yes that will be really good (i think we need that)19:28
SumitNaiksatam#topic Service Objects19:28
*** openstack changes topic to "Service Objects (Meeting topic: Networking FWaaS)"19:28
badveliyes i have been waiting19:28
SumitNaiksatambadveli: i know you are waiting on reviews19:28
badvelii have some minor comments19:28
badvelithat will be addressed19:28
*** emagana has quit IRC19:28
SumitNaiksatambadveli: but the DVR work has taken higher priority19:28
SumitNaiksatambadveli: great, i will try to get to it at the earliest19:29
SridarKSumitNaiksatam: i too am lax on this - i have promised badveli something real soon19:29
*** emagana has joined #openstack-meeting-319:29
SumitNaiksatambadveli: that said, the lbaas stuff may or may not be in the main tree in Juno19:29
SumitNaiksatambadveli: same thing with VPN19:29
badvelithanks sumit19:29
SumitNaiksatambadveli: so we have to see where the discussion goes19:29
SumitNaiksatamfor now we stay on the message19:30
badvelisumit you mean fwaas?19:30
SumitNaiksatambadveli: yes, for all of lbaas, vpnaas and fwaas19:30
SumitNaiksatamok lets call it there for today19:30
badvelibut we have the spec approved in juno19:30
SumitNaiksatamthanks all for joining19:30
SridarKsounds good19:31
SumitNaiksatambadveli: yes, hence we keep moving forward, unless we are told otherwise19:31
SumitNaiksatambadveli: the specs are approved for lbaas and vpnaas as well19:31
SumitNaiksatambadveli: also for GBP :-)19:31
SumitNaiksatamits kind of unsettling and frustrating19:31
badvelithanks Sumit, atleast  i am sure we get some reviews by today or tomorrow19:31
badveliif i can reach our team and some core people19:32
SumitNaiksatambadveli: yes, we have time until sept 5th for review if the direction is to keep this in the main tree19:32
SumitNaiksatamso that is not an issue19:32
badvelifine sumit19:32
badvelii was worried if we cannot get the review in time19:32
SumitNaiksatamalirghty then19:32
SumitNaiksatambye all19:32
SumitNaiksatam#endmeeting19:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:32
openstackMeeting ended Wed Aug 20 19:32:54 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:32
SridarKbye all19:32
badvelias you are mentioning i am relying on you for this19:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-08-20-18.39.html19:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-08-20-18.39.txt19:32
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-08-20-18.39.log.html19:33
badvelibye19:33
*** pcm_ has left #openstack-meeting-319:33
*** emagana has quit IRC19:34
*** mspreitz has quit IRC19:34
*** marun has joined #openstack-meeting-319:36
*** jtomasek has quit IRC19:38
*** mfer has quit IRC19:38
*** mfer has joined #openstack-meeting-319:39
*** marun has quit IRC19:40
*** badveli has quit IRC19:47
*** jcoufal has joined #openstack-meeting-319:48
*** bradjones has quit IRC19:49
*** MaxV has joined #openstack-meeting-319:51
*** celttechie_ has joined #openstack-meeting-319:53
*** bradjones has joined #openstack-meeting-319:53
*** bradjones has quit IRC19:53
*** bradjones has joined #openstack-meeting-319:53
*** jacalcat has joined #openstack-meeting-319:57
*** marun has joined #openstack-meeting-319:57
*** jacalcat has left #openstack-meeting-320:01
*** bradjones has quit IRC20:04
*** SridharR_ has joined #openstack-meeting-320:04
*** SridharRamaswamy has quit IRC20:05
*** harrisonkelly has joined #openstack-meeting-320:13
*** marun has quit IRC20:16
*** marun has joined #openstack-meeting-320:18
*** Sukhdev has quit IRC20:20
*** emagana has joined #openstack-meeting-320:30
*** Longgeek_ has quit IRC20:31
*** emagana has quit IRC20:31
*** emagana has joined #openstack-meeting-320:31
*** bradjones has joined #openstack-meeting-320:31
*** bradjones has quit IRC20:31
*** bradjones has joined #openstack-meeting-320:31
*** thangp has quit IRC20:42
*** SridharR_ has quit IRC20:43
*** jtomasek has joined #openstack-meeting-320:48
*** SridharRamaswamy has joined #openstack-meeting-320:51
*** mfer has quit IRC20:54
*** harrisonkelly has quit IRC20:54
*** SridharR_ has joined #openstack-meeting-321:03
*** SridharR_ has quit IRC21:03
*** SridharRamaswamy has quit IRC21:06
*** nelsnelson has quit IRC21:11
*** peristeri has quit IRC21:11
*** MaxV has quit IRC21:13
*** emagana has quit IRC21:15
*** SridharRamaswamy has joined #openstack-meeting-321:16
*** emagana has joined #openstack-meeting-321:16
*** emagana has quit IRC21:20
*** asahlin has quit IRC21:22
*** thomasem has quit IRC21:25
*** lblanchard has quit IRC21:32
*** ivar-lazzaro has quit IRC21:32
*** SridharRamaswamy has quit IRC21:39
*** jtomasek has quit IRC21:39
*** MaxV has joined #openstack-meeting-321:40
*** marun has quit IRC21:42
*** carl_baldwin has quit IRC21:43
*** julim has quit IRC21:52
*** emagana has joined #openstack-meeting-321:55
*** otherwiseguy has quit IRC21:59
*** flaper87 is now known as flaper87|afk22:02
*** armax has quit IRC22:04
*** TravT has joined #openstack-meeting-322:04
*** SumitNaiksatam_ has joined #openstack-meeting-322:09
*** emagana has quit IRC22:11
*** emagana has joined #openstack-meeting-322:11
*** SumitNaiksatam has quit IRC22:11
*** SumitNaiksatam_ is now known as SumitNaiksatam22:11
*** emagana has quit IRC22:16
*** jpomero has quit IRC22:17
*** banix has joined #openstack-meeting-322:18
*** seizadi has quit IRC22:18
*** celttechie_ has quit IRC22:19
*** seizadi has joined #openstack-meeting-322:24
*** emagana has joined #openstack-meeting-322:28
*** otherwiseguy has joined #openstack-meeting-322:28
*** david-lyle has quit IRC22:29
*** david-lyle has joined #openstack-meeting-322:29
*** shwetaap has quit IRC22:42
*** armax has joined #openstack-meeting-322:44
*** asahlin has joined #openstack-meeting-322:46
*** celttechie_ has joined #openstack-meeting-322:51
*** MaxV has quit IRC22:51
*** rcleere has quit IRC22:56
*** armax has quit IRC22:59
*** emagana has quit IRC23:02
*** emagana has joined #openstack-meeting-323:03
*** carl_baldwin has joined #openstack-meeting-323:06
*** emagana has quit IRC23:07
*** SridharRamaswamy has joined #openstack-meeting-323:07
*** pballand has quit IRC23:12
*** shakamunyi has quit IRC23:13
*** banix has quit IRC23:15
*** eghobo has joined #openstack-meeting-323:17
*** amotoki has quit IRC23:23
*** banix has joined #openstack-meeting-323:25
*** rudrarugge has quit IRC23:30
*** alexpilotti has quit IRC23:34
*** david-lyle has quit IRC23:34
*** carl_baldwin has quit IRC23:35
*** eghobo has quit IRC23:36
*** dhellmann has quit IRC23:49
*** tsufiev has quit IRC23:49
*** tsufiev has joined #openstack-meeting-323:49
*** eghobo has joined #openstack-meeting-323:50
*** dhellmann has joined #openstack-meeting-323:50
*** SumitNaiksatam has quit IRC23:57

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