<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 23, 2016 at 10:54 PM, Nir Soffer <span dir="ltr"><<a href="mailto:nsoffer@redhat.com" target="_blank">nsoffer@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="">On Tue, Feb 23, 2016 at 6:30 PM, Yaniv Bronheim <span dir="ltr"><<a href="mailto:ybronhei@redhat.com" target="_blank">ybronhei@redhat.com</a>></span> wrote:<br></span><span class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>(Nir, Adam, YanivB, Dan, Milan, Piotr, Francesco, Martin Polednik, Edward)</div><div><br></div><div>- Some of us started to work on refactoring for python3, basic file movements and improving testings </div><div><br></div><div> - We added functional tests to check-merged automation script - currently, for some reason, it doesn't run tests that require root. I'm on it.</div><div><br></div><div> - if anyone know that their functional tests work good please add them to the list </div><div>so they will run each merge</div><div><br></div><div> - moving code from supervdsmServer to supervdsm_api - follow <a href="https://gerrit.ovirt.org/53496" target="_blank">https://gerrit.ovirt.org/53496</a> and move also virt, storage and sla part</div><div><br></div><div> - Nir says to use the weekly contact from storage team to help with verification about storage code changes- I'll try to reach them next week to test direct LUN</div></div></blockquote><div><br></div></span><div>Tal should know who is the qe contact</div></div></div></div></blockquote><div><br></div><div>can you publish it somewhere or send mail to the devels when you change shifts? </div><div>I struggle with testing specific rpms with ovirt-system-tests currently - it requires some tweaks there and I prefer to trust your verification - I moved blkid, parted_utils, hostdev, alignmentScan - how do you suggest to approve that it didn't break anything (<a href="https://gerrit.ovirt.org/#/c/53897/4">https://gerrit.ovirt.org/#/c/53897/4</a>) </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><br></div><div> - I also wanted to use lago basic_suite (ovirt-system-tests) to run full flow from specific vdsm commit - but the infrastructure for that requires many manual steps and its not easy as I expected it to be.</div><div><br></div><div>- moving code from vdsm dir (/usr/share/vdsm/) to site-packages/vdsm (by moving them to lib/vdsm) - this is required to avoid relative imports which are not allowed in python3 - storage dir is the main gap we currently have.</div><div><br></div><div><div>- python-modernize - Dan uses it for network tests dir and encourage us to start running it for our parts</div></div></div></blockquote><div><br></div></span><div>Where is this tool?</div></div></div></div></blockquote><div><br></div><div> dnf install python-modernize</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><br></div><div>- there are some schema changes, mostly removal parts that Piotr posted as part of converting to yaml structure. this code needs to be reviewed<br></div><div><div>- Nir asks to keep the current API order instead of sorting by names </div><div>- Nir concerns about yaml notation looks for a list with single element</div></div></div></div></blockquote><div><br></div></span><div>Whis is less nice than the previous notation:</div><div><br></div><div>new: </div><br> - name: pathlist<br> type:</div><div class="gmail_quote"> - *IscsiSessionInfo<div> <br></div><div>old:</div><div><br></div><div><div> 'pathlist': ['IscsiSessionInfo'],<br></div><div><br></div><div>I don't see how to make this better.</div></div><span class=""><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div>- split the yaml schema to several files is complex but nir asks to see if its possible</div><div><br></div><div>- storage team mainly works hard on SDM patches</div><div><br></div><div>- Edward works on splitting network tests between unit tests and integration tests which do environment setup changes</div><div><br></div><div>- we currently don't run the slow test automatically</div><div>- we might want more "tags" for tests such as SlowTests, StressTests</div></div></div></div></blockquote><div><br></div></span><div>We can solve this issue by marking tests as slowtest, but we better use more</div><div>specific tags such as "integration", for tests that depend on the environment, and </div><div>"privileged" for tests that requires root.</div></div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div><br></div><div>And the most important issue - vdsm for ovirt 4.0 will keep only 3.6 backward compatibility - if you don't agree with that statement, please say why ... but as far as we see it, this is the direction and we already removing 3.5 stuff.</div></div></div></div></blockquote><div><br></div></span><div>+2 from storage side</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div><br></div><div>Thanks all for participating,</div></div></div></div></blockquote><div><br></div><div>Thanks for taking the notes!</div><span class=""><font color="#888888"><div><br></div><div>Nir</div><div><br></div></font></span></div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><span style="font-size:12.8px"><b>Yaniv Bronhaim.</b></span><br></div></div></div></div></div>
</div></div>