Description of problem: The DR ansible playbook supports adding a gluster storage domain using a mount option, although gluster volumes configured in oVirt are not yet supported through the recovery process. We should add gluster volumes as part of the recovery process of DR site to site Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
(In reply to Maor from comment #0) > Description of problem: > The DR ansible playbook supports adding a gluster storage domain using a > mount option, although gluster volumes configured in oVirt are not yet > supported through the recovery process. > We should add gluster volumes as part of the recovery process of DR site to > site > > What does it mean to add gluster volumes as part of recovery process? Do you mean the management of the volumes?
(In reply to Sahina Bose from comment #1) > (In reply to Maor from comment #0) > > Description of problem: > > The DR ansible playbook supports adding a gluster storage domain using a > > mount option, although gluster volumes configured in oVirt are not yet > > supported through the recovery process. > > We should add gluster volumes as part of the recovery process of DR site to > > site > > > > > > What does it mean to add gluster volumes as part of recovery process? Do you > mean the management of the volumes? Yes, to where the engine manage bricks
Sas, for the DR recovery via Ansible, is there currently a gap? Do we need the gluster volumes managed at the secondary site? If not, we can close this
This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
(In reply to Sahina Bose from comment #3) > Sas, for the DR recovery via Ansible, is there currently a gap? Do we need > the gluster volumes managed at the secondary site? > If not, we can close this The secondary site too has the RHV Manager instance and a hyperconverged setup, where the gluster volume is already managed. Master volume is managed in the RHV Manager instance in the primary site and geo-rep session is created via gluster CLI. In this case, I do not see a requirement for workflow to import gluster volumes at the secondary site. If I have misunderstood the question, please clarify.
Thanks Sas. I think the request was for the volume to be managed at secondary site - which is already done. Hence closing this bug