Bug 1279612 - Enable configuration of OVS ARP Responder
Enable configuration of OVS ARP Responder
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director (Show other bugs)
8.0 (Liberty)
Unspecified Unspecified
low Severity unspecified
: ---
: 11.0 (Ocata)
Assigned To: Brent Eagles
Shai Revivo
: ZStream
Depends On: 1271336
  Show dependency treegraph
Reported: 2015-11-09 15:57 EST by Brent Eagles
Modified: 2018-01-29 07:52 EST (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1271336
Last Closed: 2017-09-07 18:03:45 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 244801 None None None Never

  None (edit)
Description Brent Eagles 2015-11-09 15:57:44 EST
+++ This bug was initially created as a clone of Bug #1271336 +++

We should be able to explicitly configure the OVS ARP Responder feature. To enable:

 1. Enable L2 population (see https://bugzilla.redhat.com/show_bug.cgi?id=1271335)

 2. set the following value in the OVS Agent configuration for all nodes running an OVS agent:

arp_responder = True
Comment 2 Emilien Macchi 2015-12-01 12:31:08 EST
A patch in TripleO Heat Templates needs to be pushed to enabled this parameter (false by default):
Comment 5 Mike Burns 2016-04-07 16:57:01 EDT
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.
Comment 7 Stephen Gordon 2016-06-09 14:49:18 EDT
Bulk update to reflect scope of Red Hat OpenStack Platform 9 and Red Hat OpenStack Platform does not include this issue (No pm_ack+).
Comment 9 Assaf Muller 2017-01-12 08:43:06 EST
@Brent, would you kindly take care of this? We'd like to see the ability to configure the ARP responder, however it should be off by default at this point. In parallel we'll contact the performance team to see the effect of this knob and make recommendations about the default value in a future release.
Comment 10 Assaf Muller 2017-09-07 18:03:45 EDT
I'm closing this bug, with a greater focus on OVN in a future OSP offering, allocating time and energy in low priority bugs that are specific to ML2/OVS doesn't make sense.

Note You need to log in before you can comment on or make changes to this bug.