6b59cc72a4
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: I125dbc57b90027dc5e99ff0a5d6877843a0b02a5 Maybe the option is in the tree because, in Assaf Muller'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. Change-Id: I9d12b8f4c25ddf91312153f236915c0c14302e2d Related-Bug: #1639879
Welcome!
You have come across a cloud computing network fabric controller. It has identified itself as "Neutron." It aims to tame your (cloud) networking!
External Resources:
The homepage for Neutron is: http://launchpad.net/neutron. Use this site for asking for help, and filing bugs. Code is available on git.openstack.org at <http://git.openstack.org/cgit/openstack/neutron>.
The latest and most in-depth documentation on how to use Neutron is available at: <http://docs.openstack.org>. This includes:
- Neutron Administrator Guide
- Neutron Developer Guide
- Networking Guide
- Neutron API Reference:
- Current Neutron developer documentation is available at:
For help on usage and hacking of Neutron, please send mail to <mailto:openstack-dev@lists.openstack.org>.
For information on how to contribute to Neutron, please see the contents of the CONTRIBUTING.rst file.