[
https://issues.apache.org/jira/browse/MESOS-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542554#comment-14542554
]
Timothy St. Clair commented on MESOS-2044:
------------------------------------------
"should Mesos be involved in the IP assignment at all?" - imho having
extensible mechanics pre+post job hooks for custom provisioning/setup+teardown
makes a lot of sense.
> 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)
