[jira] [Updated] (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:all-tabpanel ] Avinash Sridharan updated MESOS-6014: - Target Version/s: 1.1.0 (was: 1.1.1) > 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 >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)
[jira] [Updated] (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:all-tabpanel ] Avinash Sridharan updated MESOS-6014: - Target Version/s: 1.1.1 (was: 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 >Priority: Blocker > 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)
[jira] [Updated] (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:all-tabpanel ] Alexander Rukletsov updated MESOS-6014: --- Priority: Blocker (was: Major) > 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 >Priority: Blocker > 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)
[jira] [Updated] (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:all-tabpanel ] Avinash Sridharan updated MESOS-6014: - Target Version/s: 1.1.0 (was: 1.2.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)
[jira] [Updated] (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:all-tabpanel ] Alexander Rukletsov updated MESOS-6014: --- Target Version/s: 1.1.0 Fix Version/s: (was: 1.1.0) Summary: Create a CNI plugin that provides port mapping functionality for various CNI plugins. (was: Create a CNI plugin that provides port mapping functionality for various CNI plugins) > 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)
[jira] [Updated] (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:all-tabpanel ] Alexander Rukletsov updated MESOS-6014: --- Target Version/s: 1.2.0 (was: 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)