[jira] [Commented] (MESOS-4823) Implement port forwarding in `network/cni` isolator

["Lee Calcote (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15358258#comment-15358258 ] 

Lee Calcote commented on MESOS-4823:
------------------------------------

If port-mapping is implemented in the `network/cni` isolator, what would be the expected behavior when paired with a container runtime isolator (i.e. a rkt container runtime isolator) that already handles port-mapping?

> Implement port forwarding in `network/cni` isolator
> ---------------------------------------------------
>
>                 Key: MESOS-4823
>                 URL: https://issues.apache.org/jira/browse/MESOS-4823
>             Project: Mesos
>          Issue Type: Task
>          Components: containerization
>         Environment: linux
>            Reporter: Avinash Sridharan
>            Assignee: Avinash Sridharan
>            Priority: Critical
>              Labels: mesosphere
>
> Most docker and appc images wish to expose ports that micro-services are listening on, to the outside world. When containers are running on bridged (or ptp) networking this can be achieved by installing port forwarding rules on the agent (using iptables). This can be done in the `network/cni` isolator. 
> The reason we would like this functionality to be implemented in the `network/cni` isolator, and not a CNI plugin, is that the specifications currently do not support specifying port forwarding rules. Further, to install these rules the isolator needs two pieces of information, the exposed ports and the IP address associated with the container. Bother are available to the isolator.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)