GitHub user taocnrut added a comment to the discussion: doc for hackathon 2024
I think we would not need to tackle with sanlock directly since it is already (optionaly) used with lvm when volume group is created as shared (with vgcreate --shared) https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/configuring_and_managing_logical_volumes/configuring-lvm-on-shared-storage_configuring-and-managing-logical-volumes#configuring-lvm-on-san-multiple_configuring-lvm-on-shared-storage https://www.man7.org/linux/man-pages/man8/lvmlockd.8.html We should only need to take care of calling lvchange -an/lvchange -ay when apropriate provided that vg is created as shared and each host has unique host_id if sanlock is configured to be used (other option is dlm/corosync) I'll open issue with example of configuration and observed behaviour at this moment.. GitHub link: https://github.com/apache/cloudstack/discussions/9951#discussioncomment-11326999 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
