From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cedric Le Goater Subject: Re: [Devel] OLS paper topics Date: Wed, 30 Jan 2008 10:53:26 +0100 Message-ID: <47A04916.50904@fr.ibm.com> References: <20080123195736.GA7823@sergelap.austin.ibm.com> <47990BAB.4050106@openvz.org> <20080124225002.GC13819@sergelap.austin.ibm.com> <47A03A73.6070408@openvz.org> <47A03C25.8030205@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <47A03C25.8030205-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org Cc: Kir Kolyshkin , Linux Containers List-Id: containers.vger.kernel.org >> =3D=3D Topic =3D=3D >> >> Namespaces, containers, cgroups, and container checkpoint/restart. >> >> =3D=3D Description =3D=3D >> >> 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' =E2=80=94 kernel object or userspace fiction >> * Additional cgroups and their design >> * How to initiate and synchronize checkpoint/restart >> * How to enter a 'container' ? >> >=20 > Resource Management for containers? Yes we need that. There are a few possible conflicts in requirements=20 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=20 C/R wouldn't.=20 >> =3D=3D Moderators =3D=3D >> {{Out|These are just suggestions, please edit here or let us know if y= ou >> 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=20 organization) but the moderators don't necessarily have to be from the=20 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.