Le 08/07/2016 19:18, Rick Jones a écrit :
> On 07/08/2016 01:01 AM, Nicolas Dichtel wrote:
[snip]
>> Do you have a script or something else to easily reproduce this problem?
>
> Do you mean for my much older, slightly different stuff done in HP Public
> Cloud,
> or for what Phil (?) is doing pres
On 07/08/2016 01:01 AM, Nicolas Dichtel wrote:
Those 300 routers will each have at least one namespace along with the dhcp
namespaces. Depending on the nature of the routers (Distributed versus
Centralized Virtual Routers - DVR vs CVR) and whether the routers are supposed
to be "HA" there can be
On 07/07/2016 01:28 PM, Rick Jones wrote:
On 07/07/2016 09:34 AM, Eric W. Biederman wrote:
Rick Jones writes:
300 routers is far from the upper limit/goal. Back in HP Public
Cloud, we were running as many as 700 routers per network node (*),
and more than four network nodes. (back then it was
Rick Jones writes:
> On 07/07/2016 09:34 AM, Eric W. Biederman wrote:
>> Rick Jones writes:
>>> 300 routers is far from the upper limit/goal. Back in HP Public
>>> Cloud, we were running as many as 700 routers per network node (*),
>>> and more than four network nodes. (back then it was just th
Le 07/07/2016 18:16, Rick Jones a écrit :
> On 07/07/2016 08:48 AM, Phil Sutter wrote:
>> On Thu, Jul 07, 2016 at 02:59:48PM +0200, Nicolas Dichtel wrote:
>>> Le 07/07/2016 13:17, Phil Sutter a écrit :
>>> [snip]
The issue came up during OpenStack Neutron testing, see this ticket for
refe
On 07/07/2016 09:34 AM, Eric W. Biederman wrote:
Rick Jones writes:
300 routers is far from the upper limit/goal. Back in HP Public
Cloud, we were running as many as 700 routers per network node (*),
and more than four network nodes. (back then it was just the one
namespace per router and netw
Rick Jones writes:
> On 07/07/2016 08:48 AM, Phil Sutter wrote:
>> On Thu, Jul 07, 2016 at 02:59:48PM +0200, Nicolas Dichtel wrote:
>>> Le 07/07/2016 13:17, Phil Sutter a écrit :
>>> [snip]
The issue came up during OpenStack Neutron testing, see this ticket for
reference:
http
On 07/07/2016 08:48 AM, Phil Sutter wrote:
On Thu, Jul 07, 2016 at 02:59:48PM +0200, Nicolas Dichtel wrote:
Le 07/07/2016 13:17, Phil Sutter a écrit :
[snip]
The issue came up during OpenStack Neutron testing, see this ticket for
reference:
https://bugzilla.redhat.com/show_bug.cgi?id=1310795
On Thu, Jul 07, 2016 at 02:59:48PM +0200, Nicolas Dichtel wrote:
> Le 07/07/2016 13:17, Phil Sutter a écrit :
> [snip]
> > The issue came up during OpenStack Neutron testing, see this ticket for
> > reference:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1310795
> Access to this ticket is n
Le 07/07/2016 13:17, Phil Sutter a écrit :
[snip]
> The issue came up during OpenStack Neutron testing, see this ticket for
> reference:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1310795
Access to this ticket is not public :(
Hi,
On Wed, Jul 06, 2016 at 11:58:54PM -0500, Eric W. Biederman wrote:
> Phil Sutter writes:
>
> > Hi Eric,
> >
> > Thanks for your quick and insightful reply rightfully pointing out the
> > lack of rationale behind this change. So let me try to catch up:
>
> Grr. I did not get what you are tr
Phil Sutter writes:
> Hi Eric,
>
> Thanks for your quick and insightful reply rightfully pointing out the
> lack of rationale behind this change. So let me try to catch up:
Grr. I did not get what you are trying to accomplish the first time I
skimmed this and rereading it all again closely I st
Hi Eric,
Thanks for your quick and insightful reply rightfully pointing out the
lack of rationale behind this change. So let me try to catch up:
On Tue, Jul 05, 2016 at 09:44:00AM -0500, Eric W. Biederman wrote:
> Phil Sutter writes:
>
> > Stress-testing OpenStack Neutron revealed poor performa
Phil Sutter writes:
> Stress-testing OpenStack Neutron revealed poor performance of 'ip netns'
> when dealing with a high amount of namespaces. The cause of this lies in
> the combination of how iproute2 mounts NETNS_RUN_DIR and the netns files
> therein and the fact that systemd makes all mount
Hi,
On Tue, Jul 05, 2016 at 04:42:51PM +0200, Phil Sutter wrote:
> Stress-testing OpenStack Neutron revealed poor performance of 'ip netns'
> when dealing with a high amount of namespaces. The cause of this lies in
> the combination of how iproute2 mounts NETNS_RUN_DIR and the netns files
> therei
Stress-testing OpenStack Neutron revealed poor performance of 'ip netns'
when dealing with a high amount of namespaces. The cause of this lies in
the combination of how iproute2 mounts NETNS_RUN_DIR and the netns files
therein and the fact that systemd makes all mount points of the system
shared.
16 matches
Mail list logo