Hi Mesos community, there is a lot of work in progress around virtual routers and custom allocator(s) to enable for every task to have one or more specific, or non-specific IP(v4/v6) addresses assigned to it (long lived for the life of that task on that cluster). The goal is for every mesos task to get a leased IP that it will _ALWAYS_ have. This means we can use standard ports :) since every task will be bound to its own IP.
Essentially we are working on a control plane for the virtual router (on each slave) and a data plane for task to get the IP and a custom allocator to manage it. This work is being done by a bunch of folks/companies as Open Source under Cisco Cloud. So, I wanted to send a quick note (before we circulate the design we have been working on and get coding) if folks would find this interesting? Have already done it? Would like to contribute and help? Any thing else? One thing also (which came out of this collaboration but not just for this feature) is that we are thinking of creating some callback mechanism for the allocator module so we can write in Python or Go the business logic for allocator modules. Not sure if folks have done this or are interested in such a thing or have thought about it at all. Thanks! ~ Joe Stein - - - - - - - - - - - - - - - - - http://www.stealth.ly - - - - - - - - - - - - - - - - -
