Bug 1455591 - [Docs) Add additional clarification regarding network and latency requirements
Summary: [Docs) Add additional clarification regarding network and latency requirements
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: Documentation
Version: rhgs-3.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Laura Bailey
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: Gluster-HC-2
TreeView+ depends on / blocked
 
Reported: 2017-05-25 14:29 UTC by khartsoe@redhat.com
Modified: 2017-11-17 05:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-29 04:11:25 UTC


Attachments (Terms of Use)

Description khartsoe@redhat.com 2017-05-25 14:29:36 UTC
Document URL: 

Section Number and Name: 
(Sec 3.1 Physical Machines) https://doc-stage.usersys.
 redhat.com/documentation/en-us/red_hat_gluster_storage/3.
 2/html-single/deploying_red_hats_hyper-converged_infrastructure/#physical_
 machines

(Sec 3.3 Networking) https://doc-stage.usersys.
 redhat.com/documentation/en-us/red_hat_gluster_storage/3.
 2/html-single/deploying_red_hats_hyper-converged_
 infrastructure/#networking

Describe the issue: 
Need additional clarification regarding network and latency requirements

Suggestions for improvement: 
Please add clarification of the following requirements:

(1) Two network interfaces are required:
 -one front-end network for setting the ovirtmgmt bridge
 -one back-end network for probing gluster peers and setting up the volume

Two separate networks are required so that client and management traffic in
the cluster are separated.
- client and management traffic or data and management traffic ?

Red Hat recommends 10Gbps networks for best performance.
- This recommendation is for the backend network  (i.e one with storage and
migration traffic)

(2)Also, we need to call out that the IP addresses assigned to the front-end
network needs to be from same subnet. 

(3) Similarly for back-end network, all IP addresses need to from same subnet which is different from the front-end
network's subnet (Apparently this was not obvious to customer)



(4) Latency:
 RHGS requires a minimum latency of < 5ms between between the three machines


Additional information:

Comment 5 SATHEESARAN 2017-06-20 12:57:06 UTC
Verified with the docs that the requirement as stated in comment0 is available with the LIVE docs

Comment 6 Laura Bailey 2017-08-29 04:11:25 UTC
Fixed in RHGS 3.3 documentation.


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