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 20:44:02 UTC
[jira] [Commented] (MESOS-2721) Architecture document for
per-container IP assignment, enforcement and isolation
[ https://issues.apache.org/jira/browse/MESOS-2721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540453#comment-14540453 ]
Niklas Quarfot Nielsen commented on MESOS-2721:
-----------------------------------------------
I started a doc here: https://docs.google.com/a/mesosphere.io/document/d/17mXtAmdAXcNBwp_JfrxmZcQrs7EO6ancSbejrqjLQ0g/edit?usp=sharing
Let's add our thoughts in the proposed solutions and work in and evaluate all the details
> Architecture document for per-container IP assignment, enforcement and isolation
> --------------------------------------------------------------------------------
>
> Key: MESOS-2721
> URL: https://issues.apache.org/jira/browse/MESOS-2721
> Project: Mesos
> Issue Type: Task
> Reporter: Niklas Quarfot Nielsen
>
> There are many ways in which we can go around wiring up per-container IPs in Mesos.
> As there are multiple underlying mechanisms and systems for keeping track of IP pools, we probably need to aim for a very flexible architecture, similar to the oversubscription project.
> There are a couple of folks, companies and vendors interested in getting this capability into Mesos asap to provide a stronger networking story (https://www.mail-archive.com/dev@mesos.apache.org/msg32353.html). So let's start discussing and architecting this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)