Bug 1139112 - [RFE] Geo-replication configuration should have help option.
Summary: [RFE] Geo-replication configuration should have help option.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: geo-replication
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard: status,config
Depends On: 1138541
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-08 06:26 UTC by Darshan
Modified: 2018-04-16 15:56 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1138541
Environment:
Last Closed: 2018-04-16 15:56:05 UTC
Embargoed:


Attachments (Terms of Use)

Description Darshan 2014-09-08 06:26:59 UTC
+++ This bug was initially created as a clone of Bug #1138541 +++

Description of problem:

     Geo-replication config should have a help option which would give details like possible values for attributes or specify whether an attribute is configurable or not. some thing similar to "gluster volume set help".

     RHSC can use this help option to decide whether an attribute is configurable or not. By this console can block modifications of such attributes right away, instead of user trying to modify such attributes and later getting an error message and if there are a set of possible values to an attribute rhsc can provide a list from which user can choose.

     Its better to get the information related to attributes from gluster than store this info in RHSC. As later option may lead to inconsistency .


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Aravinda VK 2018-02-06 08:08:43 UTC
Geo-replication support added to Glusterd2 project, which will be available with Gluster upstream 4.0 and 4.1 releases. 

Most of the issues already fixed with issue https://github.com/gluster/glusterd2/issues/271 and remaining fixes are noted in issue https://github.com/gluster/glusterd2/issues/557

We can close these issues since we are not planning any fixes for 3.x series.


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