You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
When the vlan and vxlan both exist in env, and l2population and arp_responder are enabled, if we update a port's ip address from vlan network, there will be arp responder related flows added into br-tun, this will cause too many arp reply for one arp request, and vm connections will be unnormal. Closes-Bug: #1824504 Change-Id: I1b6154b9433a9442d3e0118dedfa01c4a9b4740b (cherry picked from commit
|2 years ago|
|rpc_manager||6 years ago|
|README||8 years ago|
|__init__.py||8 years ago|
|db.py||5 years ago|
|mech_driver.py||2 years ago|
|rpc.py||4 years ago|
Neutron ML2 l2 population Mechanism Drivers
l2 population (l2pop) mechanism drivers implements the ML2 driver to improve
open source plugins overlay implementations (VXLAN with Linux bridge and
GRE/VXLAN with OVS). This mechanism driver is implemented in ML2 to propagate
the forwarding information among agents using a common RPC API.
More informations could be found on the wiki page .
VXLAN Linux kernel:
The VXLAN Linux kernel module provide all necessary functionalities to populate
the forwarding table and local ARP responder tables. This module appears on
release 3.7 of the vanilla Linux kernel in experimental:
- 3.8: first stable release, no edge replication (multicast necessary),
- 3.9: edge replication only for the broadcasted packets,
- 3.11: edge replication for broadcast, multicast and unknown packets.
Note: Some distributions (like RHEL) have backported this module on precedent
The OVS OpenFlow tables provide all of the necessary functionality to populate
the forwarding table and local ARP responder tables.
A wiki page describe how the flow tables did evolve on OVS agents:
-  without local ARP responder
-  with local ARP responder. /!\ This functionality is only available since
the development branch 2.1. It's possible
to disable (enable by default) it through
the flag 'arp_responder'. /!\
Note: A difference persists between the LB and OVS agents when they are used
with the l2-pop mechanism driver (and local ARP responder available). The
LB agent will drop unknown unicast (VXLAN bridge mode), whereas the OVS
agent will flood it.