I see you point Van, In the other hand, removing it, cleans up lot of conditional code parts (moving parts at the other side), and also the non-netns case is not tested by upstream CI, AFAIK, so it could be broken anytime and we would not notice it.
Miguel Ángel Ajo On Monday, 23 de March de 2015 at 9:25, Van Leeuwen, Robert wrote: > > I think there are valid reasons to not use namespaces: > > Fewer moving parts == less can potentialy fail > > Troubleshooting is easier due to less places to look / need no familiarity > > with namespaces & tools > > If I remember correctly setting up a namespace can get really slow when you > > have a lot of them on a single machine > > > > > > > > > > > > IMHO, those shouldn’t be valid reasons anymore, since they were due > > iproute, or sudo issues > > that have been corrected long ago, and all distros installing neutron are > > supporting netns at this > > Well, you exactly made my point: > There is lots that can and will go wrong with more moving parts. > That they are fixed at the moment does not mean that there will not be a new > bug in the future… > > Cheers, > Robert van Leeuwen > > _______________________________________________ > OpenStack-operators mailing list > openstack-operat...@lists.openstack.org > (mailto:openstack-operat...@lists.openstack.org) > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > >
__________________________________________________________________________ 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
