Re: [libvirt] RFC [3/3]: Lock manager usage scenarios

2010-09-13 Thread Saggi Mizrahi
On Mon, 2010-09-13 at 14:29 +0100, Daniel P. Berrange wrote: > On Mon, Sep 13, 2010 at 03:20:13PM +0200, Saggi Mizrahi wrote: > > On Mon, 2010-09-13 at 13:35 +0100, Daniel P. Berrange wrote: > > > > > > > > Overall, this looks workable to me. As proposed, thi

Re: [libvirt] RFC [3/3]: Lock manager usage scenarios

2010-09-13 Thread Saggi Mizrahi
On Mon, 2010-09-13 at 13:35 +0100, Daniel P. Berrange wrote: > On Fri, Sep 10, 2010 at 02:39:41PM -0600, Eric Blake wrote: > > On 09/10/2010 10:01 AM, Daniel P. Berrange wrote: > > > > > >At libvirtd startup: > > > > > > driver = virLockManagerPluginLoad("sync-manager"); > > > > > > > > >At libvi

Re: [libvirt] RFC [1/3]: The internal lock manager API

2010-09-12 Thread Saggi Mizrahi
On Fri, 2010-09-10 at 17:00 +0100, Daniel P. Berrange wrote: > /** > * virLockManager: > * > * A lock manager is a process that will supervise another > * process. It will obtain & hold locks/leases for resources > * the supervised process uses > */ > > typedef struct virLockManager virLockM

Re: [libvirt] RFC [0/3]: A proposal for lock manager plugins

2010-09-12 Thread Saggi Mizrahi
Sorry for commenting so late but it was Rosh Hashana over here. Just to give you some pointers, sync_manager should also be zero config. host id, timeouts etc are not in a config. Host Id is decided when sync_manager starts, and timeouts are decided upon lease creation so that all the sync_managers