Description of problem: Currently geo-replication setup restricts that the slave volume is also managed by the oVirt instance which manages the master gluster volume. But there are use cases in which the slave volume is at a remote site with flaky network connection and we do not want to further burden network managing and polling this instance The restrictions on choosing the gluster volume should be removed with warning if needed that slave volume suitability cannot be checked. Version-Release number of selected component (if applicable): How reproducible: NA Steps to Reproduce: NA. --- Additional comment from Sahina Bose on 2016-12-16 06:06:10 UTC --- Setting up geo-replication with a non-managed volume has challenges as there's no vdsm on remote host to setup passwordless ssh and run mount broker commands. --- Additional comment from Sahina Bose on 2017-09-22 11:54:19 UTC --- Need to check if this can be done via Ansible roles
Please ACK or CLOSE.