You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Alexander Rukletsov (JIRA)" <ji...@apache.org> on 2016/11/03 21:43:58 UTC

[jira] [Updated] (MESOS-6014) Added port mapping CNI plugin.

     [ https://issues.apache.org/jira/browse/MESOS-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Rukletsov updated MESOS-6014:
---------------------------------------
    Summary: Added port mapping CNI plugin.  (was: Create a CNI plugin that provides port mapping functionality for various CNI plugins.)

> Added port mapping CNI plugin.
> ------------------------------
>
>                 Key: MESOS-6014
>                 URL: https://issues.apache.org/jira/browse/MESOS-6014
>             Project: Mesos
>          Issue Type: Epic
>          Components: containerization
>         Environment: Linux
>            Reporter: Avinash Sridharan
>            Assignee: Avinash Sridharan
>            Priority: Blocker
>              Labels: mesosphere
>             Fix For: 1.1.0
>
>
> Currently there is no CNI plugin that supports port mapping. Given that the unified containerizer is starting to become the de-facto container run time, having  a CNI plugin that provides port mapping is a must have. This is primarily required for support BRIDGE networking mode, similar to docker bridge networking that users expect to have when using docker containers. 
> While the most obvious use case is that of using the port-mapper plugin with the bridge plugin, the port-mapping functionality itself is generic and should be usable with any CNI plugin that needs it.
> Keeping port-mapping as a CNI plugin gives operators the ability to use the default port-mapper (CNI plugin) that Mesos provides, or use their own plugin.



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