Bug 1572610 - Documentation for Geo-rep between CNS & non-CNS could include "HEKETI" as slave volume provisioner
Summary: Documentation for Geo-rep between CNS & non-CNS could include "HEKETI" as sl...
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 12:11 UTC by Neha Berry
Modified: 2021-05-12 02:13 UTC (History)
3 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 12:11:37 UTC
Description of problem:


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

In CNS "Container-Native Storage for OpenShift Container Platform" document, chapter #11->Point #10, there's a brief mention of setting up Container-Native Storage volumes for geo-replication to a non-Container-Native Storage remote site. 

The document doesn't mention that heketi could be used to create volumes on the slave side. As Heketi provides ease of administration and allows us to scale volume more easily, it may help to use standalone heketi in non-CNS side.

E.g.
++++++++
If we create master volume using CNS(PVC) it gets a particular size and creating similar sized volume on slave without heketi could be a challenge. This is because there is a --size= option in heketi to create volume of a particular size.

Also, it would be of great help to document the detailed steps for CNS+geo-rep setup. 

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
##########################

There's no mention of heketi for slave side gluster setup.

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.



















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.