[
https://issues.apache.org/jira/browse/MESOS-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730046#comment-14730046
]
Charles Allen commented on MESOS-2044:
--------------------------------------
I'm a bit confused on why this needs to be so integrated into Mesos all through
the stack instead of just being used as another type of Resource that any
particular slave can expose, and exposing it as a pluggable resource on the
slave. Then frameworks which know or care about such a resource can request it,
and ones that don't know or care can simply ignore it.
>From the proposals I've seen this is trying to be a global resource that
>either must be supported by all nodes or not supported at all. Is that really
>required?
What use cases fail if IP address per container are simply exposed as a slave
resource?
> 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
> Assignee: Kapil Arya
> Labels: mesosphere
>
> 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)
