I did hear of one use case.[1] :-) In all seriousness, it seems like our abstraction over executing processes must be leaking quite a bit if we can't handle a no-namespace deployment. It seems like running a command without "ip netns" in front of it shouldn't be that much harder. Or am I misunderstanding where the special-casing issues are?
1. http://lists.openstack.org/pipermail/openstack-dev/2015-March/059538.html On Fri, Mar 20, 2015 at 3:26 PM, Assaf Muller <amul...@redhat.com> wrote: > > > ----- Original Message ----- > > Tempest tests fail when not using namespaces, so I'm not sure how well > we're > > even testing that codepath anymore. > > Hrmph, I meant to mention that the code path is basically untested but > forgot > to do that when I sent the email. > > > > > doug > > > > > > > On Mar 20, 2015, at 3:19 PM, Brian Haley <brian.ha...@hp.com> wrote: > > > > > > On 03/20/2015 02:57 PM, Assaf Muller 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. > > > > > > This is a recent Neutron bug where someone is not using namespaces, so > they > > > exist: > > > > > > https://bugs.launchpad.net/neutron/+bug/1428007 > > > > > >> 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. > > > > > > +1 from me for deprecation. > > > > > > -Brian > > > > > > > > > > __________________________________________________________________________ > > > 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 > > > > > > > __________________________________________________________________________ > > 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 > > > > __________________________________________________________________________ > 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 > -- Kevin Benton
__________________________________________________________________________ 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
