[ovs-dev] [PATCH v5 0/3] Use VLANs for VLAN packets redirected to a gateway chassis
Miguel Angel Ajo Pelayo
majopela at redhat.com
Tue Jul 10 06:25:45 UTC 2018
Anil, good work!. thank you.
I'm reviewing the patches and the behaviour of the series to make sure
everything is all right.
E/W distributed L3 routing over L2 is an interesting problem I'm
documenting what I see to
share it on this thread.
On Mon, Jun 25, 2018 at 9:33 AM Anil Venkata <anilvenkata at redhat.com> wrote:
> On Sat, Jun 16, 2018 at 12:05 AM, Ben Pfaff <blp at ovn.org> wrote:
> > On Thu, Jun 07, 2018 at 02:59:46PM +0530, vkommadi at redhat.com wrote:
> > > From: Venkata Anil <vkommadi at redhat.com>
> > >
> > > This patch avoids tunneling and instead uses source tenant vlan network
> > > across hypervisors for traffic from vlan network on local hypervisor
> > > towards gateway hypervisor hosting redirect chassiss port.
> > >
> > > On the local hypervisor, when the packet enters logical router ingress
> > > pipeline from tenant vlan network, router will set REGBIT_NAT_REDIRECT
> > > and redirect the packet to gateway hypervisor, which is hosting the
> > > chassis redirect port, using tenant vlan network.
> > > Packet travelling across hypervisors will have source vlan tag and
> > > distributed gateway port MAC as destination MAC (other packet data
> > > unchanged).
> > >
> > > Gateway hypervisor will check the vlan tag and destination MAC and
> > > resubmit it to router logical ingress pipeline for routing and finding
> > > the logical output port(i.e it treats this packet as coming from the
> > > local patch port connected to tenant vlan network for routing).
> > >
> > > No changes done for return path as return path to source hypervisor
> > > always uses tenant vlan networks.
> > Thanks a lot for revising the patch series.
> > We've had a lot of churn in ovn-controller over the last week, and it
> > has caused some patch rejects for this patch series. Would you mind
> > rebasing and reposting it?
> Thanks Ben. Sorry for the delay, I was on vacation. I will rebase it now.
> dev mailing list
> dev at openvswitch.org
More information about the dev