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 2016/04/11 18:00:26 UTC
[jira] [Updated] (MESOS-5130) Enable `newtork/cni` isolator in
`MesosContainerizer` as the default `network` isolator.
[ https://issues.apache.org/jira/browse/MESOS-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Avinash Sridharan updated MESOS-5130:
-------------------------------------
Sprint: Mesosphere Sprint 32
Description: Currently there are no default `network` isolators for `MesosContainerizer`. With the development of the `network/cni` isolator we have an interface to run Mesos on multitude of IP networks. Given that its based on an open standard (the CNI spec) which is gathering a lot of traction from vendors (calico, weave, coreOS) and already works on some default networks (bridge, ipvlan, macvlan) it makes sense to make it as the default network isolator. (was: The CNI network isolator needs to be enabled by default. )
> Enable `newtork/cni` isolator in `MesosContainerizer` as the default `network` isolator.
> ----------------------------------------------------------------------------------------
>
> Key: MESOS-5130
> URL: https://issues.apache.org/jira/browse/MESOS-5130
> Project: Mesos
> Issue Type: Task
> Components: containerization
> Reporter: Avinash Sridharan
> Assignee: Avinash Sridharan
> Labels: mesosphere
>
> Currently there are no default `network` isolators for `MesosContainerizer`. With the development of the `network/cni` isolator we have an interface to run Mesos on multitude of IP networks. Given that its based on an open standard (the CNI spec) which is gathering a lot of traction from vendors (calico, weave, coreOS) and already works on some default networks (bridge, ipvlan, macvlan) it makes sense to make it as the default network isolator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)