Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Tue, 12 May 2015 17:33:07 +0000 (UTC)
From: "Timothy St. Clair (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12752882.1415140788000.89673.1431451987960@Atlassian.JIRA>
In-Reply-To: <JIRA.12752882.1415140788000@Atlassian.JIRA>
References: <JIRA.12752882.1415140788000@Atlassian.JIRA>
 <JIRA.12752882.1415140788809@arcas>
Subject: [jira] [Commented] (MESOS-2044) Use one IP address per container
 for network isolation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Timothy St. Clair commented on MESOS-2044:
------------------------------------------

flannel intends to provide this abstraction layer for some of impls (VxLan, and OVS).. There may be more on the roadmap.  

Re: storage 
- Yes it's all stored under /coreos.com/network/subnets

> Use one IP address per container for network isolation
> ------------------------------------------------------
>
>                 Key: MESOS-2044
>                 URL: https://issues.apache.org/jira/browse/MESOS-2044
>             Project: Mesos
>          Issue Type: Epic
>            Reporter: Cong Wang
>
> If there are enough IP addresses, either IPv4 or IPv6, we should use one IP address per container, instead of the ugly port range based solution. One problem with this is the IP address management, usually it is managed by a DHCP server, maybe we need to manage them in mesos master/slave.
> Also, maybe use macvlan instead of veth for better isolation.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)