[GitHub] mesos issue #263: Allow nested containers in pods to have separate namespace...
Github user sagar8192 commented on the issue: https://github.com/apache/mesos/pull/263 Closed in favor of https://reviews.apache.org/r/65987/ ---
[GitHub] mesos issue #263: Allow nested containers in pods to have separate namespace...
Github user sagar8192 commented on the issue: https://github.com/apache/mesos/pull/263 Posted a new review here: https://reviews.apache.org/r/65987/ ---
[GitHub] mesos issue #263: Allow nested containers in pods to have separate namespace...
Github user sagar8192 commented on the issue: https://github.com/apache/mesos/pull/263 @jdef, @qianzhangxa: I have added some more information about the use case to the [ticket](https://issues.apache.org/jira/browse/MESOS-8534). Please check it out. We are planning to discuss this in today's containerization sync. ---
[GitHub] mesos issue #263: Allow nested containers in pods to have separate namespace...
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. ---
[GitHub] mesos issue #263: Allow nested containers in pods to have separate namespace...
Github user Gilbert88 commented on the issue: https://github.com/apache/mesos/pull/263 A quick note that we could have a followup patch to add documents here: http://mesos.apache.org/documentation/latest/containerizer-internals/#linux-namespaces ---
[GitHub] mesos issue #263: Allow nested containers in pods to have separate namespace...
Github user jdef commented on the issue: https://github.com/apache/mesos/pull/263 What's the high level use case that's driving this change request? One of the major goals of task-groups (pods) is to allow containers to share networking and storage. What point is there in launching a nested container that DOES NOT share these things with the other containers in the pod? ---
