[
https://issues.apache.org/jira/browse/MESOS-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540315#comment-14540315
]
Niklas Quarfot Nielsen commented on MESOS-2044:
-----------------------------------------------
That boils down to; "should Mesos be involved in the IP assignment at all?"
Let's go through this in the architecture doc.
My first intuition is that frameworks need to communicate, somehow, with the IP
pool coordinator/manager that it needs private/public IPs from a certain
network/group.
Our initial thought was to _not_ have a separate controller which the
frameworks need to support/worry about how to interface with.
> 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)
