[Devel] Re: containers and cgroups mini-summit @ Linux Plumbers

[Serge Hallyn]

Quoting Glauber Costa (glommer at parallels.com):
> On 07/25/2012 03:51 PM, Serge Hallyn wrote:
> > Quoting Glauber Costa (glommer at parallels.com):
> >> On 07/12/2012 01:41 AM, Kir Kolyshkin wrote:
> >>> Gentlemen,
> >>>
> >>> We are organizing containers mini-summit during next Linux Plumbers (San
> >>> Diego, August 29-31).
> >>> The idea is to gather and discuss everything relevant to namespaces,
> >>> cgroups, resource management,
> >>> checkpoint-restore and so on.
> >>>
> >>> We are trying to come up with a list of topics to discuss, so please
> >>> reply with topic suggestions, and
> >>> let me know if you are going to come.
> >>>
> >>> I probably forgot a few more people (such as, I am not sure who else
> >>> from Google is working
> >>> on cgroups stuff), so fill free to forward this to anyone you believe
> >>> should go,
> >>> or just let me know whom I missed.
> >>>
> >>> Regards,
> >>>   Kir.
> >>
> >> I just came up with the following preliminary list of sessions:
> >>
> >> http://wiki.linuxplumbersconf.org/2012:containers
> > 
> > Thanks.  We could also add devices namespace to the list.  I'm fine NOT
> > having it in the list, as I think we're agreed that it should come after
> > user namespaces are complete.
> > 
> How about a "future of namespaces" generic placeholder?

Sure.  And I suppose syslog and time ns could also fall under that.  Issues
to discuss include:

1. what other namespaces do people expect to need?
2. justifications for the proposed namespaces, and other potential ways
   to address each.  I.e., for devices ns, two justifications are (1)
   per-container loop devices (could be pre-allocated with containers
   aware of which /dev/loopN index they may use), and (2) filtering
   uevents only to appropriate containers to limit the uevent storm when
   containers do udevadm trigger --action=add (not sure, but we can
   brainstorm other solutions).
3. semantics for the namespace - I.e syslog namespace, how do we decide
   whether/when to unshare it, is it owned by a user namespace or a pid
   namespace, etc.