From: "Daniel P. Berrange" <berrange@redhat.com>
To: debian-devel@lists.debian.org, linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org
Subject: Re: cgroup mount point
Date: Tue, 3 Feb 2009 13:26:08 +0000 [thread overview]
Message-ID: <20090203132608.GA15613@redhat.com> (raw)
In-Reply-To: <20090203123028.GA3788@vespa.holoscopio.com>
On Tue, Feb 03, 2009 at 10:30:28AM -0200, Thadeu Lima de Souza Cascardo wrote:
> Sorry. I didn't mean to imply that libvirt or Fedora did anything in
> respect to the mountpoint themselves. But that they are supporting or
> planning to support cgroups. And I think that one time we will need to
> sort the problem of the mountpoint, either let the applications mount it
> (in this case, libvirt) or the system do it (Fedora install, Debian
> initscripts, et al).
>
> I have some experience with lxc tools from http://lxc.sf.net/ and these
> tools also look up the mountpoint at /proc/mounts. So it is up to the
> system or the user to mount it.
That's good. We settled on letting mount points be OS / admin defined
in libvirt, because we felt libvirt shouldn't try to impose a mount
policy on a resource that will have many users & we are able to work
with whatever mount hierarchy the admin / OS decided to setup.
> > Putting new mount points in / is not really acceptable, so that rules
> > out the first two. /opt is just totally wrong, since that is intended
> > for add on software packages. /dev/ feels a little odd, since it is
> > not really device nodes, but perhaps that doesn't matter. So my pref
> > would be something in /dev/cgroups or /sys/cgroups
>
> My suggestions were /proc/cgroup, /sys/cgroup, /cgroup or /dev/cgroup. I
> sent the problems with the former two, and the rationale for the latter
> two in a previous message.
>
> I agree that /opt/ is not the place for it (and that's the one I called
> 'funny'). I've head some people telling that /dev/ is for devices, but I
> can't see a problem (/dev/log is a socket and it is there, the FHS
> refers to special files).
>
> /proc/ and /sys/ are two good options if the kernel does not put anything
> else there. /proc/cgroups already exist, for example.
>
> Could you please give your rationale why / is not really acceptable?
Just a general preference is to not continually add more ad-hoc top
level directories to /, when there are other places in the filesystem
hierarchy that are available, such as /sys or /proc.
> > I also think 'cgroups' is a better name than 'containers', since
> > 'containers' is refering to just one specific use case.
>
> Agreed on this one, although I still prefer the singular (it is also the
> name of the filesystem type).
Either singular / plural sounds fine to me
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2009-02-03 13:27 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090202200013.GU3643@vespa.holoscopio.com>
[not found] ` <1233606371.15779.32.camel@radis.liafa.jussieu.fr>
[not found] ` <20090202205246.GA28593@glandium.org>
[not found] ` <20090202205246.GA28593-YmoObPS1fuhg9hUCZPvPmw@public.gmane.org>
2009-02-02 21:41 ` cgroup mount point Thadeu Lima de Souza Cascardo
2009-02-02 21:41 ` Thadeu Lima de Souza Cascardo
2009-02-02 22:54 ` Chris Friesen
[not found] ` <498779C2.2060908-ZIRUuHA3oDzQT0dZR+AlfA@public.gmane.org>
2009-02-02 23:43 ` Thadeu Lima de Souza Cascardo
2009-02-03 3:15 ` KAMEZAWA Hiroyuki
2009-02-02 23:43 ` Thadeu Lima de Souza Cascardo
2009-02-03 3:15 ` KAMEZAWA Hiroyuki
2009-02-03 5:06 ` Serge E. Hallyn
2009-02-06 6:17 ` Balbir Singh
[not found] ` <20090203121524.cdff11ae.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2009-02-03 5:06 ` Serge E. Hallyn
2009-02-06 6:17 ` Balbir Singh
[not found] ` <20090202214153.GV3643-StA3NKSgq9XYLCA8tIpKU1aTQe2KTcn/@public.gmane.org>
2009-02-02 22:54 ` Chris Friesen
2009-02-03 10:24 ` Daniel P. Berrange
2009-02-03 10:24 ` Daniel P. Berrange
2009-02-03 12:30 ` Thadeu Lima de Souza Cascardo
2009-02-03 13:26 ` Daniel P. Berrange [this message]
[not found] ` <20090203123028.GA3788-StA3NKSgq9XYLCA8tIpKU1aTQe2KTcn/@public.gmane.org>
2009-02-03 13:26 ` Daniel P. Berrange
[not found] ` <87ljsnzo4v.fsf@benfinney.id.au>
[not found] ` <87ljsnzo4v.fsf-TqlCGjI+HWGnbCmf7pGUHw@public.gmane.org>
2009-02-03 12:57 ` Thadeu Lima de Souza Cascardo
2009-02-03 12:57 ` Thadeu Lima de Souza Cascardo
2009-02-04 3:59 ` Ben Finney
2009-02-03 14:38 ` Gustavo Noronha
2009-02-03 16:55 ` Paul Menage
2009-02-03 18:49 ` Mike Hommey
2009-02-03 18:51 ` sean finney
2009-02-03 19:14 ` Paul Menage
2009-02-03 23:38 ` Harald Braumann
2009-02-03 23:40 ` Paul Menage
2009-02-04 0:18 ` Harald Braumann
2009-02-04 9:16 ` Josselin Mouette
2009-02-05 21:19 ` José Luis Tallón
2009-02-06 22:00 ` Harald Braumann
[not found] ` <20090203102416.GA8886-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-02-03 12:30 ` Thadeu Lima de Souza Cascardo
2009-02-03 15:03 ` Gabor Gombas
2009-02-03 15:03 ` Gabor Gombas
[not found] ` <20090203150315.GI482-WfxVeM0IB4OcrO3FVCo2em/Xy1I+TMuj@public.gmane.org>
2009-02-03 16:19 ` Bill Nottingham
2009-02-03 16:19 ` Bill Nottingham
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=20090203132608.GA15613@redhat.com \
--to=berrange@redhat.com \
--cc=containers@lists.linux-foundation.org \
--cc=debian-devel@lists.debian.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.