Linux Container Development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
Cc: Linux Containers
	<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
	Daniel Lezcano <dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>,
	Alexey Dobriyan
	<adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: kernel summit topic - 'containers end-game'
Date: Tue, 7 Jul 2009 11:14:40 -0500	[thread overview]
Message-ID: <20090707161440.GA16152@us.ibm.com> (raw)
In-Reply-To: <4A536B91.5010205-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>

Quoting Oren Laadan (orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org):
> 
> 
> Serge E. Hallyn wrote:
> > Quoting Oren Laadan (orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org):
> >>
> >> Serge E. Hallyn wrote:
> >>> Quoting Oren Laadan (orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org):
> >>>> Serge E. Hallyn wrote:
> >>>>> A topic on ksummit agenda is 'containers end-game and how do we
> >>>>> get there'.
> >>>>>
> >>>>> So for starters, looking just at application (and system) containers, what do
> >>>>> the libvirt and liblxc projects want to see in kernel support that is currently
> >>>>> missing?  Are there specific things that should be done soon to make containers
> >>>>> more useful and usable?
> >>>>>
> >>>>> More generally, the topic raises the question... what 'end-games' are there?
> >>>>> A few I can think of off-hand include:
> >>>>>
> >>>>> 	1. resource control
> >>>>> 	2. lightweight virtual servers
> >>>>> 	3. (or 2.5) unprivileged containers/jail-on-steroids
> >>>>> 		(lightweight virtual servers in which you might, just
> >>>>> 		maybe, almost, be able to give away a root account, at
> >>>>> 		least as much as you could do so with a kvm/qemu/xen
> >>>>> 		partition)
> >>>>> 	4. checkpoint, restart, and migration
> >>>>>
> >>>>> For each end-game, what kernel pieces do we think are missing?  For instance,
> >>>>> people seem agreed that resource control needs io control :)  Containers imo
> >>>>> need a user namespace.  I think there are quite a few network namespace
> >>>>> exploiters who require sysfs directory tagging (or some equivalent) to
> >>>>> allow us to migrate physical devices into network namespaces.  And
> >>>>> checkpoint/restart needs... checkpoint/restart.
> >>>> Heh ... it does need ... checkpoint/restart; and a few issues
> >>>> which we should think about sometime --
> >>> Yup, these are all things we need to discuss.  For some of them we might
> >>> just need to flail about and code a few approaches until we figure out an
> >>> answer, but then I think that everyone has thought about a few of these
> >>> in some detail, so there probably is much we could gain from talking.
> >>>
> >>> ...  Does this mean we should try to have a mini-summit in the next 6
> >>> months or so?  I'd recommend having one right before kernel summit so
> >>> we can get our act together, but getting everyone to tokyo to chat seems
> >>> uneconomical :)  It'd be good to chat about at least the first two items
> >>> before the summit, though.
> >>>
> >> How about linux plumbers ?
> > 
> > Well it seems like an appropriate place for it.  Alas there is almost no chance
> > of my being there, but let's hear a roll call - how many people (interested in
> > checkpoint/restart) will be or can be at plumber's?
> > 
> > I'm pretty sure Suka and Dave will be there.
> 
> Seems like I can make it.

Alexey, are you planning on being at the plumber's conf this year?

-serge

      parent reply	other threads:[~2009-07-07 16:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 14:56 kernel summit topic - 'containers end-game' Serge E. Hallyn
2009-06-29 10:35 ` [libvirt] " Balbir Singh
2009-06-30 20:06   ` Serge E. Hallyn
2009-07-01  4:29     ` Balbir Singh
     [not found]     ` <20090630200613.GA22283-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-07-02 16:58       ` Daniel Lezcano
2009-07-02 16:43 ` [libvirt] " Daniel Lezcano
     [not found]   ` <4A4CE3A6.200-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2009-07-02 18:27     ` Oren Laadan
2009-07-06 14:51   ` [libvirt] " Serge E. Hallyn
2009-07-08  7:55     ` Daniel Lezcano
2009-07-08 13:45       ` Serge E. Hallyn
     [not found] ` <20090623145611.GB19332-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-07-02 18:38   ` Oren Laadan
2009-07-06 14:34     ` [libvirt] " Serge E. Hallyn
     [not found]       ` <20090706143401.GA16868-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-07-06 17:30         ` Oren Laadan
2009-07-06 18:48           ` [libvirt] " Serge E. Hallyn
     [not found]             ` <20090706184848.GA23819-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-07-07 15:36               ` Oren Laadan
     [not found]                 ` <4A536B91.5010205-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2009-07-07 16:14                   ` Serge E. Hallyn [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090707161440.GA16152@us.ibm.com \
    --to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
    --cc=orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox