[ClusterLabs Developers] New LVM resource agent name (currently LVM-activate)

Eric Ren zren at suse.com
Thu Nov 23 03:54:41 EST 2017


> What about VolumeGroup (in the tradition of Filesystem, for instance)?
In the LVM-activate, we will support both all VG activation and only one 
specified LV
activation depending on the parameters.
> Or why not shoot for an LVM merge (plus proper versioning to tell
> the difference)?

You mean merging LVM-activate with the existing LVM? Here was a long 
discussion about that:



More information about the Developers mailing list