From: Anthony Liguori <aliguori@us.ibm.com>
To: Michael Mey <michael.mey@to.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: remote xend - howto connect??
Date: Mon, 06 Feb 2006 21:02:09 -0600 [thread overview]
Message-ID: <43E80DB1.5040409@us.ibm.com> (raw)
In-Reply-To: <200602061556.36972.michael.mey@to.com>
Michael Mey wrote:
> Hi,
>
> currently, I am planning to implement a command line based tool to query more
> than one xends for their running domains at the same time.
>
> Unfortunately, I cannot connect to any other xend as the local one. This is
> what I was trying to do:
>
> ----------------------------------------------------------------------------------------------------
> #!/usr/bin/env python
> # -*- mode: python; -*-
> import sys
> import os
>
> # add fallback path for non-native python path installs if needed
> sys.path.append('/usr/lib/python')
> sys.path.append('/usr/lib64/python')
>
> from xen.xend.XendClient import server
>
from xen.xend.XendClient import getHttpServer
server = getHttpServer(...)
Of course, I'm not sure works all that well either.
I'd recommend using libvir (http://www.libvir.org). libvir speaks the
S-Expression/HTTP protocol pretty well. It also has python bindings.
Regards,
Anthony Liguori
> from xen.xend import sxp
>
> def parse_doms_info(info):
> def get_info(n, t, d):
> return t(sxp.child_value(info, n, d))
> return {
> 'dom' : get_info('domid', int, -1),
> 'name' : get_info('name', str, '??'),
> 'mem' : get_info('memory', int, 0),
> 'vcpus' : get_info('online_vcpus', int, 0),
> 'state' : get_info('state', str, '??'),
> 'cpu_time' : get_info('cpu_time', float, 0),
> 'ssidref' : get_info('ssidref', int, 0),
> }
>
> def xm_brief_list(doms):
> print 'Name ID Mem(MiB) VCPUs State Time(s)'
> for dom in doms:
> d = parse_doms_info(dom)
> if (d['ssidref'] != 0):
> d['ssidstr'] = (" s:%04x/p:%04x" %
> ((d['ssidref'] >> 16) & 0xffff,
> d['ssidref'] & 0xffff))
> else:
> d['ssidstr'] = ""
> print ("%(name)-32s %(dom)3d %(mem)8d %(vcpus)5d %(state)5s
> %(cpu_time)7.1f%(ssidstr)s" % d)
>
>
> server.bind('192.168.111.18:8000',)
> xm_brief_list(server.xend_list_domains())
> ----------------------------------------------------------------------------------------------------
>
> I am running this script form my xenhost1 (192.168.111.17) and want to query
> xenhost2 (192.168.111.18). But I only get the local informations.
> Even if I manually hack
>
> class Xend:
> """Client interface to Xend.
> """
>
> """Default location of the xend server."""
> SRV_DEFAULT = "192.168.111.18:8000"
>
> into xen/xend/XendClient.py it's still the same.
>
> telnetting to 192.168.111.18 to port 8000 and do a manual
> GET /xend/domain/?detail=1
> works nicely.
>
> Maybe someone could give me a hint how to query a remote xen host with
> XendClient.py?
>
>
> Regards, Michael
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2006-02-07 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 14:56 remote xend - howto connect?? Michael Mey
2006-02-07 3:02 ` Anthony Liguori [this message]
2006-02-07 9:14 ` Michael Mey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43E80DB1.5040409@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=michael.mey@to.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.