This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] [Xen-API] [3/3] Extension of the Xen-API for man

To: Stefan Berger <stefanb@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] [Xen-API] [3/3] Extension of the Xen-API for managing the ACM policy (and others)
From: Tom Wilkie <tom.wilkie@xxxxxxxxx>
Date: Mon, 21 May 2007 17:39:49 +0100
Cc: Ewan Mellor <ewan@xxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Tom Wilkie <tom.wilkie@xxxxxxxxx>, sailer@xxxxxxxxxx
Delivery-date: Mon, 21 May 2007 09:38:23 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; b=YfLfQhcvtDqrZKggCdJYbwjo/1tLbGrjUSmnNEt3F8j2sbJS2ll83omm68uX1ugin7Hb1llF5dJgrQmBSINrzjUF/S7Xj5eyoMxUQ5WWdg7mvk8/29UHJ/rQr4KYWJ8JtigyN6rWAtQfMvnOl3pBK/tdbQuya0sDTaQ2g86v1IU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; b=iPclX0UfIRNHPbocUqxrRQJOJxdhi6Q0Y/Hc2/3BuwNhR6wZyFItDRNU5/W+TdUtNntusuDN4o/YbabJLEILfT9BwpIuS/NDYKYjP+gybDonRQqN2l74mRXesIuVnMBmNMjw8rjxhTSZpjSqCNMllUl98uzk8DafOb8ie9VgpEs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1179760788.4473.10.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1179760788.4473.10.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Stefan

Just had a quick look at this patch. Some of the work I've been doing recently is to make the XenAPI implementation inside xend a bit 'nicer'. I want to head towards a model where all the XenAPI classes subclass XendBase.py and use auto plugging in XendAPI.py. This should provide a more natural implementation of these classes as (first class) python classes, handle all the ref / uuid mapping for you (via XendAPIStore.py) and break the class implementation out from XendAPI.py. Hopefully (in the future) this will also help with persistence.

If you want some example look at the recent work on XendPIF.py, XendNetwork.py and the metrics classes, which have all been implemented this way.



On 21 May 2007, at 16:19, Stefan Berger wrote:

This patch implements extensions for managing security policies in xend. The XSPolicy and ACMPolicy classes provide the interface for the Xen-API
and implement the functionality described in the documentation.

Some of the xend-internal code implements changing the previously used
format into the format used by the Xen-API. This is mostly related to
the labels and their format of <policy identifier>:<policy

The acmpolicy class implements a compiler for translating an XML policy
into their binary format and provides functionality for comparing a
current policy against a new one when changing a policy.

The xspolicyadmin class administers the policy of the system.

Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxx>

Xen-devel mailing list

Xen-devel mailing list