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-devel

Re: [Xen-devel] Re: xend http interface

To: Evan Bigall <evan.bigall@xxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: xend http interface
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Tue, 12 Dec 2006 09:43:25 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 12 Dec 2006 01:43:31 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <457E16B0.3070706@xxxxxxxxxxx>
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: <457B976C.2070801@xxxxxxxxxxx> <457E16B0.3070706@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Tue, Dec 12, 2006 at 09:40:48AM +0700, Evan Bigall wrote:

> Tried this on xen-users and got no responses, so I am trying here...
> 
> I am trying to use the xend http interface (yes, I know about 
> http://wiki.xensource.com/xenwiki/XenApi, but this is for a quick demo 
> this month).
> 
> When I open http://127.0.0.1:8000/xend/domain I get a page the just 
> says: "/ xend / domain /" thats its, no list of the domains.
> 
> If I telnet to 127.0.0.1 8000 and do "GET /xend HTTP/1.1" I get a 500 
> Internel server error.
> 
> Looking at xend-debug.log I see:
> 
> Traceback (most recent call last):
> File "//usr/lib/python/xen/web/httpserver.py", line 141, in process
>   return self.render(resource)
> File "//usr/lib/python/xen/web/httpserver.py", line 188, in render
>   self.resultErr(ex)
> File "//usr/lib/python/xen/web/httpserver.py", line 181, in render
>   val = resource.render(self)
> File "//usr/lib/python/xen/web/resource.py", line 59, in render
>   return meth(req)
> File "//usr/lib/python/xen/xend/server/SrvDomainDir.py", line 138, in 
> render_GET
>   self._list(req, 'detail' in req.args and req.args['detail'] == ['1'])
> File "//usr/lib/python/xen/xend/server/SrvDomainDir.py", line 149, in 
> _list
>   self.ls_domain(req, detail, False)
> File "//usr/lib/python/xen/xend/server/SrvDomainDir.py", line 167, in 
> ls_domain
>   req.write(
> AttributeError: XendDomainInfo instance has no attribute 'getSsidref'
> 
> This is xen 3.03 with a RHEL4U3 host.  I downloaded the source and built 
> it from scratch.  Have I gone wrong somewhere?

This is a regression that I fixed this last week -- you need the
attached patch, which you ought to be able to apply singly, or you could
pull forward to the latest xen-unstable.

That said, this server is by far the worst of all your options for demo'ing Xen!
What are you trying to demo?  There are a plethora of Xen administration
interfaces, both web-based and not, open source and not, and I'm pretty
sure that any one of them is better than that HTTP interface.

Ewan.

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

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