yahoo-eng-team team mailing list archive

[Subbu <1804136@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Problem statement:

In the current implementation of DVR E/W Routing when the DVR instance
having same mac running in multiple compute node will create mac
movement in the br-int bridge. The way we addressed this issue doesn't
follow any l2/l3 standard. I am proposing a simpler solution for this.

Proposal: Keep br-int as vlan+mac based learning switch. And, set DVR
port connected with br-int as tagged.

Scenario: Please refer https://assafmuller.com/2015/04/ for a
diagrammatic view. Say, blue host running in left compute node trying to
reach orange host running in right compute node. Both the compute node
running DVR and do E/W routing.  Blue host subnet vlan is 10, and Orange
host subnet vlan is 20.

Packet Forwarding:

1. When vlan based mac learning happens in both br-int bridges, there will be two entries with same DVR mac one with vlan 10 and other with 20. Thus no mac-movement issue will not arise.
 
2. When packets send by blue host having vlan 10 reaches the left-dvr, it will route the packet and it send out with vlan 20 to Orange host.

3. br-int in right side will also have two mac entries for the same MAC
one for vlan 10 and another for vlan 20.

4. Since DVR has access to connected to both vlans, packets from
blue/orange host have to hop only the DVR in its compute node.

Please review this proposal will it work and simplify the DVR E/W
routing.

Thanks
Subbu
iimksubbu@xxxxxxxxx

** Affects: neutron
     Importance: Undecided
         Status: New

** Summary changed:

- Industry Standard approach to DVR-E/W routing fixing port/mac movement using 
+ Industry Standard approach for DVR E/W routing issue of port/mac movement by vlan based mac learning

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1804136

Title:
  Industry Standard approach for DVR E/W routing issue of port/mac
  movement by vlan based mac learning

Status in neutron:
  New

Bug description:
  Problem statement:

  In the current implementation of DVR E/W Routing when the DVR instance
  having same mac running in multiple compute node will create mac
  movement in the br-int bridge. The way we addressed this issue doesn't
  follow any l2/l3 standard. I am proposing a simpler solution for this.

  Proposal: Keep br-int as vlan+mac based learning switch. And, set DVR
  port connected with br-int as tagged.

  Scenario: Please refer https://assafmuller.com/2015/04/ for a
  diagrammatic view. Say, blue host running in left compute node trying
  to reach orange host running in right compute node. Both the compute
  node running DVR and do E/W routing.  Blue host subnet vlan is 10, and
  Orange host subnet vlan is 20.

  Packet Forwarding:

  1. When vlan based mac learning happens in both br-int bridges, there will be two entries with same DVR mac one with vlan 10 and other with 20. Thus no mac-movement issue will not arise.
   
  2. When packets send by blue host having vlan 10 reaches the left-dvr, it will route the packet and it send out with vlan 20 to Orange host.

  3. br-int in right side will also have two mac entries for the same
  MAC one for vlan 10 and another for vlan 20.

  4. Since DVR has access to connected to both vlans, packets from
  blue/orange host have to hop only the DVR in its compute node.

  Please review this proposal will it work and simplify the DVR E/W
  routing.

  Thanks
  Subbu
  iimksubbu@xxxxxxxxx

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1804136/+subscriptions