<div dir="ltr"><div dir="ltr"><div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Mon, Nov 5, 2018 at 8:43 AM Sankarshan Mukhopadhyay <<a href="mailto:sankarshan.mukhopadhyay@gmail.com">sankarshan.mukhopadhyay@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, Nov 5, 2018 at 8:35 AM Atin Mukherjee <<a href="mailto:amukherj@redhat.com" target="_blank">amukherj@redhat.com</a>> wrote:<br>
><br>
> Thank you Rahul for the report. This does help to keep community up to date on the effort being put up here and understand where the things stand. Some comments inline.<br>
><br>
> On Sun, Nov 4, 2018 at 8:01 PM Rahul Hinduja <<a href="mailto:rhinduja@redhat.com" target="_blank">rhinduja@redhat.com</a>> wrote:<br>
>><br>
>> Hello,<br>
>><br>
>> Over past few weeks, few folks are engaged in integrating gd2 with existing glusto infrastructure/cases. This email is an attempt to provide the high level view of the work that's done so far and next.<br>
>><br>
>> Whats Done.<br>
>><br>
>> Libraries incorporated / under review:<br>
>><br>
>> Gluster Base Class and setup.py file required to read config file and install all the packages<br>
>> Exception and lib-utils file required for all basic test cases<br>
>> Common rest methods(Post, Get, Delete), to handle rest api’s<br>
>> Peer management libraries<br>
>> Basic Volume management libraries<br>
>> Basic Snapshot libraries<br>
>> Self-heal libraries<br>
>> Glusterd init<br>
>> Mount operations<br>
>> Device operations<br>
>><br>
>> Note: I request you all to provide review comments on the libraries that are submitted. Over this week, Akarsha and Vaibhavi will try to get the review comments incorporated and to get these libraries to closure.<br>
>><br>
>> Where is the repo?<br>
>><br>
>> [1] <a href="https://review.gluster.org/#/q/project:glusto-libs" rel="noreferrer" target="_blank">https://review.gluster.org/#/q/project:glusto-libs</a><br>
>><br>
>> Are we able to consume gd1 cases into gd2?<br>
>><br>
>> We tried POC to run glusterd and snapshot test cases (one-by-one) via modified automation and libraries. Following are the highlights:<br>
>><br>
>> We were able to run 20 gd1 cases out of which 8 passed and 12 failed.<br>
>> We were able to run 11 snapshot cases out of which 7 passed and 4 failed.<br>
>><br>
>> Reason for failures:<br>
>><br>
>> Because of different volume options with gd1/gd2<br>
><br>
> Just to clarify here, we have an open GD2 issue <a href="https://github.com/gluster/glusterd2/issues/739" rel="noreferrer" target="_blank">https://github.com/gluster/glusterd2/issues/739</a> which is being worked on and that should help us to achieve this backward compatibility.<br>
>><br>
>> Due to different error or output format between gd1/gd2<br>
><br>
><br>
> We need to move towards parsing error codes than the error messages. I'm aware that with GD1/CLI such infra was missing, but now that GD2 offers specific error codes, all command failures need to be parsed through error/ret codes in GD2. I believe the library/tests need to be modified accordingly to cater to this need to handle both GD1/GD2 based failures.<br>
><br>
>> For more detail which test cases is passed or failed and reasons for the failures [2]<br>
>><br>
>> [2] <a href="https://docs.google.com/spreadsheets/d/1O9JXQ2IgRIg5uZjCacybk3BMIjMmMeZsiv3-x_RTHWg/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/spreadsheets/d/1O9JXQ2IgRIg5uZjCacybk3BMIjMmMeZsiv3-x_RTHWg/edit?usp=sharing</a><br>
>><br>
<br>
Do these failures require bugs or, issues to track the resolution?<br></blockquote><div><br></div><div>We are going to use github [1] to track these issues. Libraries that were identified missing from the above exercises are now captured as an issue [2].<br></div><div><br>[1]: <a href="https://github.com/gluster/glusto-libs/issues">https://github.com/gluster/glusto-libs/issues</a><br>[2]: <a href="https://github.com/gluster/glusto-libs/issues/1">https://github.com/gluster/glusto-libs/issues/1</a><br><br></div><div>Regards,<br></div><div>Rahul<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
>> For more information/collaboration, please reach-out to:<br>
>><br>
>> Shrivaibavi Raghaventhiran (<a href="mailto:sraghave@redhat.com" target="_blank">sraghave@redhat.com</a>)<br>
>> Akarsha Rai (<a href="mailto:akrai@redhat.com" target="_blank">akrai@redhat.com</a>)<br>
>> Rahul Hinduja (<a href="mailto:rhinduja@redhat.com" target="_blank">rhinduja@redhat.com</a>)<br>
>><br>
<br>
Should we not be using<br>
<<a href="https://lists.gluster.org/mailman/listinfo/automated-testing" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/automated-testing</a>> for<br>
these conversations as well?</blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-devel</a></blockquote></div></div></div></div>