[linux-lvm] [PATCH 10/10] man: document --node option to lvchange

[Vladislav Bogdanov]

19.03.2013 18:32, David Teigland wrote:
> On Tue, Mar 19, 2013 at 01:32:50PM +0000, Vladislav Bogdanov wrote:
>> +.B \-\-node \fINodeID
>> +Perform specified activation command on a remote cluster node (the same to running
>> +corresponding command on that node locally).
>> +Currently tested only for corosync clusters (\fB-I\fP \fIcorosync\fP option to clvmd)
>> +for corosync versions from 2.0.
>> +If corosync configuration has node names in a nodelist (nodelist.node.X.name = name
>> +in CMAP tems) or node names are used for ring0_addr (nodelist.node.X.ring0_addr = name),
>> +then that names may be used as NodeID. Otherwise numeric node IDs should be used.
> 
> lvm tools should move away from doing remote command execution.

This would break current behavior btw (I do not say current is the right
one, but it exists).
lvchange -ay|-an on a clustered LV activates it shared everywhere in
cluster. Internally this is done by sending message to all nodes
(wildcard). Each node obtain shared lock itself then.

I just slightly modified this to be able to send targeted messages.
Everything was already in code, I just made it work for non-wildcard
messages and added possibility to enable this in tools.

> As you mentioned before, this is the equivalent of "ssh node lvchange".
> ssh or some other tool outside lvm is the right way to run the remote
> commands.
> 
> Also, lvm should not assume that it's using dlm/corosync, or that this
> kind of remote option will be possible to support.
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>