Bug 980541

Summary: GlusterFS testing framework needs rdma support added
Product: [Community] GlusterFS Reporter: Justin Clift <jclift>
Component: unclassifiedAssignee: bugs <bugs>
Status: CLOSED EOL QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: pre-releaseCC: bugs, gluster-bugs, kwade
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-22 15:40:20 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:

Description Justin Clift 2013-07-02 16:20:26 UTC
Description of problem:

  At present, the GlusterFS testing framework uses tcp for all tests, as there
  is no "protocol $PROTOCOL" line in any of the volume creation commands.

  We should add a protocol specifier to the volume creation commands in our
  testing framework, which would enable us to test RDMA as well.


Version-Release number of selected component (if applicable):

  Upstream GlusterFS git, master branch as of Tue 2nd July 2013.


Additional info:

  Initial support should be very easy to add without breaking the existing
  testing framework.

  Likely starting by adding the PROTOCOL definition to tests/include.rc:

    PROTOCOL=${PROTOCOL:=tcp};    # transport protocol to use

  Then adding "protocol $PROTOCOL" to the volume creation commands in:

    tests/basic/*.t

  Adding "protocol $PROTOCOL" to other tests could be done at a future point.

Comment 1 Justin Clift 2013-07-02 19:25:36 UTC
s/protocol $PROTOCOL/transport $PROTOCOL/

Comment 2 Anand Avati 2013-07-02 21:50:25 UTC
REVIEW: http://review.gluster.org/5275 (Add transport keyword and variable to our test framework) posted (#1) for review on master by Justin Clift (jclift)

Comment 4 Kaleb KEITHLEY 2015-10-22 15:40:20 UTC
pre-release version is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.