mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jie Yu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-2528) Symlink the namespace handle with ContainerID for the port mapping isolator.
Date Mon, 23 Mar 2015 19:18:53 GMT

     [ https://issues.apache.org/jira/browse/MESOS-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jie Yu updated MESOS-2528:
--------------------------
          Sprint: Twitter Mesos Q1 Sprint 5
    Story Points: 3

> Symlink the namespace handle with ContainerID for the port mapping isolator.
> ----------------------------------------------------------------------------
>
>                 Key: MESOS-2528
>                 URL: https://issues.apache.org/jira/browse/MESOS-2528
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Jie Yu
>            Assignee: Jie Yu
>
> This serves two purposes:
> 1) Allows us to enter the network namespace using container ID (instead of pid): "ip
netns exec <ContainerID> [commands] [args]".
> 2) Allows us to get container ID for orphan containers during recovery. This will be
helpful for solving MESOS-2367.
> The challenge here is to solve it in a backward compatible way. I propose to create symlinks
under /var/run/netns. For example:
> /var/run/netns/containeridxxxx --> /var/run/netns/12345
> (12345 is the pid)
> The old code will only remove the bind mounts and leave the symlinks, which I think is
fine since containerid is globally unique (uuid).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message