[libvirt] image locking?

Daniel P. Berrange berrange at redhat.com
Wed Oct 22 20:49:10 UTC 2008

On Wed, Oct 22, 2008 at 10:21:38PM +0200, Guido G?nther wrote:
> On Tue, Oct 21, 2008 at 12:16:01PM -0700, Itamar Heim wrote:
> > While this might work for SBC (although most enterprises have the
> > datacenter on remote sites as well, so not always that easy).  I don't
> > think the solution is viable for CBC though (I am not sure CBC would
> > use iSCSI, probably NFS is a more relevant option, but the leased
> > locking is required there as well, just as a collaborative effort to
> > notate to the non-responding node to stop writing to the image).
> What about using dlm? This gives fencing for free. See my other post
> - allowing libvirt to use cluster wide storage locks would solve your
> problem?

Yes it all comes back to clustering. If you have clustering you can 
build a reliable image locking system across all types of storage
backend. If you don't have clustering you can make a best effort,
likely only enforcing safety within the scope of a single host. 

We need libvirt to enforce safety per host using standard POSIX locking
because we cann't demand that everyone using clustering.

We should optionally use some cluster based locking scheme if it is 
available, as a 2nd layer ontop of the basic single-host view locking

|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

More information about the libvir-list mailing list