Bug 1386673

Summary: [Doc RFE] Document concept and task information related to how CNS 3.4 scales from a volume and cluster point of view
Product: Red Hat Gluster Storage Reporter: Anjana Suparna Sriram <asriram>
Component: doc-Container_Native_Storage_with_OpenShiftAssignee: storage-doc
Status: CLOSED NOTABUG QA Contact: storage-qa-internal <storage-qa-internal>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: cns-3.4CC: annair, asriram, rcyriac, rhs-bugs, storage-doc
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-20 12:15:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Anjana Suparna Sriram 2016-10-19 12:24:38 UTC 
Additional info: This bug will track the following use cases from the content plan: https://docs.google.com/document/d/1SrbUxavmmdbLn7FT2nhOAlX0Q3VTsqPCZyx6wV3gjn0/edit#


Use Case #1 As an administrator, I need to understand how CNS 3.4 scales from a volume and cluster point of view.

Provide concept information that explains CNS 3.4 scalability.
Provide a graphic illustration that shows a CNS 3.4 deployment that scaled successfully.


Use Case #2 As an administrator, I need to scale my CNS 3.4 deployment.

Provide detailed instructions regarding how to scale CNS 3.4.
Provide an applicable example of the scale workflow that reflects a CNS 3.4 context.