All of lore.kernel.org
 help / color / mirror / Atom feed
From: Syunsuke HAYASHI <syunsuke@jp.fujitsu.com>
To: xen-devel@lists.xensource.com, Stefan Berger <stefanb@us.ibm.com>
Subject: Re: [PATCH] [Xend/Xm/ACM] [RESEND] [1/2] Implement legacy XML-RPC interface for ACM commands
Date: Wed, 05 Dec 2007 18:35:04 +0900	[thread overview]
Message-ID: <475670C8.1040403@jp.fujitsu.com> (raw)
In-Reply-To: <1196810603.11145.20.camel@941e-2.watson.ibm.com>

Hi,

I applied these patches.
-security_commands_through_xend.diff
-xend_acm_new_storage_path.diff

These patches fix the following problem.

Before applying these patches:
# xm labels type=any
__NULL_LABEL__ <--------__NULL_LABEL__??
dom_BoincClient
dom_Fun
dom_HomeBanking
dom_NetworkDomain
dom_StorageDomain
res_EthernetCard
res_GraphicsAdapter
res_HardDrive(hda)
res_LogicalDiskPartition1(hda1)
res_LogicalDiskPartition2(hda2)
res_ManagementResource
res_SecurityToken

After applying these patches:
# xm labels type=any
SystemManagement
dom_BoincClient
dom_Fun
dom_HomeBanking
dom_NetworkDomain
dom_StorageDomain
res_EthernetCard
res_GraphicsAdapter
res_HardDrive(hda)
res_LogicalDiskPartition1(hda1)
res_LogicalDiskPartition2(hda2)
res_ManagementResource
res_SecurityToken

Thanks

Syunsuke HAYASHI

Stefan Berger wrote:
> This time with a gzipp'ed patch attached.
> 
> This patch implements a (non Xen-API) legacy XML-RPC interface for the
> ACM commands and funnels the calls into code introduced by the Xen-API
> support for ACM security management. Since some of the functionality has
> changed, also the xm applications have changed. In particular the
> following old commands have been removed along with some tools the have
> become obsolete now:
> 
> - loadpolicy    (included in: setpolicy)
> - makepolicy    (included in: setpolicy)
> - cfgbootpolicy (included in: setpolicy)
> 
> and the following commands been introduced:
> 
> - setpolicy
> - getpolicy
> - resetpolicy
> 
> All tools have been adapted to work in Xen-API and legacy XML-RPC mode.
> Both modes support the same functionality.
> 
> An update to the documentation will follow as well as new test cases.
> 
> I have run this and the 2nd patch with the xm-test suite on the tip of
> the staging tree and they caused no regressions.
> 
> Signed-off-by: Stefan Berger <stefanb@us.ibm.com>
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

      reply	other threads:[~2007-12-05  9:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-04 23:23 [PATCH] [Xend/Xm/ACM] [RESEND] [1/2] Implement legacy XML-RPC interface for ACM commands Stefan Berger
2007-12-05  9:35 ` Syunsuke HAYASHI [this message]

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=475670C8.1040403@jp.fujitsu.com \
    --to=syunsuke@jp.fujitsu.com \
    --cc=stefanb@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.