I treat Mesos as a resource allocator, so while I am aware of these proposed work-around, it would be awesome if we have Mesos do the resource allocations for network interfaces the same way it does for CPU, Memory, Disk, etc.
On Wed, Oct 8, 2014 at 9:28 AM, Tim St Clair <[email protected]> wrote: > Not via mesos directly (at least not that I'm aware of), however it may be > possible if you use Docker and do it indirectly by configuring multiple > bridge adapters || via (https://github.com/jpetazzo/pipework). > > Another option might be Kube on Mesos, I hear that openvswitch exists > under the hood to enable this capability, depending on whether that meets > your requirements. > > Best of Luck, > Tim > > ------------------------------ > > *From: *"Diptanu Choudhury" <[email protected]> > *To: *[email protected] > *Sent: *Tuesday, October 7, 2014 7:09:44 PM > *Subject: *Multiple Network interfaces > > > 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 <http://twitter.com/diptanu> > > > > -- Thanks, Diptanu Choudhury Web - www.linkedin.com/in/diptanu Twitter - @diptanu <http://twitter.com/diptanu>
