Re: [ovs-dev] VLAN tenant network patches

2018-11-15 Thread Ankur Sharma
, 2018 1:06:34 AM To: Gurucharan Shetty; Numan Siddique Cc: Ankur Sharma; ovs dev Subject: Re: [ovs-dev] VLAN tenant network patches Thanks for looking at this and keeping it moving forward. I'm also fine with both ways of implementing the feature, and of course, having distributed E/W for VLAN

Re: [ovs-dev] VLAN tenant network patches

2018-11-15 Thread Miguel Angel Ajo Pelayo
Thanks for looking at this and keeping it moving forward. I'm also fine with both ways of implementing the feature, and of course, having distributed E/W for VLAN is great, It'd be amazing, based on not duplicating interfaces, that the implementations don't interfere each other, and that numan's

Re: [ovs-dev] VLAN tenant network patches

2018-11-14 Thread Guru Shetty
Okay. I want to make sure that we don't end up with 3 gateway implementations. We currently have 2. So when you are adding this new feature, please do NOT make it an independent feature which only works for your use case. It will be a maintenance headache otherwise. Instead, it has to be looked at

Re: [ovs-dev] VLAN tenant network patches

2018-11-14 Thread Ankur Sharma
Hi Guru, Sure, providing more explanation. Q. What are we trying to solve? Ans. Getting distributed routing to work for vlan backed networks through OVN. Q. Disconnect wrt OVN capabilities for above task? Ans. OVN lacks in certain areas wrt how to forward the packets "correctly/efficiently"

Re: [ovs-dev] VLAN tenant network patches

2018-11-12 Thread Guru Shetty
On Sun, 11 Nov 2018 at 21:02, Ankur Sharma wrote: > Hi Guru, > > Thanks for spending time in understanding the proposal and drafting your > understanding as well. > Thanks Numan for pitching in. > > Some comments (trying to keep them as brief as possible). > > a. On a high level, we are trying

Re: [ovs-dev] VLAN tenant network patches

2018-11-11 Thread Ankur Sharma
Hi Guru, Thanks for spending time in understanding the proposal and drafting your understanding as well. Thanks Numan for pitching in. Some comments (trying to keep them as brief as possible). a. On a high level, we are trying to do following: "Distributed router functionality for vlan

Re: [ovs-dev] VLAN tenant network patches

2018-11-09 Thread Mark Michelson
On 11/09/2018 04:16 PM, Guru Shetty wrote: > Ankur's proposal: > == > > Though the complete patches do not exist, Ankur wants to solve the problem > 1 by having a chassis specific MAC. So when packet leaves a hypervisor for > east-west

Re: [ovs-dev] VLAN tenant network patches

2018-11-09 Thread Guru Shetty
> > Ankur's proposal: > > == > > > > Though the complete patches do not exist, Ankur wants to solve the > problem > > 1 by having a chassis specific MAC. So when packet leaves a hypervisor > for > > east-west routing, it uses a unique mac. The disadvantage with this > > proposal is

Re: [ovs-dev] VLAN tenant network patches

2018-11-09 Thread Mark Michelson
Thanks for the summary Guru. I have one question down below. On 11/09/2018 02:45 PM, Guru Shetty wrote: I have tried to summarize the problem statement that Numan and Ankur are trying to solve here based on my understanding so far. Please correct me and I will revise it along. Current feature

[ovs-dev] VLAN tenant network patches

2018-11-09 Thread Guru Shetty
I have tried to summarize the problem statement that Numan and Ankur are trying to solve here based on my understanding so far. Please correct me and I will revise it along. Current feature set in OVN. == A logical switch should only have one localnet logical port. If a