Scheduler is announcing itself on 0.0.0.0

[bobrik]

This is follow-up from #46.

This is not true, 0.0.0.0 is "all ips", not localhost. Because of this mesos cannot reach back to scheduler and framework cannot register itself. This probably works on localhost, but does not work with 3 masters on different hosts.

I think we should pass upid.UPID into scheduler.NewMesosSchedulerDriver to make it more flexible.

[vladimirvivien]

@bobrik So, to clarify, you are suggesting to provide a way to specify an address to bind the scheduler to?

[bobrik]

@vladimirvivien yes, exactly.

[vladimirvivien]

@bobrik I opened a ticket for your suggestion and closing this one.