On Thu, Jun 18, 2015 at 01:20:59PM +0300, Vasiliy Tolstov wrote: > 2015-06-18 12:01 GMT+03:00 Daniel P. Berrange <berrange@xxxxxxxxxx>: > > FWIW, we really consider the RPC protocol to be a private impl detail > > and strongly discourage people from trying to re-implement it > > themselves. > > > > Can you explain a bit more about what you're trying to achieve by > > creating an RPC proxy > > > I have DO like cloud hosting and want to provide libvirt compat > endpoint to create/start/stop servers. I really discourage anyone from trying to fit the libvirt API over a cloud system. In general the libvirt API is designed to be fairly host-centric. We did once have a libvirt driver that targetted a cloud system, but we deleted it because the libvirt API was a bad fit for case where the concept of individual hosts is hidden from the user. I'd really recommend that any cloud hosting exposes one or more of the common cloud APIs, in particular EC2 compatible API, and possibly an OpenStack compatible API. There are also some projects that attempt to provide a cloud API abstraction layer, in the same way that libvirt provides a host API abstraction layer. eg libcloud, or the (now defunct IIRC) deltacloud. Regards, 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 :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list