Re: [Gluster-devel] Identifying tests to automate with Glusto

2017-10-31 Thread Raghavendra Gowdappa
"Kartik Burmee" > > Sent: Tuesday, October 31, 2017 2:26:25 PM > Subject: Re: [Gluster-devel] Identifying tests to automate with Glusto > > Hi DHT pundits, > > I was chatting with Karthik, and was thinking tests on 'rebalance' and > 'remove-bri

Re: [Gluster-devel] Identifying tests to automate with Glusto

2017-10-31 Thread Amar Tumballi
Hi DHT pundits, I was chatting with Karthik, and was thinking tests on 'rebalance' and 'remove-brick' may be well suited to be started on in glusto frame-work (mainly because it is applicable for all kind of volumes). Please help him to get started on the feature, and also he was keen to pick up

Re: [Gluster-devel] Identifying tests to automate with Glusto

2017-10-30 Thread Nigel Babu
> >> One of the missing part with existing .t tests in glusterd is the client >> and server compatibility with different op-versions. Off late we have seen >> most of the bugs. I think we’d need to write tests with clients running >> with different versions, heterogeneous servers ( in n to n-2 rang

Re: [Gluster-devel] Identifying tests to automate with Glusto

2017-10-30 Thread Shyam Ranganathan
On 10/30/2017 10:07 AM, Atin Mukherjee wrote: On Mon, 30 Oct 2017 at 19:32, Nigel Babu > wrote: Hello folks, One of the action items of the Testing BoF around Glusto is to start a discussion on the mailing list about specific scenarios that aren't cov

Re: [Gluster-devel] Identifying tests to automate with Glusto

2017-10-30 Thread Atin Mukherjee
On Mon, 30 Oct 2017 at 19:32, Nigel Babu wrote: > Hello folks, > > One of the action items of the Testing BoF around Glusto is to start a > discussion on the mailing list about specific scenarios that aren't covered > in our existing .t tests that need a proper cluster to test. I know Nithya > ha

[Gluster-devel] Identifying tests to automate with Glusto

2017-10-30 Thread Nigel Babu
Hello folks, One of the action items of the Testing BoF around Glusto is to start a discussion on the mailing list about specific scenarios that aren't covered in our existing .t tests that need a proper cluster to test. I know Nithya had one about rebalance where we don't have enough coverage wit