Comment 2 for bug 1427893

I'd like more information on the reasoning behind why you believe you need to support 1024 minimum MAC addresses in any particular network namespaces' neighbor table, let alone a hard limit of 8192 MACs. Each Neutron network in a neutron-agents container will live inside of network namespaces, and each namespace has its own MAC garbage collection tunables. The only namespaces where multiple Neutron networks could be seen is inside of a router namespace with multiple networks plugged into that router. Even so, a 'hard' limit of 8192 MACs is a very large collection of networks hooked into any given router -- 8 /22s would be that size, for instance.

More to the point though, I'm not sure that I agree this should be upped substantially in the base OSAD project, and instead feel that the deployer should make use of the sysctl framework to apply per-container adjustments as they see fit if their network density requires them.