yahoo-eng-team team mailing list archive

[Ihar Hrachyshka <1639879@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: neutron
     Importance: Low
     Assignee: Ihar Hrachyshka (ihar-hrachyshka)
         Status: Confirmed


** Tags: deprecation l3-ha

** Changed in: neutron
     Assignee: (unassigned) => Ihar Hrachyshka (ihar-hrachyshka)

** Changed in: neutron
       Status: New => Confirmed

** Changed in: neutron
   Importance: Undecided => Low

** Tags added: deprecation l3-ha

-- 
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:
  Confirmed

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