[ovs-dev] [PATCH] ovn-controller: Support vxlan tunnel in ovn

Russell Bryant russell at ovn.org
Thu May 4 02:57:11 UTC 2017


On Wed, May 3, 2017 at 10:17 PM, xurong00037997 <xu.rong at zte.com.cn> wrote:
> Because vxlan envelope have no enough fields to carry pipeline information
> between ovs, so current ovn version do not support vxlan tunnel.
> However, may only vxlan tunnel can be used in some special scenario. so we
> think it is necessary to implement the function of vxlan. For this
> purpose, we do the modifications as follow:
>     1. packets received from vxlan jump to table 29 for outport finding
>     2. add mac-binding information to table 29
> ---
>  ovn/controller/lflow.c    | 51 +++++++++++++++++++++++++++++++++++++++++++++++
>  ovn/controller/lflow.h    |  1 +
>  ovn/controller/physical.c |  9 +++++----
>  3 files changed, 57 insertions(+), 4 deletions(-)
>  mode change 100644 => 100755 ovn/controller/lflow.c
>  mode change 100644 => 100755 ovn/controller/lflow.h
>  mode change 100644 => 100755 ovn/controller/physical.c
>

I'm interested in how you concluded that VXLAN support was needed.
I've been looking at this question pretty extensively and have not
been able to find any good justification for why VXLAN support should
be added to OVN.

Can you expand on what special scenarios you have in mind?

Thanks,

-- 
Russell Bryant


More information about the dev mailing list