+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
+1 to deprecate this option
At 2015-03-21 02:57:09, Assaf Muller 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
+1 Would like to hear feedback hoping that deprecation is viable.
Carl
On Fri, Mar 20, 2015 at 12:57 PM, Assaf Muller 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
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
Assaf Muller amul...@redhat.com writes:
Hello everyone,
Hi Assaf,
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
Assaf Muller amul...@redhat.com writes:
Hello everyone,
Hi Assaf,
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
- Original Message -
Assaf Muller amul...@redhat.com writes:
Hello everyone,
Hi Assaf,
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
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
Tempest tests fail when not using namespaces, so I'm not sure how well we're
even testing that codepath anymore.
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
- 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
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
11 matches
Mail list logo
