Re: [libvirt] remote access libvirtd / bindings for php/asp

On Wed, Jun 04, 2008 at 02:01:21AM +0200, Stefan de Konink wrote: Hum, no really we disagree on this. libvirtd is just here because it's the only way to implement the API in a correct and secure way and garantee transparent remote access. The kind of APIs that have been designed in libvirt are based on the assumption you talk to one Node (please go back to the introduction on the architecture http://libvirt.org/intro.html ), there is no notion of cluster. You don't list domains or peripherals on a cluster with the same kind of APIs as you can do on a node. The latter allows direct immediate answers part of synchronous single call. For a cluster you need asynchronous queries, filtering built into the API or it becomes useless. Trying to turn libvirt into a cluster management API is something which doesn't make sense. The goal is to provide an API which allows to build those tools relatively easilly on top, or simpler tools for smaller solutions. Turning libvirtd into a cluster management daemon just doesn't make sense to me based on the previous point and the fact that the daemon has been designed to be a libvirt API server not a client querying other nodes, this would need threading, caching, local state, change in security, plus a change of the kind of API being served. Really what you're looking for is a different development, better done on top of libvirt but not in libvirt. Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard(a)redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/