yahoo-eng-team team mailing list archive

[Rodolfo Alonso <1518392@xxxxxxxxxxxxxxxxxx>]

Bug closed due to lack of activity, please feel free to reopen if
needed.

** Changed in: neutron
       Status: Triaged => Fix Released

** Changed in: neutron
       Status: Fix Released => Won't Fix

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

Title:
  [RFE] Enable arp_responder without l2pop

Status in neutron:
  Won't Fix

Bug description:
  Remove the dependency between arp_responder and l2_pop.
  arp_responder should be enabled without enabling l2_pop.
  setup arp_responder on OVS integration bridge

  To enable arp_responder, we only need port's MAC and IP Address and no tunnel ip(So no need for l2pop). 
  Currently agents use l2pop notifications to create ARP entries. With the new approach, agents can use
  port events(create, update and delete) to create ARP entry and without l2pop notifications.

  The advantages with this approach for both linuxbridge and OVS agent -
  1) Users can enable arp_responder without l2pop 
  2) Support ARP for distributed ports(DVR and HA).
     Currently, ARP is not added for these ports.
     This is a fix for https://bugs.launchpad.net/neutron/+bug/1661717

  This allows to create ARP entries on OVS integration bridge.

  Advantages for OVS agent, if ARP entries are setup on integration bridge(br-int) rather than on tunneling bridge(br-tun)
  1) It enables arp_responder for all network types(vlans, vxlan, etc)
     arp_responder based on l2pop is supported for only overlay networks.
  2) ARP can be resolved within br-int.
  3) ARP packets for local ports(ports connected to same br-int) will be resolved
     in br-int without broadcasting to actual ports connected to br-int.

  
  Already submitted https://review.openstack.org/#/c/248177/ for this.

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