From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <5148A215.7080004@hoster-ok.com> Date: Tue, 19 Mar 2013 20:36:21 +0300 From: Vladislav Bogdanov MIME-Version: 1.0 References: <1363699970-10002-1-git-send-email-bubble@hoster-ok.com> <1363699970-10002-11-git-send-email-bubble@hoster-ok.com> <20130319153215.GB986@redhat.com> <5148874A.2060106@hoster-ok.com> <20130319155456.GC986@redhat.com> <514897BE.90609@hoster-ok.com> <20130319171608.GE986@redhat.com> In-Reply-To: <20130319171608.GE986@redhat.com> Content-Transfer-Encoding: 7bit Subject: Re: [linux-lvm] [PATCH 10/10] man: document --node option to lvchange Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" To: David Teigland Cc: linux-lvm@redhat.com 19.03.2013 20:16, David Teigland wrote: > On Tue, Mar 19, 2013 at 07:52:14PM +0300, Vladislav Bogdanov wrote: >> And, do you have any estimations, how long may it take to have you ideas >> ready for production use? > > It'll be quite a while (and the new locking scheme I'm working on will not > include remote command execution.) > >> Also, as you're not satisfied with this implementation, what alternative >> way do you see? (calling ssh from libvirt or LVM API is not a good idea >> at all I think) > > Apart from using ovirt/rhev, I'd try one of the following behind the > libvirt locking api: sanlock, dlm, file locks on nfs, file locks on gfs2. Unfortunately none of these solve the main thing I need: Allow LVM snapshots without breaking live VM migration :( Cluster-wide snapshots (with shared lock) would solve this, but I do not expect to see this implemented soon.