Re: [Xen-devel] [PATCH] [Xen-API] [3/3] Extension of the Xen-API for managing the ACM policy (and others)

[Tom Wilkie <tom.wilkie@xxxxxxxxx>]

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.
Cheers

Tom

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
> name>:<label>.
>
> 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>
>
>
> <xend-xspolicy-xapi-xend.diff>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel