Linux Container Development
 help / color / mirror / Atom feed
From: Balbir Singh <balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
Cc: Kir Kolyshkin <kir-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>,
	Linux Containers
	<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: [Devel] OLS paper topics
Date: Wed, 30 Jan 2008 15:29:22 +0530	[thread overview]
Message-ID: <47A04A7A.9030701@linux.vnet.ibm.com> (raw)
In-Reply-To: <47A04916.50904-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>

Cedric Le Goater wrote:
> 
>>> == Topic ==
>>>
>>> Namespaces, containers, cgroups, and container checkpoint/restart.
>>>
>>> == Description ==
>>>
>>> Development for namespaces and cgroups is well underway in the
>>> mainline kernel. To keep momentum going and keep the loosely
>>> knit teams of developers well-coordinated, a physical meeting in
>>> which to discuss future development plans is needed.
>>> Additionally, we are at a point where crucial decisions about
>>> the nature of a "container object" and about the checkpoint/restart
>>> design need to be made.
>>>
>>> A final set of topics will be decided upon through mailing lists
>>> ahead of time, but potential topics include:
>>> * Handling filesystem/namespace synchronization
>>> * Handling of /proc and /sysfs within containers
>>> * Additional needed namespaces (i.e. device namespace)
>>> * Nature of a 'container' — kernel object or userspace fiction
>>> * Additional cgroups and their design
>>> * How to initiate and synchronize checkpoint/restart
>>> * How to enter a 'container' ?
>>>
>>
>> Resource Management for containers?
> 
> Yes we need that. There are a few possible conflicts in requirements
> that need to be discussed. For example, a resource management req
> would be to be able to move a process from one group to another and C/R
> wouldn't.

Cedric,

Why is that a conflict w.r.t resource management, isn't that more of a cgroup
feature - task migration. We need task migration for resource management, but
task migration is a system administrator/management function. I don't see the
conflict, but may be I am missing something very obvious.

>>> == Moderators ==
>>> {{Out|These are just suggestions, please edit here or let us know if you
>>> do or do not want to moderate.}}
>>>
>>> * Namespaces/containers: Serge Hallyn, Cedric Le Goater
>>> * cgroups: Paul Menage
>>> * Checkpoint/restart: Dave Hansen, Cedric Le Goater
> 
> IMO, 2 is a minimum to get the work done (it will require a minimum of
> organization) but the moderators don't necessarily have to be from the
> same team.
> 
> Or, having some one in charge of the logistics would be better ? In that
> case, you can remove me from the moderators.
> 
>> Resource Management? - I don't mind moderating that if it happens to be
>> included in the summit or can we merge it with cgroups?
> 
> Good thing.
> 
> Cheers,
> 
> C.


-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL

  parent reply	other threads:[~2008-01-30  9:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-23 19:57 OLS paper topics Serge E. Hallyn
     [not found] ` <20080123195736.GA7823-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2008-01-24 22:05   ` [Devel] " Kir Kolyshkin
     [not found]     ` <47990BAB.4050106-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-01-24 22:50       ` Serge E. Hallyn
     [not found]         ` <20080124225002.GC13819-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2008-01-25  0:13           ` Kir Kolyshkin
2008-01-30  8:50           ` Kir Kolyshkin
     [not found]             ` <47A03A73.6070408-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-01-30  8:58               ` Balbir Singh
     [not found]                 ` <47A03C25.8030205-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-01-30  9:53                   ` Cedric Le Goater
     [not found]                     ` <47A04916.50904-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-01-30  9:59                       ` Balbir Singh [this message]
     [not found]                         ` <47A04A7A.9030701-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-01-30 12:57                           ` Cedric Le Goater
     [not found]                             ` <47A07430.3000600-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-01-30 15:48                               ` Serge E. Hallyn
2008-01-30 15:52                           ` Serge E. Hallyn
     [not found]                             ` <20080130155220.GD1206-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2008-01-30 16:54                               ` Balbir Singh
2008-01-30 10:43                   ` Dhaval Giani
     [not found]                     ` <20080130104336.GD3862-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-01-30 15:40                       ` Serge E. Hallyn
     [not found]                         ` <20080130154043.GB1206-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2008-01-31  7:49                           ` Dhaval Giani

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=47A04A7A.9030701@linux.vnet.ibm.com \
    --to=balbir-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=kir-GEFAQzZX7r8dnm+yROfE0A@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