dragonflow/dragonflow/neutron
eran gampel b12d5ac014 Unicast reactive L3 flows to the correct tunnel port
In order to avoid flooding and learning for the L3 traffic The
controller marks in the flow the address of the destination VM compute
Node.
We use local vlan mapping to map the tunnel ports destination ip
In the tunnel bridge unicast_to_tunnel table we pre populate match for
the mapped vlan tag and the remote tunnel port.
This solution is needed only for software base tunneling (GRE,VxLAN..)
and not for VLAN base segmentation.
The proposed VLAN mapping is totally isolated from the integration br
VLAN mapping, different pipeline (NORMAL, Openflow).

Closes-Bug: 1480760
(merged form commit 85b0928b84)

Change-Id: Ieaf07ad6fdb6f9d24652ea05444a10a7860b386c
2015-09-07 12:28:09 +03:00
..
agent Unicast reactive L3 flows to the correct tunnel port 2015-09-07 12:28:09 +03:00
common Revert " Neutron main line compatibility patch for liberty." 2015-06-16 18:43:44 +03:00
services Align with neutron stable/kilo 2015-06-17 13:26:27 +03:00
__init__.py Set Up the neutron l3 sdn addon using neutron as library 2015-03-01 18:16:07 +02:00