You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Niklas Quarfot Nielsen (JIRA)" <ji...@apache.org> on 2015/05/12 19:04:01 UTC

[jira] [Commented] (MESOS-2044) Use one IP address per container for network isolation

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

Niklas Quarfot Nielsen commented on MESOS-2044:
-----------------------------------------------

We need this for a networking solution we are working on, and I know that other folks are interested in this capability too.

I suggest that we start an architecture proposal doc and start discussing an approach (and turn this into an epic).

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