Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Deprecate CONF.fixed_range, do dynamic setup
Do dynamic fixed_range setup by pulling the networks that should exist on the host and making the appropriate calls to set up the NAT entries for each network. This allows for non-contiguous subnets to be configured in the fixed_ip space and only configures the NAT rules as they are needed. This also restricts the NAT range to the smallest range required preventing the NAT from impacting subnets that might exist on the external network. DocImpact: For backwards compatibility, Grizzly will still support the CONF.fixed_range option and if set will perform the default logic from Folsom and earlier releases. To use the new dynamic fixed_range setup in Grizzly, set fixed_range='' in your nova.conf. The intention is to remove the CONF.fixed_range option entirely early in the Havana cycle and use the dynamic fixed_range setup from Havana going forward. Change-Id: I4ec111079f7a1d253190e6a6008048f992a53f68 Fixes: bug #741626 bug #966175
- Loading branch information
Showing
3 changed files
with
229 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters