Open Stack

On Mar 4, 2013, at 10:32 AM, Nathanael Burton <nathanael.i.burton at gmail.com> wrote:

> On Mon, Mar 4, 2013 at 1:15 PM, Jay Pipes <jaypipes at gmail.com> wrote:
> On 03/04/2013 12:52 PM, Nathanael Burton wrote:
> > Problem 1: Users have to specify the 'fixed_range' in the first place in
> > their nova.conf file, when it shouldn't be necessary as the system (DB
> > networks table) has all the information it needs to set up the NATs
> > correctly.  If this eventually gets implemented we can deprecate and
> > then remove the flag entirely in Havana or future.
> 
> Right. This is kind of what I'm saying... we should just do this now and
> not add any more confusion to the nova.conf options.
> 
> Best
> -jay
> 
> To be clear, you agree that this should be done? 
> 
> Then:
> 
> 1. Keep 'fixed_range' in Grizzly with a new default (?) value of 'dynamic' meaning use the new behavior and completely remove the 'fixed_range' flag in Havana

> 
> or
> 
> 2. Do the dynamic fixed_range automatically and remove 'fixed_range' altogether in Grizzly?


Rather than use 'dynamic' I think we should key of of 'not fixed_range' and default it to none and mark it deprecated. I'd have to see how complex the code is but it seems a bit late to get this into grizzly.

Vish
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130304/63d7ef72/attachment.html>