You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jay Buffington (JIRA)" <ji...@apache.org> on 2014/12/18 18:19:13 UTC
[jira] [Commented] (MESOS-1908) Support for Multi-Home NICs
[ https://issues.apache.org/jira/browse/MESOS-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14251915#comment-14251915 ]
Jay Buffington commented on MESOS-1908:
---------------------------------------
I think what you're saying is "Provide network interfaces as resources"
When you launch a task and use, say, port 32123, you own that port for all interfaces (0.0.0.0). We should carve that up a bit more. Two separate tasks should be able to bind to port 32123 on different two separate interfaces, e.g., Task A binds to 127.0.0.1:32123 and Task B binds to 10.1.2.3:32123.
This also would provide for the scheduler use case of "run a task for each interface on the host"
> Support for Multi-Home NICs
> ---------------------------
>
> Key: MESOS-1908
> URL: https://issues.apache.org/jira/browse/MESOS-1908
> Project: Mesos
> Issue Type: Story
> Components: isolation
> Affects Versions: 0.23.0
> Reporter: Ken Sipe
>
> We need to have multihome NIC support in Mesos. There may be other scenarios. At a minimum, we need to have support for a slave to reside on a multihome node. In this scenario, at task launch we need a way to know which IP to bind to. Perhaps there is room for managing the consumption of a NIC.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)