From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <514897BE.90609@hoster-ok.com> Date: Tue, 19 Mar 2013 19:52:14 +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> In-Reply-To: <20130319155456.GC986@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 18:54, David Teigland wrote: > On Tue, Mar 19, 2013 at 06:42:02PM +0300, Vladislav Bogdanov wrote: >> And... Every cluster has nodes. Clustered LVM VG assumes you have >> cluster. Why not be cluster-aware in tools then? > > The changes I'm making move away from remote command execution within lvm > itself because it's poor a design and complicates things tremendously for > a dubious feature. Also, it would not fit well at all with sanlock which > I'm adding support for. There are much better ways of doing remote > commands. > David, can you please share where you go, because google shows only recent thread from this list when I ask it about lvmlockd. And, do you have any estimations, how long may it take to have you ideas ready for production use? 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)