Bug 1707823 - Update the upgrade doc to how to bypass the 1000 volume limit brought in rhgs-volmanager v3.11.3
Summary: Update the upgrade doc to how to bypass the 1000 volume limit brought in rhgs...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Container_Native_Storage_with_OpenShift
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: OCS 3.11.z Batch Update 4
Assignee: Anjana KD
QA Contact: Sri Vignesh Selvan
URL:
Whiteboard:
Depends On: 1476223
Blocks: 1709460
TreeView+ depends on / blocked
 
Reported: 2019-05-08 13:22 UTC by Raghavendra Talur
Modified: 2019-11-04 15:44 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-04 15:44:36 UTC
Embargoed:

Attachments (Terms of Use)

Description Raghavendra Talur 2019-05-08 13:22:58 UTC 
Description of problem:

If a user/admin has already crossed 1000 volumes limit that heketi imposes then we provide a method to override the limit.

Best way is to provide a higher value in the ENV or the heketi config json.
We should document it at relevant places in the doc.
Comment 8 Anjana KD 2019-10-20 19:31:27 UTC 
Hello Talur

Based on comments https://bugzilla.redhat.com/show_bug.cgi?id=1746446#c1 and https://bugzilla.redhat.com/show_bug.cgi?id=1746446#c3. I have added the link to the KCS article. 

Is a new section or an appendix still required here? Let me know your thought. I will make the changes accordingly.


Have updated the above sections in the doc.

3.1.4. Deployment and Scaling Guidelines
https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.11/html-single/deployment_guide/index?lb_target=stage#Planning_Guidelines

3.2.5. Deployment and Scaling Guidelines
https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.11/html-single/deployment_guide/index?lb_target=stage#Planning_Guidelines_CRS


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