You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Timothy St. Clair (JIRA)" <ji...@apache.org> on 2014/05/15 04:25:25 UTC
[jira] [Commented] (MESOS-1324) Create a network isolator based on
port mapping
[ https://issues.apache.org/jira/browse/MESOS-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998388#comment-13998388 ]
Timothy St. Clair commented on MESOS-1324:
------------------------------------------
It sounds to me like you are recreating some of the work that is done by either fleet or geard.
https://github.com/openshift/geard/blob/master/docs/linking.md
> Create a network isolator based on port mapping
> -----------------------------------------------
>
> Key: MESOS-1324
> URL: https://issues.apache.org/jira/browse/MESOS-1324
> Project: Mesos
> Issue Type: Improvement
> Components: isolation
> Reporter: Jie Yu
> Assignee: Chi Zhang
> Fix For: 0.20.0
>
>
> Here, we assume that we don't have enough public IPs. As a result, we are not able to assign an individual public IP to each container.
> One solution is to assign the same IP for all containers on a host, and use port mapping to properly redirect network traffic to/from containers. In other words, each container will be assigned a range of ports from the host. The isolator will setup filters to properly redirect packets to/from the corresponding containers based on dst/src ip/ports.
--
This message was sent by Atlassian JIRA
(v6.2#6252)