Reviewed: https://review.openstack.org/457680 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8bb94820bd1d95414047ae52165411fe818a8d0e Submitter: Jenkins Branch: master
commit 8bb94820bd1d95414047ae52165411fe818a8d0e Author: Ihar Hrachyshka <[email protected]> Date: Tue Apr 18 07:54:45 2017 -0700 Remove deprecated send_arp_for_ha option Now Neutron always sends three gARPs after address assigned to an interface. Change-Id: I0d44f4cc59e1675b20d0da329faf7fd3ab91acbf Closes-Bug: #1639879 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1639879 Title: Deprecate and remove send_arp_for_ha option Status in neutron: Fix Released Bug description: It puzzles me why we would want to have it configurable. Having it = 0 is just plain bad (it breaks a floating IP roaming around HA routers), having it = 1 may be unsafe if clients miss the update, having it more than 3 (the default) is probably wasteful. That makes me think that maybe we should not have it in the first place. The patch that introduced the option also introduced the feature itself, and does not provide any clue around why we would need it: https://review.openstack.org/#/c/12037/ Maybe the option is in the tree because, in Assaf's words, "we're a bunch of lazy developers that like to shift the responsibility to our poor users that have to deal with thousands of configuration options". I suggest we just move with deprecation and removal here. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1639879/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
