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

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



On Mon, Dec 05, 2011 at 06:54:08PM +0100, Guido Günther wrote:
> 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?

Yeah, I did quite a big re-design of the internal code impl, but I
have not finished it off yet.


Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|


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