diff options
| author | mathrock <nathanael.i.burton.work@gmail.com> | 2013-03-06 16:28:50 -0500 |
|---|---|---|
| committer | mathrock <nathanael.i.burton.work@gmail.com> | 2013-03-12 01:45:25 -0400 |
| commit | 26440ae2cd4c8ffe44beecb6bb0cce19cb43bb7b (patch) | |
| tree | 6eb892252f9e3a7dc09329d55b5a260c2de4f779 /nova/utils.py | |
| parent | ae251b99a3fb6aa99ec8898152d79dfa2c026a92 (diff) | |
| download | nova-26440ae2cd4c8ffe44beecb6bb0cce19cb43bb7b.tar.gz nova-26440ae2cd4c8ffe44beecb6bb0cce19cb43bb7b.tar.xz nova-26440ae2cd4c8ffe44beecb6bb0cce19cb43bb7b.zip | |
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
Diffstat (limited to 'nova/utils.py')
0 files changed, 0 insertions, 0 deletions