[
https://issues.apache.org/jira/browse/MESOS-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044116#comment-14044116
]
Jie Yu commented on MESOS-1324:
-------------------------------
commit e878c74fb6309366d26d9eee2fbccf16ac0617cf
Author: Chi Zhang <[email protected]>
Date: Wed Jun 25 15:06:22 2014 -0700
Added a network isolator based on port mapping.
Added a network isolator using port-range based traffic redirection on
Linux.
- Containers are assigned non-ephemeral ports by the scheduler and
ephemeral ports by the network isolator.
- Virtual ethernet devices and traffic control filters are set up so
that network traffic in and out of the containers is isolated based on
the ports assigned to them.
- Containers run inside their own network namespaces with separate
network stacks, from which per-container network statistics can be
retrieved.
A joint work with:
- Cong Wang ([email protected])
- Jie Yu ([email protected])
- Ian Downes ([email protected])
Review: https://reviews.apache.org/r/21594
> 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
>
> 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)
