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@lists.xensource.com http://lists.xensource.com/xen-devel
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. Cheers, Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 5/28/06, Ewan Mellor <ewan@xensource.com> 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. Cheers,> > Ewan. > > >-- Jayesh ------------------------------------------------------------------------ Everything you can imagine is real _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel