<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Mar 13, 2019 at 5:08 AM Sankarshan Mukhopadhyay <<a href="mailto:sankarshan.mukhopadhyay@gmail.com" target="_blank">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 Wed, Mar 13, 2019 at 3:03 PM Yaniv Kaul <<a href="mailto:ykaul@redhat.com" target="_blank">ykaul@redhat.com</a>> wrote:<br>
> On Wed, Mar 13, 2019, 3:53 AM Sankarshan Mukhopadhyay <<a href="mailto:sankarshan.mukhopadhyay@gmail.com" target="_blank">sankarshan.mukhopadhyay@gmail.com</a>> wrote:<br>
>><br>
>> What I am essentially looking to understand is whether there are<br>
>> regular Glusto runs and whether the tests receive refreshes. However,<br>
>> if there is no available Glusto service running upstream - that is a<br>
>> whole new conversation.<br>
><br>
><br>
> I'm* still trying to get it running properly on my simple Vagrant+Ansible setup[1].<br>
> Right now I'm installing Gluster + Glusto + creating bricks, pool and a volume in ~3m on my latop.<br>
><br>
<br></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
This is good. I think my original question was to the maintainer(s) of<br>
Glusto along with the individuals involved in the automated testing<br>
part of Gluster to understand the challenges in deploying this for the<br>
project.<br>
<br>
> Once I do get it fully working, we'll get to make it work faster, clean it up and and see how can we get code coverage.<br>
><br>
> Unless there's an alternative to the whole framework that I'm not aware of?<br>
<br>
I haven't read anything to this effect on any list.<br>
<br></blockquote><div><br></div><div><div>This is cool. I haven't had a chance to give it a run on my laptop, but it looked good.<br></div><div>Are you running into issues with Glusto, glusterlibs, and/or Glusto-tests?</div></div><div><br></div><div>I was using the glusto-tests container to run tests locally and for BVT in the lab.</div><div>I was running against lab VMs, so looking forward to giving the vagrant piece a go.</div><div><br></div><div>By upstream service are we talking about the Jenkins in the CentOS environment, etc?</div><div><a class="gmail_plusreply" id="m_-5406023252844920932plusReplyChip-1" href="mailto:vavuthu@redhat.com" target="_blank">@Vijay Bhaskar Reddy Avuthu</a> <a class="gmail_plusreply" id="m_-5406023252844920932plusReplyChip-2" href="mailto:akrai@redhat.com" target="_blank">@Akarsha Rai</a> any insight?<br></div><div><br></div><div>Cheers,</div><div>Jonathan<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">
> Surely for most of the positive paths, we can (and perhaps should) use the the Gluster Ansible modules.<br>
> Y.<br>
><br>
> [1] <a href="https://github.com/mykaul/vg" rel="noreferrer" target="_blank">https://github.com/mykaul/vg</a><br>
> * with an intern's help.<br>
_______________________________________________<br>
automated-testing mailing list<br>
<a href="mailto:automated-testing@gluster.org" target="_blank">automated-testing@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/automated-testing" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/automated-testing</a><br>
</blockquote></div></div>