Bug 814809

Summary: Users don't understand that you cannot write to bricks
Product: [Community] Gluster-Documentation Reporter: Joe Julian <joe>
Component: OtherAssignee: Anjana Suparna Sriram <asriram>
Status: ON_QA --- QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: bugs
Target Milestone: ---Flags: joe: needinfo? (pyaduvan)
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://download.gluster.org/pub/gluster/glusterfs/3.2/Documentation/AG/html/chap-Administration_Guide-Setting_Volumes.html
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joe Julian 2012-04-20 18:24:35 UTC 
On http://download.gluster.org/pub/gluster/glusterfs/3.2/Documentation/AG/html/chap-Administration_Guide-Setting_Volumes.html a warning should be added to prevent customers from expecting replication of changes made directly to bricks.

"""
A volume is a logical collection of bricks where each brick is an export directory on a server in the trusted storage pool. Most of the gluster management operations happen on the volume.

### WARNING GOES HERE ###

You can create new volumes in your storage environment, as needed. When creating a new volume, you must specify the bricks that comprise the volume.
"""
Comment 1 Divya 2012-06-07 11:54:07 UTC 
I have warning for the same at: http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Storage/2.0/html/Administration_Guide/chap-User_Guide-Setting_Volumes.html
Comment 3 Joe Julian 2018-10-18 22:12:44 UTC 
Not sure why this is on QA for a change to RHS documentation. Shouldn't this change be "upstream first" before it can change from ASSIGNED?