Bug 1703053

Summary: [Tracker for bug 1378321] Allow setting up geo-replication session with non managed volumes
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: rhhiAssignee: Patric Uebele <puebele>
Status: CLOSED DEFERRED QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: medium    
Version: rhhiv-1.6CC: bugs, godas, jiazhang, rhs-bugs, sabose, seamurph
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1378321 Environment:
Last Closed: 2020-03-20 10:32:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1378321    
Bug Blocks:    

Description SATHEESARAN 2019-04-25 11:46:18 UTC 
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
Comment 2 Yaniv Kaul 2019-07-22 08:31:00 UTC 
Please ACK or CLOSE.