<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">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><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc 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><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><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>- 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><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><div>If a customer has 3.5 level cluster with all hosts on RHEL 7, why would we break compatibility? Need to understand the cost here.</div><div>The very least is to allow live migration .</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"><div dir="ltr"><div><div><div><br></div><div>Thanks all for participating,</div><span class="HOEnZb"><font color="#888888"><div><br></div>-- <br><div><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>
</font></span></div></div></div>
<br>_______________________________________________<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/mailman/listinfo/devel</a><br></blockquote></div><br></div></div>