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 l3-agent. To see an example of how to migrate a router to a specific l3-agent please look at: https://github.com/openstack/osops-tools-contrib/blob/master/neutron/l3-agent-evacuate.py Saverio 2017-01-25 20:00 GMT+01:00 Adam Lawson <alawson at aqorn.com>: > 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 nodes in all racks? > > Example: > 6 racks,3 dedicated Neutron nodes per rack > > //adam > > Adam Lawson > > Principal Architect, CEO > Office: +1-916-794-5706 > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >