la.org/show_bug.cgi?id=14328
https://code.google.com/p/chromium/issues/detail?id=22423
...
For Mesos systems, here is what I suggest we do: we using something like
OVS or one of the many alternative vswitches or vrouters or bridges to
assign an IP per task or an IP per executor. Then use default por
some prefer something simple (e.g. search.mesos), while others some
> more complex (search.prod.europe.mesos). If you have preferences, please
> add them at https://github.com/mesosphere/mesos-dns/issues
>
> Thanks
>
> On Sun, Jan 25, 2015 at 3:19 AM, Tom Arnfeld wrote:
>
> &g
few alternatives. For
example some prefer something simple (e.g. search.mesos), while others some
more complex (search.prod.europe.mesos). If you have preferences, please
add them at https://github.com/mesosphere/mesos-dns/issues
Thanks
On Sun, Jan 25, 2015 at 3:19 AM, Tom Arnfeld wrote:
> Tha
wrote:
> A few days ago, we open sourced a simple DNS server for Mesos clusters that
> automatically draws information from the Mesos master(s). It should be
> helpful for service discovery in multi-framework clusters.
> The code: https://github.com/mesosphere/mesos-dns
&
A few days ago, we open sourced a simple DNS server for Mesos clusters that
automatically draws information from the Mesos master(s). It should be
helpful for service discovery in multi-framework clusters.
The code: https://github.com/mesosphere/mesos-dns
Docs: https://mesosphere.github.com/mesos
