Is using bridged networking with docker an option. That would map the service port (fixed) to a dynamically assigned port. Granted it will not utilize different nics but it's something.
Sent from my iPhone > On Oct 8, 2014, at 8:52 AM, Jay Buffington <[email protected]> wrote: > > My reading of the code is that this is not supported. > > I have this same problem. I'm trying to work around an issue with a > stubborn application that requires that all instances in a cluster run > on the same port. Therefore, I have 5+ interfaces per slave and I > want task A and task B to bind to the same port on different > interfaces on the same slave. > > Since the ports resource is simply a Range[1] there is nowhere to > stick the IP they belong to. I think to get what you want mesos would > need to introduce a new first class IP resource in the C++ Resources > abstraction[2] which has an IP (Scalar) and a list of ports (Range). > > I opened https://issues.apache.org/jira/browse/MESOS-1874 to track the > work that needs to be done to support this. > > Jay > > [1] https://github.com/apache/mesos/blob/master/include/mesos/mesos.proto#L335 > [2] https://github.com/apache/mesos/blob/master/src/common/resources.cpp > >> On Tue, Oct 7, 2014 at 5:09 PM, Diptanu Choudhury <[email protected]> wrote: >> Hi, >> >> I am wondering if Mesos can offer resources from multiple network >> interfaces? We would like to attach multiple Network Interfaces on EC2 >> instances and would like to bind specific applications that we run on mesos >> on specific interfaces? >> >> So basically I am wondering if Mesos can offer ports from different network >> interfaces on the same slave?? >> >> -- >> Thanks, >> Diptanu Choudhury >> Web - www.linkedin.com/in/diptanu >> Twitter - @diptanu
