[
https://issues.apache.org/jira/browse/MESOS-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540277#comment-14540277
]
Niklas Quarfot Nielsen commented on MESOS-2044:
-----------------------------------------------
I think we should be flexible enough to support flannel (and Calico,
OpenVSwitch, etc). I think we are mostly interested in the mechanics of
treating IP pools as resources and let framework schedule on those, i.e.
providing the plumbing to interface the container ip assignment, isolation
(security and performance).
Does this make 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)
