Currently 'force_gateway_on_subnet' configuration is set to True
by default and enforces the subnet on to the gateway. With the
fix in https://review.openstack.org/#/c/233287/, gateway outside
the subnet can be added, and the configuration option now has
lost its significance.
With this patch, the configuration option is deprecated.
It should be removed in Newton release, and the system should
always allow gateway outside the subnet.
This patch is dependent on the fix for adding gateway outside
the subnet, mentioned above.
DocImpact: 'force_gateway_on_subnet' description should be
updated in the docs and marked as deprecated to be removed in
the Newton release.
Reviewed: https:/ /review. openstack. org/277303 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=3e6d602f542 fc97e64cd5503bf 1ea4e71d648abf
Committed: https:/
Submitter: Jenkins
Branch: master
commit 3e6d602f542fc97 e64cd5503bf1ea4 e71d648abf
Author: Sreekumar S <email address hidden>
Date: Mon Feb 8 12:58:01 2016 +0530
Deprecate 'force_ gateway_ on_subnet' configuration option
Currently 'force_ gateway_ on_subnet' configuration is set to True /review. openstack. org/#/c/ 233287/, gateway outside
by default and enforces the subnet on to the gateway. With the
fix in https:/
the subnet can be added, and the configuration option now has
lost its significance.
With this patch, the configuration option is deprecated.
It should be removed in Newton release, and the system should
always allow gateway outside the subnet.
This patch is dependent on the fix for adding gateway outside
the subnet, mentioned above.
DocImpact: 'force_ gateway_ on_subnet' description should be
updated in the docs and marked as deprecated to be removed in
the Newton release.
Change-Id: I28b3d7add303ee 479fc071c1de142 b0f7811e4e5
Closes-Bug: #1335023
Closes-Bug: #1398768