[
https://issues.apache.org/jira/browse/MESOS-4641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15337751#comment-15337751
]
Stephan Erb commented on MESOS-4641:
------------------------------------
Mesos has a bunch of network level statistics ([as documented
here|https://github.com/apache/mesos/blob/2127376b8e092684312ec9843173b532df931d20/docs/network-monitoring.md#monitoring-container-network-statistics]).
Unfortunately as of today only the {{network/port_mapping}} isolator can
expose those. Are there plans to expose those also for the CNI?
> 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
>
> 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)
