On 07/07/2016 01:28 PM, Rick Jones wrote:
On 07/07/2016 09:34 AM, Eric W. Biederman wrote:
Rick Jones <rick.jon...@hpe.com> 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 network). Mileage will of course vary based
on the "oomph" of one's network node(s).
To clarify processes for these routers and dhcp servers are created
with "ip netns exec"?
I believe so, but it would be good to have someone else confirm that, and speak
to your paragraph below.
Yes, the namespace is created and configured, then in the case of dhcp an 'ip
netns exec $namespace dnsmasq ...' is run. Routers typically have a small
daemon running "inside" as well.
If that is the case and you are using this feature as effectively a
lightweight container and not lots vrfs in a single network stack
then I suspect much larger gains can be had by creating a variant
of ip netns exec avoids the mount propagation.
So you're thinking a new command like 'ip netns daemon $namespace ...' ? Or if
there's a better way with other tools today to accomplish this I'd be
interested, as waiting for a new iproute2 to ripple through the distros could
take a while.
-Brian
