This bug is related to:
Bug 1208523 - Add instructions to disable lvmetad to chapter "2.3. Exclusive Activation of a Volume Group in a Cluster"

Bug 1223096 - Update procedure for configuring LVM in a cluster to note new options for lvmconf to disable lvmetad

This all involves coming up with a new procedure and coordinating this documentation. It will not make 7.2 GA so I'm moving this to 7.3 but this can go on the Portal at any time. We'll put this on the asap list.

Still not sure this is needed, but I don't want to lose this. Moving to 7.4.

The only place we currently document the lvmconf command in the LVM manual is here, as part of the section on lvmetad:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/logical_volume_manager_administration/metadatadaemon

And also in this summary section of LVM in a cluster (if we leave it in -- 

So we should add the new options there, and we should add the startstopservices option to the cluster admin guide.  If we leave this section in -- see BZ#1507973.

So this BZ should be addressed in conjunction with that one.

I have updated the LVM in a cluster procedures as per BZ#1507973 and I think what I need to do now is add a mention of the lvmconf command to the summary in the LVM manual of LVM in a cluster, while noting that for clvm Pacemaker takes care of things. I should also mention this command in the appendix on the metadata daemon, also mentioning that Pacemaker takes care of things for CLVM.

Ok, for the LVM manual:  For HA-LVM the summary in the LVM manual points to the configuration procedure for configuration HA-LVM in the Cluster Administration Guide, which is where this command is documented.  For CLVM in RHEL 7 the clvm resource agent takes care of this and the user shouldn't have to worry about it. I have now added the final sentence to this note in the section of the document on lvmetad:

Note:
The lvmetad daemon is not currently supported across the nodes of a cluster, and requires that the locking type be local file-based locking. When you use the lvmconf --enable-cluster/--disable-cluster command, the lvm.conf file is configured appropriately, including the use_lvmetad setting (which should be 0 for locking_type=3). Note, however, that in a Pacemaker cluster, the ocf:heartbeat:clvm resource agent itself sets these parameters as part of the start procedure. 

I will republish the LVM manual when review is completed for the issues noted in BZ# 150793 and I will close both BZs at once.

Correction to comment 6:  It is BZ#1507973 that I am waiting for.  I missed a digit.

The updated section on LVM volumes in a cluster (section 1.4) is here:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/logical_volume_manager_administration/lvm_cluster_overview

The updated section on creating volume groups in a cluster (4.3.3) is here:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/logical_volume_manager_administration/vg_admin#VG_create_cluster

The updated section on configuring GFS2/LVM in a cluster is here:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/global_file_system_2/ch-clustsetup-gfs2

The updated section on the lvmetad daemon is here:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/logical_volume_manager_administration/#metadatadaemon