[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] question on XML-RPC interface to xend


  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Jayesh Salvi" <jayeshsalvi@xxxxxxxxx>
  • Date: Sun, 28 May 2006 14:31:29 +0000
  • Delivery-date: Sun, 28 May 2006 07:31:50 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=HuIw8rupSJDjoApzS1QjKm35abDxvmhttgFFkP4LfGBxLd/8qVaa2uzt0WA587XGKVhpX3DrPe4r/rLn0bkO/cXY58o2yQbPvUvaGzSFwGJ1LR3hOZ+Th600wrxZu/eOEEI9riZD8bAn2a1kE/Xmqc7P4z6unfUtz8+pz/VXy0E=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,

I noticed that an XMLRPC interface has been introduced from 3.0.2+. This is breaking the remote execution of xm commands I used to do.

This change entirely changed the tools/python/xen/xend/XendClient.py. I used to remotely control the pool of servers by doing:
XEND=<remote server name> xm <operation>

For this I had to change last line of XendClient.py from getUnixServer() to getHttpServer() . This tweak changed the way "xm" connects to xend process - instead of Unix domain sockets it uses Http connections.

This setup used to work fine. I however do not understand the XML-RPC behavior from "xm"'s point of view. The XendClient.py now just opens a ServerProxy for a xmlrpc socket, which take httpu URI. I don't know how I can direct xm operations to the remote physical servers now.

Is remote access using xm discontinued because of this change? Or is there some method?

Please let me know.
Thanks,

--
Jayesh
------------------------------------------------------------------------
Everything you can imagine is real
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.