[
https://issues.apache.org/jira/browse/MESOS-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008712#comment-15008712
]
John Omernik commented on MESOS-3828:
-------------------------------------
I think the key factor here is that Docker containers may need to talk to other
Docker containers, but it also may need to talk to non-Docker containers on
your cluster. Consider some data frameworks like Spark. You can Dockerize it,
heck at the end of the day you may be able to Dockerize all things, however
they may be reasons not to. If an org choose not to Dockerize say a Spark
framework, and they want to put a web front on in say flask, than having the
the ability to specify that the Spark frame runs in the Mesos containerizer on
X network, and also has a Docker container attached to it on X network, and
then expose the web app only via the IP tables rules, you've now created a
situation where the Spark framework is isolated and the Docker container sits
within that isolation only exposing the one port that is needed. When you need
to run another similar setup, say for another user or business unit, everything
can be the same, except they use network Y instead of X. No conflicts, no
"mistakes" or cross connections. (This also applies to Prod/Dev/Staging
setups).
I guess that long winded explanation is me thinking out loud about use cases.
If there was a plugin that where the Docker Multihost networking could be used
and mated together with something else like Calico and networking for cluster
managed in one place, that would be worth looking at, however, I would hate to
look at a feature of Docker and not have it work for the situation mentioned
above.
> 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)
