Hello Adam,
this feature you describe makes sense only if the tenant VMs are also
aggregated in the same rack. Is this your scenario ?
Given that you could have 3 network nodes running the L3-agent, then
you can make some scripting to stick the specific router (linux
namespace) to the specific
Hey everyone,
If we want to implement multiple dedicated neutron routers in multiple
racks (same cloud), is there a means of which I'm unaware that forces
instances to route cross-tenant and public traffic to a neutron node within
the local rack as opposed to load balancing L3 across all neutron
