[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] Different approach to locking

On Thu, Nov 11, 2010 at 11:35:55AM +0000, Daniel P. Berrange wrote:

> If you wanted to avoid directly using the libvirt lock manager plugins,
> and use a public libvirt API, then the other option is for libguestfs to
> create a custom XML with all the requested disks, and boot a transient
> libvirt guest with the libguestfs kernel/initrd/appliance and attach to
> the guestfsd inside that VM. Then the locking would all 'just work' since
> libguestfs would be a normal libvirt client application.

Yet another option would be to directly implement the locking schemes
in libguestfs itself. eg directly talk to sync-manager via its CLI
tool, or directly talk to libvirt's  virt-lockd (or follow the same
fcntl() locking rules that virt-lockd will use). Of course this is
probably more code work than all the other options, but is maximally
flexible in how you integrate.

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

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]