test: add a test to enable and test rdma connect

[dsharma-dc]

• Added a simple test to create and publish a nexus. Connect it over rdma.
• The connect API is modified to take transport parameter.
• The test automatically detects a suitable interface to create a soft-RDMA device, creates it and deletes it at the end of the test.

[dsharma-dc]

The changes for composer dependencies are here: openebs/mayastor-dependencies#96

[dsharma-dc]

bors try

[bors-openebs-mayastor]

try

Build failed:

• continuous-integration/jenkins/branch

[dsharma-dc]

bors try

[bors-openebs-mayastor]

try

Build failed:

• continuous-integration/jenkins/branch

[dsharma-dc]

CI machines have been setup with required modules now.

bors try

[bors-openebs-mayastor]

try

Merge conflict.

[pchandra19]

bors try

[bors-openebs-mayastor]

try

Build failed:

• continuous-integration/jenkins/branch

[pchandra19]

bors try

[bors-openebs-mayastor]

try

Build failed:

• continuous-integration/jenkins/branch

[dsharma-dc]

I tried running the test manually and I notice the issue is that rxe rdma device is not getting correct IP address of the chosen interface assigned. This is the issue that we see when overlay network is present. As a result rdma listen is failing. I'll mark the test as #ignore for now and merge with that.

IP assigned to rdma device on eth0 (compare only last byte of dot decimal notation)
io-engine-rxe0 1 1 0000:0000:0000:0000:0000:ffff:87b5:b781 111.222.333.129 v2 eth0

Actual IP of eth0 from ifconfig

eth0: flags=xxxx<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 111.222.333.161  netmask 255.255.255.255  broadcast 0.0.0.0

[dsharma-dc]

bors try

[bors-openebs-mayastor]

try

Build succeeded:

• continuous-integration/jenkins/branch

[dsharma-dc]

bors merge

[bors-openebs-mayastor]

Build succeeded:

• continuous-integration/jenkins/branch