[openstack-dev] [Nova] Bug #741626 - FLAGS.fixed_range is silly

Sam Stoelinga sammiestoel at gmail.com
Fri Mar 8 07:00:22 UTC 2013


I think we had this problem before:
We were using the 172.16.0.0/16 range but client wanted to change to
10.xx.x.xx, it seems this fix would allow that, right?

It seems to make a lot more sense to let it check which networks are
created and do the init for the created networks.

On Fri, Mar 8, 2013 at 12:44 PM, Nathanael Burton <
nathanael.i.burton at gmail.com> wrote:

> Initial review is posted here [1] if you think this is worth fixing for
> Grizzly.
>
> [1] - https://review.openstack.org/23787
> On Mar 4, 2013 2:16 PM, "Nathanael Burton" <nathanael.i.burton at gmail.com>
> wrote:
>
>> I thought of that after I posted the last update. Attached is a hack of
>> my initial patch (not completed).  It doesn't currently add the logic to
>> check if fixed_range is set and a few other things.  It's fairly small in
>> scope, about a dozen changes.
>>
>> Nate
>>
>>
>> On Mon, Mar 4, 2013 at 2:05 PM, Vishvananda Ishaya <vishvananda at gmail.com
>> > wrote:
>>
>>>
>>> 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
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130308/f3973013/attachment.html>


More information about the OpenStack-dev mailing list