[Avocado-devel] Do we need a copy of tp-qemu/tp-avocado for avocado?

[Wei, Jiangang]

Hi, 

Thanks for your reply.

On Fri, 2016-05-06 at 10:00 -0300, Ademar Reis wrote:
> On Tue, May 03, 2016 at 04:33:56AM +0000, Wei, Jiangang wrote:
> > Hi all,
> > 
> > There're some arguments about the compatibility of test providers with
> > autotest
> >  since virttest shift to avocado-vt.  
> > 
> > Some cases of tp-qemu/tp-libvirt needs autotest's common functions.
> > Now avocado also supports these common functions (not all).
> > (avocado-vt still need autotest，we can find clue in requirements.txt）
> 
> That's correct. There's a one-direction dependency. Given
> avocado-vt could be described as a compatibility module (plugin)
> in Avocado to support "autotest-based virt-tests".
> 
> > 
> > Someone supports replacing the common function of autotest with
> > avocado's. 
> > In the long term, it's right.
> > But there're a lot of people who still uses tp-qemu with autotest.
> > and recommended by the Qemu community .
> 
> Why do you say Autotest is recommended by the QEMU community? We
> would like to change this perception, if it still exists.
You can refer to Qemu and KVM ‘s official website.

http://wiki.qemu.org/Contribute/KVMAutotestInstallfest
http://www.linux-kvm.org/page/KVM-Autotest
> 
> > 
> > Besides above,
> > The tp-qemu is still kept in autotest main page.【autotest/tp-qemu】,
> > and it hasn't been *definitely* declared to shift to avocado now.
> 
> That's probably a mistake. Although tp-* repositories can live
> anywhere, once virt-test was declared deprecated in favor of
> avocado-vt, tp-* should have been moved as well.
> 
> > 
> > So I suggest to copy tp-libvirt/tp-qemu to the avocado organization and
> > No longer accept new testcase，but bugfix.
> 
> I don't understand the motivation for accepting bugfixes. Just
> like we did with virt-test, the autotest version of tp-* should
> be considered deprecated (or read-only, kept there for historical
> purposes).
Yes, Freezing tp-* is OK.

> But as open source components, people should be free to maintain
> the project if there's interest.
> 
> > 
> > so that, We can concentrate on maintaining them based on avocado, 
> > and develop new test cases on it.
> > 
> > what about this proposal？
> 
> I support the idea. My suggestion is that tp-* get moved to
> under the avocado-umbrella and the autotest/tp-* reset to the
> commit from when virt-test was declared deprecated. This way we
> have two copies:
>  
>   - autotest/virt-test, autotest/tp-*: frozen in time, considered
>     deprecated, no risk of avocado-related changes getting merged
>     there.
> 
>   - avocado/avocado-vt, tp-*: newer version, using avocado
>     infrastructure.
I agree with you.
> 
> Thanks.
>    - Ademar
>