On Wed, Jun 04, 2008 at 01:36:17AM +0200, Stefan de Konink wrote: > Or just exending libvirtd with proxy functionality. I would like to hear > the Red Hat ideas on this one. This kind of functionality doesn't really belong in libvirtd. It is not intended to be a centralized management daemon for multiple nodes. It has one job - provide remote access to the libvirt APIs for a single node. If you want management of a whole cluster/network of machines then you want to have a separate management server talking to the libvirtd on each node and providing an aggregate view of some kind. libvirt isn't intended to be a complete management application in its own right - it is just providing the base infrastructure on which you can build applications. One such application is oVirt which talks to multiple libvirtd enabled hosts and provides an aggegrate view. There are other people working on similar types of application. Dan. -- |: Red Hat, Engineering, London -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/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list