From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: "Mike D. Day" <ncmike@us.ibm.com>
Cc: Chris <hap10@tycho.ncsc.mil>, xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: Domgrps/SchedGrps Merge RFC: domgrps-vmm
Date: Tue, 12 Feb 2008 00:05:11 +0000 [thread overview]
Message-ID: <20080212000511.GC4483@implementation> (raw)
In-Reply-To: <20080211220738.GA11545@silverwood.ncultra.org>
Mike D. Day, le Mon 11 Feb 2008 17:07:38 -0500, a écrit :
> So a domain can only belong to one group at a time. Would it ever be
> useful for a domain to belong to more than one group? This type of
> restriction seems to work against the idea of a general grouping
> concept.
Right.
> For example, all domains that belong to a scheduling group
> (assuming we eventually merge domgrp and schedgrp) would automatically
> be removed from a scheduling group if added to any other type of
> group.
Which makes sense, doesn't it?
> This argues for keeping different types of groups under different
> grouping infrastructures unless we can figure out a way for a domain
> to have multiple group memberships. It may be too complicated to do so.
Yes, usually group mecanisms are just hierarchical rather than being so
generic as to permit several membership. I guess the common pitfall is
when enumerating groups, you may see a domain several times, and such
strange effects.
Samuel
next prev parent reply other threads:[~2008-02-12 0:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 19:14 [1/3] Domgrps/SchedGrps Merge RFC: domgrps-vmm Chris
2008-02-06 12:00 ` Akio Takebe
2008-02-06 13:59 ` Chris
2008-02-11 22:07 ` Mike D. Day
2008-02-12 0:05 ` Samuel Thibault [this message]
2008-02-27 18:45 ` Chris
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=20080212000511.GC4483@implementation \
--to=samuel.thibault@eu.citrix.com \
--cc=hap10@tycho.ncsc.mil \
--cc=ncmike@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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.