Bug 1572591 - Request for adding setup details and steps for CNS+Geo-Rep operations in CNS documentation
Summary: Request for adding setup details and steps for CNS+Geo-Rep operations in CNS ...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: doc-Container_Native_Storage_with_OpenShift
Version: cns-3.9
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: storage-doc
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-27 11:28 UTC by Neha Berry
Modified: 2021-05-12 02:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Neha Berry 2018-04-27 11:28:43 UTC
Description of problem:

Description of the use case:
#################################

As a user, I would like set up Container-Native Storage volumes for geo-replication to a non-Container-Native Storage remote site. Current documenation briefly specifies the details but a more detailed documentation for this use case will be very handy.

Hence would like to request for a change/addition to the documentation for the above use case

Moreover , the current documentation points towards Geo-rep on gluster  v3.2 instead of latest gluster v3.3.

Document Link
##################
https://access.redhat.com/documentation/en-us/container-native_storage/3.9/html-single/container-native_storage_for_openshift_container_platform/

Document Section
######################
 
Chapter 11. Operations on a Red Hat Gluster Storage Pod in an OpenShift Environment --> Point #10.

Current details in doc
##########################

Currently the doc has a brief description of configuring geo-rep on CNS and then points to the gluster geo-rep documentation. But the geo-rep settings for CNS and standalone Gluster vary significantly, hence it would be better to get the geo-rep setup details in CNS perspective.

Snippet from current document
###############################

You can set up Container-Native Storage volumes for geo-replication to a non-Container-Native Storage remote site. Geo-replication uses a master–slave model. Here, the Container-Native Storage volume acts as the master volume. To set up geo-replication, you must run the geo-replication commands on gluster pods. To enter the gluster pod shell, execute the following command:
 # oc rsh <gluster_pod_name>
For more information about setting up geo-replication, refer https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.2/html/administration_guide/chap-managing_geo-replication.



CNS+GEO-REP use case may also include documenting some of the following points:
------------------------------------------------------------------------

(a) All prerequisite information and possible setup details. e.g passwordless ssh authentication in CNS setup for geo-rep, etc.
 
(b) All possible implementations which can be supported for Geo-rep in CNS , i.e. 
    1 In case of CNS on master and non-cns in slave, complete setup requirement on both sides, including the passwordless ssh authentication information.
    
    2. Whether we can have geo-rep between volumes of 2 CNS DCs. If yes, what could be the setup requirements and use cases, in terms of pods and pvcs.

If documented, it would help in setting up a geo-rep deployment without errors.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:




Describe the issue: 

Suggestions for improvement: 

Additional information: 


Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


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