Bug 1477726

Summary:	[HCI] [RFE] Automated solution for setting up geo replication
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Dave <dfitzpat>
Component:	geo-replication	Assignee:	Aravinda VK <avishwan>
Status:	CLOSED DUPLICATE	QA Contact:	Rahul Hinduja <rhinduja>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	annair, bturner, csaba, dfitzpat, rhs-bugs, storage-qa-internal, surs
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-04 06:24:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dave 2017-08-02 17:55:56 UTC

Description of problem:
There is no automated, preferably Ansible based, way of configuring geo replication available. Geo replication configuration can be intimidating even with the documentation. An automated alternative would help efficiency internally and help with the customer experience; especially in regards to RH-HI (HCI). 

How reproducible:
Always

Steps to Reproduce:
1. Try to configure geo replication manually

Actual results:
Must be done manually

Expected results:
Automated configuration of geo replication

Additional info:

Comment 2 Aravinda VK 2017-08-03 05:10:24 UTC

Gdeploy(Ansible based tool) already added support for Geo-replication.

https://github.com/gluster/gdeploy/commit/a1447c4304de50

Comment 3 Dave 2017-08-03 18:57:40 UTC

Thank you for your update, unfortunately we need something that is downstream.

Comment 4 Sachidananda Urs 2017-08-04 06:23:02 UTC

Hi Dave, this is slated for upcoming downstream release.
Tracked by the bz: https://bugzilla.redhat.com/show_bug.cgi?id=1475724

I'll mark this bug duplicate of the above bug.

Comment 5 Sachidananda Urs 2017-08-04 06:24:11 UTC


*** This bug has been marked as a duplicate of bug 1475724 ***