<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 5, 2018 at 3:01 PM, Yedidyah Bar David <span dir="ltr"><<a href="mailto:didi@redhat.com" target="_blank">didi@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
Recently I have been pushing various patches to OST in order to verify<br>
specific bugs/fixes I was working on, using them with the "manual"<br>
jenkins job but with no immediate intention to get them merged. Main<br>
reason is that it's not clear what's the best approach to get such<br>
tests merged. Do we want a new suite? How often does it run? How long<br>
does it take? Do we have enough resources? etc.<br></blockquote><div><br></div><div>I'll answer generally, since specifically for each test we'll need to see.</div><div>The guidelines that I have (in my head, not written down anywhere) are really:</div><div>1. Be efficient in resource - HW mainly. My guideline is quite simple - can it run on my laptop (8GB of RAM).</div><div>Not everything can fit of course on my laptop (the performance suite, the upcoming OpenShift on oVirt suite, etc.), but I try.</div><div>2. Be quick - whatever we can test in parallel to other tests, is much preferred. We have quite a bit of 'dead time' between tests, we need to use them.</div><div>3. Bend the rules, but don't cheat - I move the yum cache repo to /dev/shm, etc. - to make things quicker, but I don't cheat and install deps. ahead of time, etc.</div><div>4. Most suites do not run too often (several times a day) - I think it's OK to add to those that run once a day or so.</div><div>5. Strive for others (QE!) to contribute to the suite. The more we can collaborate, the better.</div><div>6. Generally, we have enough gaps in our positive tests, that I rather not introduce negative tests.</div><div>7. Whatever we can do in order to ensure QE does not get a dead-on-arrival or broken functionality build - the better.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Do we have plans re this? Bugs/tickets/etc.?<br></blockquote><div><br></div><div>Bugzilla, but I did not see anything there for quite some time.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Do we want to do something?<br>
<br>
Specifically, do we want (eventually) many more suites? This seems<br>
unmanageable. A few suites, perhaps (also) using lago snapshots?<br>
Didn't try that myself, might be useful and relevant.<br>
<br>
Some examples:<br>
<a href="https://gerrit.ovirt.org/79203" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/79203</a><br>
<a href="https://gerrit.ovirt.org/79215" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/79215</a><br>
<a href="https://gerrit.ovirt.org/84813" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/84813</a><br>
<a href="https://gerrit.ovirt.org/88201" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/88201</a><br>
<a href="https://gerrit.ovirt.org/88234" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/88234</a><br>
<br>
And current one - this and the next ones in the stack:<br>
<a href="https://gerrit.ovirt.org/88331" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/88331</a></blockquote><div><br></div><div>Many of those change the default installation and test the 'interesting' combinations - which I think is great. </div><div>I'd be happy for a setup with custom '3rd party' certificate, Kerberos auth., ovirtmgmt on a VLAN interface, etc.</div><div>Y.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
Best regards,<br>
<span class="HOEnZb"><font color="#888888">--<br>
Didi<br>
______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/devel</a><br>
</font></span></blockquote></div><br></div></div>