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] question on XML-RPC interface to xend

To: "Ewan Mellor" <ewan@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] question on XML-RPC interface to xend
From: "Jayesh Salvi" <jayeshsalvi@xxxxxxxxx>
Date: Sun, 28 May 2006 14:34:43 -0500
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 28 May 2006 12:35:05 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Ylqy3wzUmVLCuNfFtQQ9gWTnbotkMg7T1JeGOgDJEseg+JAt2ayvquTRsjJycqQBrSXsabPqQRp87ETiQJ8u+la9ks5eJS9hcfcf3MpdQirXuoT+650hv/NR06j6TQh4o5raA1DySY0mO34a4lXWy2Bw2fjUefNZQjy8EH+aCl4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060528165631.GA22622@xxxxxxxxxxxxxxxxxxxxxx>
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: <871640aa0605280731t6a10c7f8k4f386b3689b62fff@xxxxxxxxxxxxxx> <20060528165631.GA22622@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 5/28/06, Ewan Mellor <ewan@xxxxxxxxxxxxx> wrote:
On Sun, May 28, 2006 at 02:31:29PM +0000, Jayesh Salvi wrote:

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

It's certainly the intention that xm can work remotely, though it does
seem to be broken at the moment.

The attached patch is enough for me to be able to use xm remotely.  This
might be enough for you for now.  Bear in mind that by enabling the TCP
server, you are opening a very large security hole -- you should only
use this on a secure network.

There is work already planned to fix this whole area, so if you can wait
a few weeks, all this should be in a good state for you again.

Thanks Ewan for the patch. I will try it. Or if it's matter of weeks I will stick to 3.0.1 using my old method.



Everything you can imagine is real
Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>