WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-cim

RE: [Xen-cim] Port to new Xen API committed

To: "Jim Fehlig" <jfehlig@xxxxxxxxxx>, <xen-cim@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-cim] Port to new Xen API committed
From: "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>
Date: Tue, 14 Nov 2006 09:43:10 -0500
Delivery-date: Tue, 14 Nov 2006 06:44:18 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4558ACF1.EE3A.00BE.0@xxxxxxxxxx>
List-help: <mailto:xen-cim-request@lists.xensource.com?subject=help>
List-id: xen-cim mailing list <xen-cim.lists.xensource.com>
List-post: <mailto:xen-cim@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-cim>, <mailto:xen-cim-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccHhTBitqmjitisQHqSKqd86f8mFwAdfWrg
Thread-topic: [Xen-cim] Port to new Xen API committed
Jim,
Thanks. I just pulled the repo and I will start playing with it.
Raj 

> -----Original Message-----
> From: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-cim-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Jim Fehlig
> Sent: Monday, November 13, 2006 7:38 PM
> To: xen-cim@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-cim] Port to new Xen API committed
> 
> Resending as it appears we may be having some internal 
> problems with certain mail lists again :-/.
> 
> All,
> 
> Today I committed the initial port to the new Xen API.  All 
> providers build cleanly against xen-unstable c/s 12391.  
> There is certainly a lot of work to do to regain the 
> functionality we had when using libvirt and the shim.  I have 
> not yet tested lifecycle operations (e.g. DefineVirtualSystem 
> and RequestStateChange) so don't expect these to work.  I 
> simply wanted to make this work available to the wider group 
> so that everyone can contribute to this effort.
> 
> Until we determine how to handle transport and authentication 
> to xend I would recommend disabling authentication in xend 
> using this trivial patch:
> 
> --- a/tools/python/xen/xend/XendAuthSessions.py Mon Nov 13 
> 14:25:48 2006 +0000
> +++ b/tools/python/xen/xend/XendAuthSessions.py Mon Nov 06 
> 17:07:00 2006 
> +++ -0700
> @@ -70,6 +70,9 @@ class XendAuthSessions:
> 
>         @rtype: boolean
>         """
> +        return True
> +
>         pam_auth = None
>         try:
>             pam_auth = PAM.pam()
> 
> With this patch I can enumerate instances of 
> Xen_ComputerSystem and any other classes that use domains for 
> their resource type.
> 
> Enjoy,
> Jim
> 
> 
> 
> _______________________________________________
> Xen-cim mailing list
> Xen-cim@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-cim
> 

_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim

<Prev in Thread] Current Thread [Next in Thread>