+1 for deprecation if people don’t have use cases / good reasons to keep it, I
don’t know
and I can’t think of any, but that doesn’t mean they don’t exist.
Miguel Ángel Ajo
On Monday, 23 de March de 2015 at 2:34, shihanzhang wrote:
> +1 to deprecate this option
>
> At 2015-03-21 02:57:09, "Assaf Muller" <[email protected]> wrote: >Hello
> everyone, > >The use_namespaces option in the L3 and DHCP Neutron agents
> controls if you >can create multiple routers and DHCP networks managed by a
> single L3/DHCP agent, >or if the agent manages only a single resource. > >Are
> the setups out there *not* using the use_namespaces option? I'm curious as
> >to why, and if it would be difficult to migrate such a setup to use
> namespaces. > >I'm asking because use_namespaces complicates Neutron code for
> what I gather >is an option that has not been relevant for years. I'd like to
> deprecate the option >for Kilo and remove it in Liberty. > > >Assaf Muller,
> Cloud Networking Engineer >Red Hat >
> >__________________________________________________________________________
> >OpenStack Development Mailing List (not for usage questions) >Unsubscribe:
> [email protected]?subject:unsubscribe
> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: [email protected]?subject:unsubscribe
> (mailto:[email protected]?subject:unsubscribe)
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
