[
https://issues.apache.org/jira/browse/MESOS-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108801#comment-15108801
]
Alex Pollitt commented on MESOS-3828:
-------------------------------------
Docker libnetwork supports plug-in network drivers that allow SDN vendors to
connect Docker to their underlying SDN solutions. This is a good thing.
However, libnetwork implements a larger part of the network control plane than
many SDN vendors would like, and tightly restricts the amount of information it
passes to plug-in network drivers. This makes it quite hard for SDN vendors to
offer differentiated or value add features beyond what you get with Docker's
batteries included driver. It also means it is very hard to map concepts such
as Mesos's netgroups through to such a driver. It also makes it very hard to
combine Docker and non-Docker workloads within the same SDN.
The Kubernetes community tried really hard to find a way to sensibly use Docker
libnetwork, but in the end have decided (at least for now) to use CNI instead.
You might find this recent blog post on this topic interesting: "Why Kubernetes
doesn’t use libnetwork" :
http://blog.kubernetes.io/2016/01/why-Kubernetes-doesnt-use-libnetwork.html
By the way, I work on Project Calico. We have drivers for Mesos, Kubernetes,
Docker libnetwork, Rkt, and OpenStack. So if Mesos did decide to start using
libnetwork we could support that very easily. But given the direction the rest
of Mesos networking is heading (see Spike's comment above) with it's own IP per
container and network isolation concepts and APIs, I think it would be very
hard to integrate libnetwork seamlessly into that in a sensible, consistent and
coherent fashion.
> Strategy for Utilizing Docker 1.9 Multihost Networking
> ------------------------------------------------------
>
> Key: MESOS-3828
> URL: https://issues.apache.org/jira/browse/MESOS-3828
> Project: Mesos
> Issue Type: Story
> Components: isolation
> Affects Versions: 0.26.0
> Reporter: John Omernik
> Assignee: Timothy Chen
> Labels: Docker, isolation, mesosphere, network, plugins
>
> This is a user story to discuss the strategy for Mesos to in using the new
> Docker 1.9 feature: Multihost Networking.
> http://blog.docker.com/2015/11/docker-multi-host-networking-ga/
> Basically we should determine if this is something we want to work with from
> a standpoint of container isolation and going forward how can we best
> integrate.
> The space for networking in Mesos is growing fast with IP per Container and
> other networking modules being worked on. Projects like Project Calico offer
> services from outside the Mesos community that plug nicely or will plug
> nicely into Mesos.
> So how about Multihost networking? An option to work with? With Docker being
> a first class citizen of Mesos, this is something we should be considering.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
