mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Spike Curtis (JIRA)" <>
Subject [jira] [Commented] (MESOS-3828) Strategy for Utilizing Docker 1.9 Multihost Networking
Date Tue, 08 Dec 2015 17:42:11 GMT


Spike Curtis commented on MESOS-3828:

We're already well on the road to getting IP-per-container networking into the MesosContainerizer.
 I would strongly advocate for a unified networking layer that handles both Docker and Mesos
containers.  This work is centered at:

We can straightforwardly enhance this work to extend multihost networking to Docker containers
as well, without the need for Docker's libnetwork.  That gives us the advantage of all tasks
getting a consistent, unified, and easy to understand network function, rather than attempting
to mate Docker's opinionated network model with Mesos container networking.

> Strategy for Utilizing Docker 1.9 Multihost Networking
> ------------------------------------------------------
>                 Key: MESOS-3828
>                 URL:
>             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. 
> 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

View raw message