[Avocado-devel] [RFC v3]: Avocado maintainability and integration with avocado-vt

[Cleber Rosa]

On 04/20/2017 07:06 AM, Andrei Stepanov wrote:
> Hello.
> 
> Sounds good.
> I would add a small note.
> QE teams tend to run their tests against old RHEL (7.0/7.1/7.3)
> versions as well.
> Maybe this somehow correct your roadmap.
> My point is to stay away from useless dependencies.
> Ideally Avocado should run on RHEL7.0+official repo / RHEL 7.1 +
> official repo / etc....
> Problem with EPEL is: EPEL can be installed only on the latest .z stream.
> For example, if you have: EPEL + RHEL7.0 this is no more RHEL 7.0.
> Actually you cannot update RHEL7.0 with EPEL.
> It must be the latest RHEL7.x.z.
> Now we use python-virtenv+pypi to overcome this.
> 

Hi Andrei,

This is a very valid point indeed.  We've made things a little better by
moving a lot of the optional plugins outside the base package.

AFAIK, the base (python-)avocado package on EL7 requires EPEL only
because of (python-)stevedore.  I believe this can only be addressed by
requesting this extra package to be added to EL7 (even if it's only on
newer releases).

But this actually brings a question: is EL7 + Avocado RPM from official
repo, still RHEL7?  I mean, from a QE perspective, is this acceptable?
If not, the only real solution I see is also adding Avocado to EL7.

Thanks,

-- 
Cleber Rosa
[ Sr Software Engineer - Virtualization Team - Red Hat ]
[ Avocado Test Framework - avocado-framework.github.io ]
[  7ABB 96EB 8B46 B94D 5E0F  E9BB 657E 8D33 A5F2 09F3  ]

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/avocado-devel/attachments/20170426/9342700d/attachment.sig>