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/10/10 13:40:20 UTC
[jira] [Commented] (MESOS-6014) Create a CNI plugin that provides
port mapping functionality for various CNI plugins.
[ https://issues.apache.org/jira/browse/MESOS-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562335#comment-15562335 ]
Alexander Rukletsov commented on MESOS-6014:
--------------------------------------------
Retargeting this for 1.2, please speak up if you want to land this in 1.1.0.
> Create a CNI plugin that provides port mapping functionality for various CNI plugins.
> -------------------------------------------------------------------------------------
>
> 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
> Labels: mesosphere
>
> 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)