I would love to see IPv6 support in Mesos for both the executor and scheduler APIs, as well as the master and slave IPC. Does Yandex need support for all of these across the board, or are you primarily looking to enable containers with IPv6? Given the nature of IPv6 auto-configuration, it's likely that you can simply enable MACVLAN per container, get IPv6 "for free", as well as enabling link-local communication so the executor can communicate with the agent.
It may make sense building an IPv4 overlay for the libprocess communication for expediency. If the new scheduler and executor APIs are also difficult to move to IPv6, the HTTP API should work through a simple TCP proxy. On Fri, Jan 29, 2016 at 1:11 PM, Benjamin Mahler <bmah...@apache.org> wrote: > I've un-assigned and removed the shepherd on this, no work has taken place > for some time. > > Glad to see you're using Mesos! There is currently no shepherd for IPv6 > support, but it would be great if you could publish a design document for > feedback after you've assessed what needs to be done to complete this. > > On Mon, Jan 25, 2016 at 4:53 AM, Evers Benno <ben...@yandex-team.ru> wrote: > >> Hello all, >> >> We are currently planning to deploy a mesos cluster for internal use in >> Yandex.Maps. >> >> Since the ability to work on IPv6-only hosts is necessary for us, we are >> planning to start working on the necessary patches in the coming weeks, >> and to contribute our progress. >> >> Work towards full IPv6 support apparently was started a year ago in >> MESOS-1027 (https://issues.apache.org/jira/browse/MESOS-1027), but as >> far as I can tell, the last activity was in June 2015. >> >> Is someone else currently working on this? Or did anyone work on this, >> and encounter unexpected difficulties? >> >> If so, it would likely be a good idea to coordinate with each other, so >> we don't unnecessarily duplicate work and/or mistakes and bugs. >> >> Best regards, >> Benno Evers >>
