Bug 1511981

Summary:	Unclear description of brick ports
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Jose A. Rivera <jarrpa>
Component:	Documentation	Assignee:	Chandrakanth Pai <chpai>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Vijay Avuthu <vavuthu>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.3	CC:	apaladug, chpai, rhs-bugs, sankarshan, storage-doc, storage-qa-internal, vavuthu
Target Milestone:	---
Target Release:	RHGS 3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-10 15:46:40 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:
Embargoed:
Bug Depends On:
Bug Blocks:	1503142

Description Jose A. Rivera 2017-11-10 14:54:58 UTC

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.3/html/administration_guide/chap-getting_started

Section Number and Name: 
Chapter 3, Table 3.1: TCP Port Numbers

Describe the issue: 
The description for the brick ports seems out of date and unclear. I have had two customers now have misconfigured firewalls because they didn't understand the requirements for the brick port range.

Suggestions for improvement: 
Change the description for the 49152 - 49251 range to something like:

Each brick for every volume on the host requires its own port for communications with GlusterFS clients. For each brick, one port will be used starting from 49152. Sizing must be considered for the expected maximum of concurrent volumes to determine what the exact range of ports should be.

Comment 3 Vijay Avuthu 2018-08-30 10:51:42 UTC

Looks Good.

Changing status to Verified.