mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-8534) Allow nested containers in TaskGroups to have separate network namespaces
Date Thu, 22 Feb 2018 07:20:00 GMT

    [ https://issues.apache.org/jira/browse/MESOS-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372510#comment-16372510
] 

ASF GitHub Bot commented on MESOS-8534:
---------------------------------------

Github user qianzhangxa commented on the issue:

    https://github.com/apache/mesos/pull/263
  
    I'd like to echo @jdef's comment, we need a clear use case for ip per nested container.
Our current status is, if framework launches multiple task groups (pods) via a single default
executor, all the nested containers of all these task groups will share the executor's network
namespace. This is actually different from Kubernetes pod where each pod will have its own
network namespace and all the container in a pod will share the same network namespace so
that they can communicated with 127.0.0.1/localhost. IMHO, we should consider to do something
similar with Kubernetes, i.e., each task group will have its own network namespace rather
than each nested container has its own network namespace unless we have a use case for it.


> Allow nested containers in TaskGroups to have separate network namespaces
> -------------------------------------------------------------------------
>
>                 Key: MESOS-8534
>                 URL: https://issues.apache.org/jira/browse/MESOS-8534
>             Project: Mesos
>          Issue Type: Task
>          Components: containerization
>            Reporter: Sagar Sadashiv Patwardhan
>            Priority: Minor
>              Labels: cni
>
> As per the discussion with [~jieyu] and [~avinash.mesos] , I am going to allow nested
containers in TaskGroups to have separate namespaces. I am also going to retain the existing
functionality, where nested containers can share namespaces with parent/root container.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message