Open Stack

Vish,

Do you think this would be eligible for FFE for Grizzly?  Does it seem
worthwhile?  As I've said above, I can reuse the 'fixed_range' above for
Grizzly and override it to use some string like 'dynamic'. Additionally, we
could mark the flag as deprecated in Grizzly, and then remove it in
Hipster(err...Havana) and use the dynamic fixed_range from that point
forward.

If you think it's worthwhile, but too late for Grizzly that's fine and I
can propose it following the above process for H -> I.

Thanks,

Nate


On Mon, Mar 4, 2013 at 9:01 AM, Thierry Carrez <thierry at openstack.org>wrote:

> Nathanael Burton wrote:
> > Since fixed_range is simply a StrOpt I can just use it and forgo a new
> > opt.  If it's set to 'dynamic' do the new logic otherwise it's a CIDR
> > and do the old backwards compatible logic. Aside from the conf option
> > any other issues with working on this and submitting a patch?
>
> It definitely would be a new feature (as in: expanding the scope of what
> we support), so it requires an exception. That said it's a rather minor
> feature that could almost be seen as a bug.
>
> If the PTL wants it, if the documenters are fine with it, and if the
> implementation makes sure not to change the existing code path, I guess
> I could live with it.
>
> Land it early, though. Back from one week vacation I'm rather joyful,
> but let a few days pass and I'll become grumpy again :)
>
> --
> Thierry Carrez (ttx)
> Release Manager, OpenStack
>
> _______________________________________________
> 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/20130304/5021b707/attachment.html>