[libvirt] language bindings
Hello. I'm newbie in libvirt world and not able to find answer for my question in google. If i want to create binding for some language (for example go) is that possible do not use libvirt C library and talk to libvirtd via some rpc protocol? For example json or internal binary.. is that possible to talk to libvirtd not using C library? -- Vasiliy Tolstov, e-mail: v.tolstov@selfip.ru jabber: vase@selfip.ru
On 04/04/2013 08:47 AM, Vasiliy Tolstov wrote:
Hello. I'm newbie in libvirt world and not able to find answer for my question in google. If i want to create binding for some language (for example go) is that possible do not use libvirt C library and talk to libvirtd via some rpc protocol? For example json or internal binary.. is that possible to talk to libvirtd not using C library?
It would be possible to bind RPC calls for remote interfaces, but that would limit the scope of what your bindings can do. That is, you would be able to control stateful URIs like qemu:/// and lxc:/// but not stateless URIs like esx:///. All of the existing language bindings are built on top of the C interface in libvirt.so, for a reason. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
On Thu, Apr 04, 2013 at 06:47:49PM +0400, Vasiliy Tolstov wrote:
Hello. I'm newbie in libvirt world and not able to find answer for my question in google. If i want to create binding for some language (for example go) is that possible do not use libvirt C library and talk to libvirtd via some rpc protocol? For example json or internal binary.. is that possible to talk to libvirtd not using C library?
We explicitly do *not* want anything other than the libvirt C library talking the RPC protocol. We consider the RPC protocol to be a *private* implementation detail for libvirt.so and libvirtd only. Nothing else should ever use it, not least because not all libvirt drivers actually make use of the RPC protocol. We also do not make any guarantees that it will continue to operate in the same way long term, so if you use the RPC api you may find yourself broken by future libvirt releases. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
2013/4/4 Daniel P. Berrange <berrange@redhat.com>:
We explicitly do *not* want anything other than the libvirt C library talking the RPC protocol. We consider the RPC protocol to be a *private* implementation detail for libvirt.so and libvirtd only. Nothing else should ever use it, not least because not all libvirt drivers actually make use of the RPC protocol. We also do not make any guarantees that it will continue to operate in the same way long term, so if you use the RPC api you may find yourself broken by future libvirt releases.
Thanks! Does it possible to compile libvirt C library to static library? -- Vasiliy Tolstov, e-mail: v.tolstov@selfip.ru jabber: vase@selfip.ru
participants (3)
-
Daniel P. Berrange -
Eric Blake -
Vasiliy Tolstov