[Avocado-devel] Heads-up: dropping Python 2.6 support

[Cleber Rosa]

On 02/07/2017 09:53 AM, Andrei Stepanov wrote:
> It seems that I can install: Avocado LTS using virtualenv + avocado-vt
> from github as a plugin.
> 
> avocado shows tp-qemu tests.
> 
> My steps are:
> 
> 1. Enable RHEL optional repo.
> 2. yum install libvirt libvirt-devel xz-devel libffi-devel python-devel
> openssl-devel openssl-devel "@Development tools" 
> 3. python get-pip.py --user
> 4. ./.local/bin/pip install --user virtualenv
> 5. ./.local/bin/virtualenv a1
> 6. . ./a1/bin/activate
> 7. pip install -r
> https://raw.githubusercontent.com/avocado-framework/avocado/36lts/requirements.txt
> 8. pip install 'avocado-framework==36.0'
> 9. pip install aexpect netaddr autotest
> 10. pip install -e
> "git+git://github.com/avocado-framework/avocado-vt#egg=avocado-plugins-vt <http://github.com/avocado-framework/avocado-vt#egg=avocado-plugins-vt>"
> 11. yum install yum install p7zip p7zip-plugins  # From EPEL  (can we
> get away from p7zip ?)
> 12. yum install qemu-kvm qemu-kvm-tools
> 13. avocado vt-bootstrap --vt-no-downloads
> 14. avocado list
> 
> How do you think, is this right approach to use avocado + avocado-vt  on
> RHEL 6.x + RHEL 7.x?
> 
> 

If it works (as you verified), then it's definitely (one) correct
deployment scenario.

If you find minor changes that can greatly improve deployment (such as
changes to requirements.txt), we can consider them "installation bugs"
and include them in future LTS releases.

- Cleber.

> On Tue, Feb 7, 2017 at 2:41 PM, Cleber Rosa <crosa at redhat.com
> <mailto:crosa at redhat.com>> wrote:
> 
> 
> 
>     On 02/07/2017 08:34 AM, Andrei Stepanov wrote:
>     >
>     >
>     > On Tue, Feb 7, 2017 at 2:20 PM, Cleber Rosa <crosa at redhat.com <mailto:crosa at redhat.com>
>     > <mailto:crosa at redhat.com <mailto:crosa at redhat.com>>> wrote:
>     >
>     >
>     >
>     >
>     >     Andrei,
>     >
>     >     Running a command such as:
>     >
>     >     pip install -r
>     >     https://raw.githubusercontent.com/avocado-framework/avocado/36lts/requirements.txt
>     <https://raw.githubusercontent.com/avocado-framework/avocado/36lts/requirements.txt>
>     >     <https://raw.githubusercontent.com/avocado-framework/avocado/36lts/requirements.txt
>     <https://raw.githubusercontent.com/avocado-framework/avocado/36lts/requirements.txt>>
>     >
>     >     Would have probably saved you a lot of this hassle.  This is documented
>     >     here:
>     >
>     >     http://avocado-framework.readthedocs.io/en/45.0/GetStartedGuide.html#installing-from-standard-python-tools
>     <http://avocado-framework.readthedocs.io/en/45.0/GetStartedGuide.html#installing-from-standard-python-tools>
>     >     <http://avocado-framework.readthedocs.io/en/45.0/GetStartedGuide.html#installing-from-standard-python-tools
>     <http://avocado-framework.readthedocs.io/en/45.0/GetStartedGuide.html#installing-from-standard-python-tools>>
>     >
>     >
>     >
>     >
>     > Can I ask why we do not specify required packages for pip?
>     > http://python-packaging.readthedocs.io/en/latest/dependencies.html
>     <http://python-packaging.readthedocs.io/en/latest/dependencies.html>
>     >
> 
>     We do specify the most basic requirements (stevedore) on newer versions,
>     it did not make into 36lts though.  We can still improve it and release
>     a new 36.x version.
> 
>     But, even with `install_requires`, some older versions of setuptools do
>     not allow versions to be specified there, which would cause breakage.
> 
>     Then, there's the question of too many deps required by some plugins,
>     such as remote (requires fabric), vm (requires libvirt).  We decided to
>     keep the list short and plugins just won't work without the extra deps.
> 
>     You may have noticed that we're working on splitting those plugins that
>     bring extra deps out of the "core" of Avocado:
> 
>     https://github.com/avocado-framework/avocado/pull/1751
>     <https://github.com/avocado-framework/avocado/pull/1751>
> 
>     > It would be fine if next command install all dependency automatically:
>     > pip install 'avocado-framework==36.0'
>     >
>     >
> 
>     It *would* be awesome.  But as you might imagine, it is not *that*
>     simple.  Putting a `install_requires` and releasing a new 36.x (36.4
>     now) would be the first big improvement IMHO.
> 
>     --
>     Cleber Rosa
>     [ Sr Software Engineer - Virtualization Team - Red Hat ]
>     [ Avocado Test Framework - avocado-framework.github.io
>     <http://avocado-framework.github.io> ]
> 
> 

-- 
Cleber Rosa
[ Sr Software Engineer - Virtualization Team - Red Hat ]
[ Avocado Test Framework - avocado-framework.github.io ]

-------------- 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/20170207/fe693b8c/attachment.sig>