mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guangya Liu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-3828) Strategy for Utilizing Docker 1.9 Multihost Networking
Date Tue, 17 Nov 2015 01:58:11 GMT

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

Guangya Liu commented on MESOS-3828:
------------------------------------

[~mandoskippy] So your main concern is that the network capabilities is not limited to docker
container but maybe other things running on top of Mesos, right? Is it possible to let different
container technology using different network manager? For docker container, it can just use
some overlay network module.

> 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)

Mime
View raw message