You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Avinash Sridharan (JIRA)" <ji...@apache.org> on 2017/03/30 15:36:41 UTC
[jira] [Updated] (MESOS-7326) ship a sample CNI config that
provides a mesos-bridge network, analogous to the default bridge that ships
with Docker
[ https://issues.apache.org/jira/browse/MESOS-7326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Avinash Sridharan updated MESOS-7326:
-------------------------------------
Shepherd: Jie Yu
> ship a sample CNI config that provides a mesos-bridge network, analogous to the default bridge that ships with Docker
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: MESOS-7326
> URL: https://issues.apache.org/jira/browse/MESOS-7326
> Project: Mesos
> Issue Type: Task
> Components: documentation, network
> Reporter: James DeFelice
> Assignee: Avinash Sridharan
> Labels: mesosphere
>
> UCR supports port mapping and marathon now ships an API that lets users specify a `container/bridge` networking mode. by default, this maps to a CNI network called `mesos-bridge`. Mesos should, at least:
> # ship a sample CNI configuration file that requires minimal edits, if any, to enable a `mesos-bridge` CNI network for a vanilla mesos install; like docker, the default bridge defaults to a "host-private" mode of operation
> # clearly document the steps required to enable this default bridge network for simple mesos clusters
> /cc [~jieyu]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)