I'd be very interested in the output, I really enjoy learning languages
by-project although in my case the result isn't often the best way of
doing things :p Maybe it's the way I learn!!
The bonus of python presumably is that you can use the api straight from
a python website, at the moment i'm using PHP (which i know extremely
well and can whack up a website in in no time) to exec() perl scripts
which do the administrative tasks for me.
There's certainly an open source project in here somewhere, something
where sysadmins can slot in a solution with their existing setup without
having to do enormous amounts of reconfiguration - in an operating
system independent manner (even the webserver could be packaged, like
webmin or cpanel)). Glad to hear i'm not the only one out there, let me
know if I can help at all.
Henri
Spencer Parker wrote:
I am actually in the process of trying to develop one of these in
Python. Since I am pretty new to python or programming in general, it
has been a really good learning experience. I haven't really gotten
very far yet...since its all learning about basically everything...its
been fun. I have made some basic calls to the API and had the info
shoved into a MySQL database...but thats about...nothing grand.
On Mon, Apr 7, 2008 at 12:44 PM, Daniel P. Berrange
<berrange(a)redhat.com <mailto:berrange@redhat.com>> wrote:
On Mon, Apr 07, 2008 at 02:38:17PM +0100, Richard W.M. Jones wrote:
> On Sat, Apr 05, 2008 at 09:35:33PM +0100, Henri Cook wrote:
> > I'm designing a web interface for libvirt so that my customers can
> > manage their DomUs - unless you know of a good one that
already exists???
> >
> > I'm thinking that the best way to run this is have the web server
> > connected to libvirtd - but I can't find any documentation
about the API
> > it presents - can you help?
>
> I sort of gathered from IRC that you are using Perl & Dan's Perl
> bindings. This is the right approach.
>
> In order to be able to contact libvirtd without needing to run
> anything as root you (may) need to change the permissions on the
> libvirtd socket (normally /var/run/libvirt/libvirt-sock). If your
> libvirt was configured to use PolicyKit you may also need to
edit the
> configuration file /etc/PolicyKit/PolicyKit.conf to allow your web
> server user access to the privilege 'org.libvirt.unix.manage'.
PolicyKit is one option - you'd need to edit
/etc/PolicyKit/PolicyKit.conf
to add an explicit rule allowing the httpd user access.
Alternatively you could switch the UNIX socket to use SASL as its auth
method, and setup a SASL username & password
There's some docs here
http://libvirt.org/auth.html
Dan.
--
|: Red Hat, Engineering, Boston -o-
http://people.redhat.com/berrange/ :|
|:
http://libvirt.org -o-
http://virt-manager.org -o-
http://ovirt.org :|
|:
http://autobuild.org -o-
http://search.cpan.org/~danberr/
<
http://search.cpan.org/%7Edanberr/> :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742
7D3B 9505 :|
--
Libvir-list mailing list
Libvir-list(a)redhat.com <mailto:Libvir-list@redhat.com>
https://www.redhat.com/mailman/listinfo/libvir-list
--
Spencer Parker
_______________________________________________________
"if you can't go to heaven, may you at least die in Ireland."
_______________________________________________________
------------------------------------------------------------------------
--
Libvir-list mailing list
Libvir-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list