Re: [Gluster-users] [Gluster-devel] Announcing release 3.11 : Scope, schedule and feature tracking

2017-03-03 Thread Ravishankar N
On 03/03/2017 07:23 PM, Shyam wrote: On 03/03/2017 06:44 AM, Prashanth Pai wrote: On 02/28/2017 08:47 PM, Shyam wrote: We should be transitioning to using github for feature reporting and tracking, more fully from this release. So once again, if there exists any confusion on that front,

Re: [Gluster-users] [Gluster-devel] Announcing release 3.11 : Scope, schedule and feature tracking

2017-03-03 Thread Shyam
On 03/03/2017 06:44 AM, Prashanth Pai wrote: On 02/28/2017 08:47 PM, Shyam wrote: We should be transitioning to using github for feature reporting and tracking, more fully from this release. So once again, if there exists any confusion on that front, reach out to the lists for clarification.

Re: [Gluster-users] [Gluster-devel] Announcing release 3.11 : Scope, schedule and feature tracking

2017-03-03 Thread Prashanth Pai
> On 02/28/2017 08:47 PM, Shyam wrote: > > We should be transitioning to using github for feature reporting and > > tracking, more fully from this release. So once again, if there exists > > any confusion on that front, reach out to the lists for clarification. > > I see that there was a

Re: [Gluster-users] [ovirt-users] Hot to force glusterfs to use RDMA?

2017-03-03 Thread Arman Khalatyan
I think there are some bug in the vdsmd checks; 2017-03-03 11:15:42,413 ERROR (jsonrpc/7) [storage.HSM] Could not connect to storageServer (hsm:2391) Traceback (most recent call last): File "/usr/share/vdsm/storage/hsm.py", line 2388, in connectStorageServer conObj.connect() File

Re: [Gluster-users] Announcing release 3.11 : Scope, schedule and feature tracking

2017-03-03 Thread Ravishankar N
On 02/28/2017 08:47 PM, Shyam wrote: We should be transitioning to using github for feature reporting and tracking, more fully from this release. So once again, if there exists any confusion on that front, reach out to the lists for clarification. I see that there was a discussion on this on

Re: [Gluster-users] [ovirt-users] Hot to force glusterfs to use RDMA?

2017-03-03 Thread Arman Khalatyan
Thank you all for the nice hints. Somehow my host was not able to access the userspace RDMA, after installing: yum install -y libmlx4.x86_64 I can mount: /usr/bin/mount -t glusterfs -o backup-volfile-servers=10.10.10.44:10.10.10.42:10.10.10.41,transport=rdma 10.10.10.44:/GluReplica /mnt

Re: [Gluster-users] Old bricks from deleted volumes

2017-03-03 Thread Atin Mukherjee
On Fri, Mar 3, 2017 at 12:43 PM, J.R. W wrote: > Hello, > > I have bricks were there volume doesn't exists anymore. Is there a way I > can add these bricks to a new volume? > > Essentially - > > gluster volume create new-volume host1:/export/brick1 >

Re: [Gluster-users] [ovirt-users] Hot to force glusterfs to use RDMA?

2017-03-03 Thread Deepak Naidu
>> As you can see from my previous email that the RDMA connection tested with >> qperf. I think you have wrong command. Your testing TCP & not RDMA. Also check if you have RDMA & IB modules loaded on your hosts. root@clei26 ~]# qperf clei22.vib tcp_bw tcp_lat tcp_bw: bw = 475 MB/sec

Re: [Gluster-users] [ovirt-users] Hot to force glusterfs to use RDMA?

2017-03-03 Thread Mohammed Rafi K C
Hi Arman, On 03/03/2017 12:27 PM, Arman Khalatyan wrote: > Dear Deepak, thank you for the hints, which gluster are you using? > As you can see from my previous email that the RDMA connection tested > with qperf. It is working as expected. In my case the clients are > servers as well, they are