Looking at project Calico, I don’t know if what they do is similar to what the people from triple-o & ironic do with the neutron-dhcp-agent. I believe we should ask them before deprecation.
I added their tags to the subject. AFAIK TripleO/Ironic was patching neutron-dhcp-agent too. For project Calico, why do you need no netns and why do you patch it? Kevin, thanks for pointing that out. Best, Miguel Ángel Ajo On Monday, 23 de March de 2015 at 7:34, Miguel Ángel Ajo wrote: > +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" <amul...@redhat.com > > (mailto:amul...@redhat.com)> 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: > > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > (mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe) > > >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > (mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe) > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > (mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe) > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
