On 14.12.2015 18:10, Peter Krempa wrote:
On Mon, Dec 14, 2015 at 17:18:22 +0300, Dmitry Andreev wrote:
Hi,
I'm looking for a mechanism to do a sequence of API calls as atomic
operation. Is there any way for libvirt's API client to acquire an
exclusive VM lock to prevent other client from changing VM state
through libvirt?
No there isn't anything. Libvirt is locking only on internal events that
need protection.
Doing transaction locking should be relatively easy to implement on
application layer though.
Sure we can implement a lock manager on the API client side, but it
can't lock VM for other clients. And that’s the problem for us.
Are maintainers interested in VM lock manager on the server side?
Can I move in this direction or you have something against it?
Peter
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list