Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1533477

Summary:	Gluster volumes should be supported in a DR solution
Product:	[oVirt] ovirt-ansible-collection	Reporter:	Maor <mlipchuk>
Component:	disaster-recovery	Assignee:	Sahina Bose <sabose>
Status:	CLOSED WORKSFORME	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	lsvaty, sabose, sasundar
Target Milestone:	ovirt-4.3.1	Keywords:	RFE
Target Release:	---	Flags:	rule-engine: ovirt-4.3? sasundar: planning_ack? sasundar: devel_ack? sasundar: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	DR
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-18 05:23:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Maor 2018-01-11 13:08:58 UTC

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:

Comment 1 Sahina Bose 2018-04-03 13:02:59 UTC

(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?

Comment 2 Maor 2018-04-03 13:16:08 UTC

(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

Comment 3 Sahina Bose 2018-11-21 15:13:42 UTC

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

Comment 4 Sandro Bonazzola 2019-01-28 09:37:03 UTC

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.

Comment 5 SATHEESARAN 2019-02-14 09:09:28 UTC

(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.

Comment 6 Sahina Bose 2019-02-18 05:23:14 UTC

Thanks Sas. I think the request was for the volume to be managed at secondary site - which is already done.
Hence closing this bug