neutron/neutron/plugins/ml2/drivers/l2pop
Ryan Moats eb09ebc88c Lower l2pop "isn't bound to any segement" log to debug
Per the discussion in bug 1362242, the log statement doesn't
appear to be associated with anything bad happening. Therefore,
this patch lowers the log level from WARNING to DEBUG to avoid
polluting operator's logs.

Change-Id: I55b6d1d30ed2ed55659c9a6809531cfcbc57f17c
Signed-off-by: Ryan Moats <rmoats@us.ibm.com>
Closes-Bug: 1362242
2015-11-11 12:53:26 -06:00
..
rpc_manager Restructure agent code in preparation for decomp 2015-06-26 15:06:49 +00:00
README Implement local ARP responder onto OVS agent 2014-05-19 21:42:11 +02:00
__init__.py Empty files should not contain copyright or license 2014-10-20 00:50:32 +00:00
config.py oslo: migrate to namespace-less import paths 2015-02-05 15:09:32 +01:00
db.py Fix l2pop regression 2015-10-21 09:53:06 -04:00
mech_driver.py Lower l2pop "isn't bound to any segement" log to debug 2015-11-11 12:53:26 -06:00
rpc.py Migrate to oslo.log 2015-03-12 11:22:56 +01:00

README

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 [1].

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
      kernel version.

OpenvSwitch:
------------
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:
- [2] without local ARP responder
- [3] 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.

[1] https://wiki.openstack.org/wiki/L2population_blueprint
[2] https://wiki.openstack.org/wiki/Ovs-flow-logic#OVS_flows_logic
[3] https://wiki.openstack.org/wiki/Ovs-flow-logic#OVS_flows_logic_with_local_ARP_responder