Re: [PATCH 00/14] Add a virtlockd lock manager daemon

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

 



On Thu, Jul 07, 2011 at 03:17:18PM +0100, Daniel P. Berrange wrote:
> The lock manager infrastructure we recently added to QEMU only has
> two possible drivers at this time, 'nop' and 'sanlock'. The former
> does absolutely nothing, while the latter requires a 3rd party
> package installed and is a little heavy on disk I/O and storage
> requirements.
> 
> This series adds a new daemon 'virtlockd' which is intended to be
> enabled by default on all hosts running 'libvirtd'. This daemon
> provides a service for disk locking based on the traditional
> fcntl() lock primitives. There is a new libvirt manager plugin
> which talks to this daemon over RPC. The reason for doing the
> locks in a separate process is that we want the locks to remain
> active, even if libvirtd crashes, or is restarted. The virtlockd
> daemon has this one single job so should be pretty reliable and
> selfcontained. This patch series really benefits from the new RPC
> APIs, requiring minimal code for the new daemon / client

It seems this nice feature never got in. Are you plannign a respin?
Cheers,
 -- Guido

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list


[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]
  Powered by Linux