From: David Isaac Wolinsky <davidiw@ufl.edu>
To: Tom Wilkie <tw275@cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Web based front end
Date: Sun, 04 Sep 2005 12:37:24 -0400 [thread overview]
Message-ID: <431B22C4.5080503@ufl.edu> (raw)
In-Reply-To: <B135126E-EB2A-41BB-AAA0-F5F88E29D170@cam.ac.uk>
Thanks Tom for the info, I had remembered twisted being removed but
hadn't realized that XenSV had been since updated. A couple questions
though...
Why not decouple the interface from Apache (as to require only
python be installed)? I am not sure of the performance advantage, but
it should reduce the memory requirements for dom0, allow for a slightly
smaller disk (negligible), and make installation easier.
Similarly have you looked into writing XenSV in C?
Finally, is there any distributed computing tools for Xen, ie, a
controller software? This is where my interest really lies, as I am
working for a group that could use a tool like this and am also looking
for a way to get involved.
I haven't had an oppurtunity yet to install apache, but will be doing so
soon enough.
Regards,
David
Tom Wilkie wrote:
> Dear David
>
> The web based front end, XenSV, is still alive and kicking in the
> latest unstable. I did some work on it a few weeks ago, removed its
> dependancy on twisted, and made it run using mod_python, and apache.
> I'm planing on doing some more work on it in the coming weeks, and
> doing a howto for installation.
>
> SV works by calling into the XendClient.py file, the same file xm
> uses to communicate with Xend. Its is written entirely in python,
> which probably isn't the best choice for a web app, but makes it
> easier to interface with xend.
>
> Cheers
>
> Tom
>
> On 4 Sep 2005, at 06:38, David Isaac Wolinsky wrote:
>
>> Hello all,
>>
>> I was curious if there is a web based front end (or one in the
>> works) for xen-unstable. Last I checked, the built-in one for 2.x
>> was being tossed out. Secondly assuming that there isn't one, would
>> the preferred language be python? Finally, would it be better to be
>> a front end for xm or would it be better to more tightly integrate
>> it (or of course the mix)?
>>
>> Thanks,
>> David
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>
>
next prev parent reply other threads:[~2005-09-04 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-04 5:38 Web based front end David Isaac Wolinsky
2005-09-04 7:20 ` Tom Wilkie
2005-09-04 16:37 ` David Isaac Wolinsky [this message]
2005-09-04 17:19 ` Tom Wilkie
2005-09-06 16:28 ` Anthony Liguori
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=431B22C4.5080503@ufl.edu \
--to=davidiw@ufl.edu \
--cc=tw275@cam.ac.uk \
--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.