[automated-testing] Supporting GD2 & GD1 in glusto-tests

Nigel Babu nigelb at redhat.com
Thu Jul 5 09:28:55 UTC 2018


I don't think we're in a place to branch at the moment.

The right way to branch would be to have the libraries split off from the
glusto-tests repo into its own independent repo that we can version. Then
we'd have a version of the library that works for GD2 and a version of the
library that works for GD1. The tests should continue to remain the same.
If the tests need changing, that means an incompatibility has slipped in.
However, the tests that are critical for GCS should be marked with a PyTest
flag so we can only run those tests when we want to. This is way more
tricky than it sounds, because not all volume types are supported in GCS.






On Wed, Jul 4, 2018 at 5:09 PM Rahul Hinduja <rhinduja at redhat.com> wrote:

>
>
> On Wed 4 Jul, 2018, 5:04 PM Vijay Bhaskar Reddy Avuthu, <
> vavuthu at redhat.com> wrote:
>
>> Hi All,
>>
>> This thread is regarding the support of GD2 with "glusto-tests".
>>
>> Since we are fastly moving towards GCS/RHOCS which mainly build on GD2,
>> we need to work towards supporting both GD2 and GD1.
>>
>> Here are few thoughts:
>>
>> 1) Identify GD2 is running or not, then according we need modify
>> libraries/tests to support latest command
>>
>> eg:
>>
>> new cmd :
>>
>> glustercli volume start <testvol>
>> or
>> curl -X POST http://192.168.56.101:24007/v1/volumes/testvol/start
>>
>>
>> In lib below is the modification snippet:
>>
>> if glusterd2_enable():
>>     glustercli volume start <testvol>
>> else:
>>     gluster volume start <testvol>
>>
>> For above approach, needs lot of re-work.
>>
>> 2) Versioning ?
>>
>> not sure how versioning works
>>
>> Any other thoughts whats is the best way to support both GD2 and GD1 ?
>>
>
> Gil had suggested branching and I echo that.
>
>
>> Regards,
>> Vijay A
>>
>

-- 
nigelb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/automated-testing/attachments/20180705/26eb5d63/attachment.html>


More information about the automated-testing mailing list