Bug 1536128 - RHHI-V Geo-Replication configuration is hard to consume by the end user
Summary: RHHI-V Geo-Replication configuration is hard to consume by the end user
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Maintaining_RHHI
Version: rhhi-1.1
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: Laura Bailey
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1536125
Blocks: 1724792
TreeView+ depends on / blocked
 
Reported: 2018-01-18 16:43 UTC by Dave
Modified: 2020-12-09 12:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-09 12:24:40 UTC
Embargoed:


Attachments (Terms of Use)

Description Dave 2018-01-18 16:43:53 UTC
Description of problem:
There's no one document for setting up Geo-replication for RH-HI right now (or a simple, easy to consume, automated approach either. I have been told that functionality is coming in gdeploy but how will that be utilized by the end user?). There's 4+ documents to follow. The end user can easily get lost, confused or  unable to set up geo-replication (which is a highly advised functionality). This lends itself to deterring the end user from setting up and using this product at all. This severely inhibits the user experience in addition to inhibiting testing internally by Red Hat engineers. It is a daily task to figure out what we're trying to do at a concept level versus how that translates into RHV-m versus how to actually do that via the gui and/or cli. This should all be a seamless experience. Left unchanged this will hurt the RH-HI solutions acceptance.

Version-Release number of selected component (if applicable):
1.1 and 1.1+

How reproducible:
Daily issues


Expected results:

An easy to follow document (Read: One document) that clearly has the steps to manually configure Geo-Replicaiton for RH-HI

Comment 2 Laura Bailey 2018-03-14 10:29:29 UTC
Resetting component, as this seems like more of a docs usability issue than a product issue.

Comment 3 Dave 2018-05-21 16:55:34 UTC
Bug scrub: Is the plan for this to wait until the documentation tool is changed?

Comment 14 SATHEESARAN 2019-07-15 05:12:33 UTC
Removing the qa_ack and also updating the target_release flag

Comment 19 SATHEESARAN 2020-12-09 12:24:40 UTC
The existing content for DR use case is pretty comprehensive with information available in one single docbook.
Please try with RHHI-V 1.8 maintenance guide


Note You need to log in before you can comment on or make changes to this bug.