Minor Description
Right now, the Aurora scheduler listens on all network interfaces available to the system, but it only chooses one to advertise in zookeeper.
This is a problem in a situation where a server has two IPs: One external, and one internal (LAN). I can access http://<lan-ip>:<aurora port>/scheduler in my browser, but aurora client commands (and scheduler <-> scheduler interaction) use the external network.
I want to be able to tell Aurora to communicate on the internal IP (and ideally, not listen on the external one at all, though that can be done at the firewall level), probably through a command line flag.