From: Syunsuke HAYASHI <syunsuke@jp.fujitsu.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>, xen-devel@lists.xensource.com
Subject: Re: Finer access control framework over users, domains and operations.
Date: Fri, 30 May 2008 18:59:51 +0900 [thread overview]
Message-ID: <483FD017.3010008@jp.fujitsu.com> (raw)
In-Reply-To: <18481.21663.161348.181541@mariner.uk.xensource.com>
Hi, Ian
We understand that the implementation of the ACM on the web layer is easy.
But we think that basic control tools of Xen (xm and libvirt) also need
the ACM
It is necessary to realize the ACM which considers users, domains and
operations.
We only know ways that control by the unit of users or processes.
Please let us know if there are other tools or ways that realize the ACM.
Thanks,
Ian Jackson wrote:
> Syunsuke HAYASHI writes ("[Xen-devel] Finer access control framework
over users, domains and operations."):
>> The current implementation exclusively allows root to control guest
>> domains. Guest administrators have to switch to root so they can
>> bring their own guest domains up and down.
>
> In most deployments this problem is addressed by the use of (for
> example) a web-based management interface layered on top of the
> underlying xm machinery.
>
> Do your users really need an structurally very similar interface to
> that provided by xm or libvirt ? If so then yes maybe you will need
> to write a policy-enforcing proxy but this would be a very large
> amount of work and I wouldn't recommend it as an approach unless
> unavoidable.
next prev parent reply other threads:[~2008-05-30 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 6:17 Finer access control framework over users, domains and operations Syunsuke HAYASHI
2008-05-19 10:21 ` Ian Jackson
2008-05-30 9:59 ` Syunsuke HAYASHI [this message]
2008-05-30 13:41 ` Ian Jackson
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=483FD017.3010008@jp.fujitsu.com \
--to=syunsuke@jp.fujitsu.com \
--cc=Ian.Jackson@eu.citrix.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.