19.03.2013 20:16, David Teigland wrote: > On Tue, Mar 19, 2013 at 07:52:14PM +0300, Vladislav Bogdanov wrote: >> And, do you have any estimations, how long may it take to have you ideas >> ready for production use? > > It'll be quite a while (and the new locking scheme I'm working on will not > include remote command execution.) > >> Also, as you're not satisfied with this implementation, what alternative >> way do you see? (calling ssh from libvirt or LVM API is not a good idea >> at all I think) > > Apart from using ovirt/rhev, I'd try one of the following behind the > libvirt locking api: sanlock, dlm, file locks on nfs, file locks on gfs2. Unfortunately none of these solve the main thing I need: Allow LVM snapshots without breaking live VM migration :( Cluster-wide snapshots (with shared lock) would solve this, but I do not expect to see this implemented soon. _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/