[jira] [Commented] (MESOS-4641) Support Container Network Interface (CNI).

["Adam B (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-4641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15779447#comment-15779447 ] 

Adam B commented on MESOS-4641:
-------------------------------

[~jieyu], [~qianzhang], [~avinash@mesosphere.io], Looks like this Epic is complete except for the bug MESOS-5533 .
Can we close out this Epic and consider it "Done" for Mesos 1.2?

> Support Container Network Interface (CNI).
> ------------------------------------------
>
>                 Key: MESOS-4641
>                 URL: https://issues.apache.org/jira/browse/MESOS-4641
>             Project: Mesos
>          Issue Type: Epic
>            Reporter: Jie Yu
>            Assignee: Qian Zhang
>              Labels: mesosphere
>
> CoreOS developed the Container Network Interface (CNI), a proposed standard for configuring network interfaces for Linux containers. Many CNI plugins (e.g., calico) have already been developed.
> https://coreos.com/blog/rkt-cni-networking.html
> https://github.com/appc/cni/blob/master/SPEC.md
> Kubernetes supports CNI as well.
> http://blog.kubernetes.io/2016/01/why-Kubernetes-doesnt-use-libnetwork.html
> In the context of Unified Containerizer, it would be nice if we can have a 'network/cni' isolator which will speak the CNI protocol and prepare the network for the container.



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