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

2017-02-07 Thread 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 
> "
> 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  > wrote:
> 
> 
> 
> On 02/07/2017 08:34 AM, Andrei Stepanov wrote:
> >
> >
> > On Tue, Feb 7, 2017 at 2:20 PM, Cleber Rosa  
> > >> wrote:
> >
> >
> >
> >
> > Andrei,
> >
> > Running a command such as:
> >
> > pip install -r
> > 
> 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
> 
> 
> > 
>  
> >
> >
> >
> >
> >
> > Can I ask why we do not specify required packages for pip?
> > 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
> 
> 
> > 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
>  ]
> 
> 

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



signature.asc
Description: OpenPGP digital signature

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

2017-02-07 Thread Andrei Stepanov 
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"
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?


On Tue, Feb 7, 2017 at 2:41 PM, Cleber Rosa  wrote:

>
>
> On 02/07/2017 08:34 AM, Andrei Stepanov wrote:
> >
> >
> > On Tue, Feb 7, 2017 at 2:20 PM, Cleber Rosa  > > wrote:
> >
> >
> >
> >
> > Andrei,
> >
> > Running a command such as:
> >
> > pip install -r
> > https://raw.githubusercontent.com/avocado-framework/avocado/
> 36lts/requirements.txt
> >  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
> >  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
> >
>
> 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
>
> > 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 ]
>
>

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

2017-02-07 Thread Cleber Rosa 


On 02/07/2017 08:34 AM, Andrei Stepanov wrote:
> 
> 
> On Tue, Feb 7, 2017 at 2:20 PM, Cleber Rosa  > wrote:
> 
> 
> 
> 
> Andrei,
> 
> Running a command such as:
> 
> pip install -r
> 
> 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
> 
> 
> 
> 
> 
> 
> Can I ask why we do not specify required packages for pip?
> 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

> 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 ]



signature.asc
Description: OpenPGP digital signature

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

2017-02-07 Thread Andrei Stepanov 
On Tue, Feb 7, 2017 at 2:20 PM, Cleber Rosa  wrote:

>
>
>
> Andrei,
>
> Running a command such as:
>
> pip install -r
> 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




Can I ask why we do not specify required packages for pip?
http://python-packaging.readthedocs.io/en/latest/dependencies.html

It would be fine if next command install all dependency automatically:
pip install 'avocado-framework==36.0'

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

2017-02-07 Thread Cleber Rosa 

On 02/07/2017 08:04 AM, Andrei Stepanov wrote:
> Hi.
> 
> Short report:   I am trying to install LTS 36 into virtualenv on RHEL6:
> 
> (avocado) [root@localhost ~]# pip install 'avocado-framework==36.0'
> DEPRECATION: Python 2.6 is no longer supported by the Python core team,
> please upgrade your Python. A future version of pip will drop support
> for Python 2.6
> Collecting avocado-framework==36.0
> /root/avocado/lib/python2.6/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:318:
> SNIMissingWarning: An HTTPS request has been made, but the SNI (Subject
> Name Indication) extension to TLS is not available on this platform.
> This may cause the server to present an incorrect TLS certificate, which
> can cause validation failures. You can upgrade to a newer version of
> Python to solve this. For more information, see
> https://urllib3.readthedocs.io/en/latest/security.html#snimissingwarning.
>   SNIMissingWarning
> /root/avocado/lib/python2.6/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:122:
> InsecurePlatformWarning: A true SSLContext object is not available. This
> prevents urllib3 from configuring SSL appropriately and may cause
> certain SSL connections to fail. You can upgrade to a newer version of
> Python to solve this. For more information, see
> https://urllib3.readthedocs.io/en/latest/security.html#insecureplatformwarning.
>   InsecurePlatformWarning
>   Downloading avocado-framework-36.0.tar.gz (714kB)
> 100% || 716kB 1.2MB/s 
> Complete output from command python setup.py egg_info:
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "/tmp/pip-build-ex9cI3/avocado-framework/setup.py", line 22,
> in 
> from avocado import VERSION
>   File "avocado/__init__.py", line 19, in 
> from avocado.core.job import main
>   File "avocado/core/job.py", line 33, in 
> from . import dispatcher
>   File "avocado/core/dispatcher.py", line 19, in 
> from stevedore import ExtensionManager
> ImportError: No module named stevedore
> 
> 
> Command "python setup.py egg_info" failed with error code 1 in
> /tmp/pip-build-ex9cI3/avocado-framework/
> 
> 
> Okay, install stevedore:
> 
> # pip install 'stevedore'
> ...
> Installing collected packages: pbr, stevedore
> Successfully installed pbr-1.10.0 stevedore-1.20.0
> 
> 
> Than I get next error:
> 
> 
> (avocado) [root@localhost ~]# pip install 'avocado-framework==36.0'
> DEPRECATION: Python 2.6 is no longer supported by the Python core team,
> please upgrade your Python. A future version of pip will drop support
> for Python 2.6
> Collecting avocado-framework==36.0
>   Using cached avocado-framework-36.0.tar.gz
> Complete output from command python setup.py egg_info:
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "/tmp/pip-build-EREmsk/avocado-framework/setup.py", line 22,
> in 
> from avocado import VERSION
>   File "avocado/__init__.py", line 19, in 
> from avocado.core.job import main
>   File "avocado/core/job.py", line 33, in 
> from . import dispatcher
>   File "avocado/core/dispatcher.py", line 19, in 
> from stevedore import ExtensionManager
>   File
> "/root/avocado/lib/python2.6/site-packages/stevedore/__init__.py", line
> 23, in 
> LOG.addHandler(logging.NullHandler())
> AttributeError: 'module' object has no attribute 'NullHandler'
> 
> 
> Command "python setup.py egg_info" failed with error code 1 in
> /tmp/pip-build-EREmsk/avocado-framework/
> 
> 
> Okay, downgrade stevedore:
> 
> 
> # pip install 'stevedore==1.2.0'
> 
> 
> Another error:
> 
> pip install 'avocado-framework==36.0'
> DEPRECATION: Python 2.6 is no longer supported by the Python core team,
> please upgrade your Python. A future version of pip will drop support
> for Python 2.6
> Collecting avocado-framework==36.0
>   Using cached avocado-framework-36.0.tar.gz
> Complete output from command python setup.py egg_info:
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "/tmp/pip-build-3f_bMj/avocado-framework/setup.py", line 22,
> in 
> from avocado import VERSION
>   File "avocado/__init__.py", line 19, in 
> from avocado.core.job import main
>   File "avocado/core/job.py", line 34, in 
> from . import runner
>   File "avocado/core/runner.py", line 28, in 
> from . import test
>   File "avocado/core/test.py", line 31, in 
> from . import multiplexer
>   File "avocado/core/multiplexer.py", line 27, in 
> from . import tree
>   File "avocado/core/tree.py", line 53, in 
> from . import output
>   File "avocado/core/output.py", line 30, in 
> import logutils
> ImportError: No module named logutils
> 
> 
> # pip install

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

2017-02-07 Thread Andrei Stepanov 
Hi.

Short report:   I am trying to install LTS 36 into virtualenv on RHEL6:

(avocado) [root@localhost ~]# pip install 'avocado-framework==36.0'
DEPRECATION: Python 2.6 is no longer supported by the Python core team,
please upgrade your Python. A future version of pip will drop support for
Python 2.6
Collecting avocado-framework==36.0
/root/avocado/lib/python2.6/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:318:
SNIMissingWarning: An HTTPS request has been made, but the SNI (Subject
Name Indication) extension to TLS is not available on this platform. This
may cause the server to present an incorrect TLS certificate, which can
cause validation failures. You can upgrade to a newer version of Python to
solve this. For more information, see
https://urllib3.readthedocs.io/en/latest/security.html#snimissingwarning.
  SNIMissingWarning
/root/avocado/lib/python2.6/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:122:
InsecurePlatformWarning: A true SSLContext object is not available. This
prevents urllib3 from configuring SSL appropriately and may cause certain
SSL connections to fail. You can upgrade to a newer version of Python to
solve this. For more information, see
https://urllib3.readthedocs.io/en/latest/security.html#insecureplatformwarning
.
  InsecurePlatformWarning
  Downloading avocado-framework-36.0.tar.gz (714kB)
100% || 716kB 1.2MB/s
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
  File "", line 1, in 
  File "/tmp/pip-build-ex9cI3/avocado-framework/setup.py", line 22, in

from avocado import VERSION
  File "avocado/__init__.py", line 19, in 
from avocado.core.job import main
  File "avocado/core/job.py", line 33, in 
from . import dispatcher
  File "avocado/core/dispatcher.py", line 19, in 
from stevedore import ExtensionManager
ImportError: No module named stevedore


Command "python setup.py egg_info" failed with error code 1 in
/tmp/pip-build-ex9cI3/avocado-framework/


Okay, install stevedore:

# pip install 'stevedore'
...
Installing collected packages: pbr, stevedore
Successfully installed pbr-1.10.0 stevedore-1.20.0


Than I get next error:


(avocado) [root@localhost ~]# pip install 'avocado-framework==36.0'
DEPRECATION: Python 2.6 is no longer supported by the Python core team,
please upgrade your Python. A future version of pip will drop support for
Python 2.6
Collecting avocado-framework==36.0
  Using cached avocado-framework-36.0.tar.gz
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
  File "", line 1, in 
  File "/tmp/pip-build-EREmsk/avocado-framework/setup.py", line 22, in

from avocado import VERSION
  File "avocado/__init__.py", line 19, in 
from avocado.core.job import main
  File "avocado/core/job.py", line 33, in 
from . import dispatcher
  File "avocado/core/dispatcher.py", line 19, in 
from stevedore import ExtensionManager
  File
"/root/avocado/lib/python2.6/site-packages/stevedore/__init__.py", line 23,
in 
LOG.addHandler(logging.NullHandler())
AttributeError: 'module' object has no attribute 'NullHandler'


Command "python setup.py egg_info" failed with error code 1 in
/tmp/pip-build-EREmsk/avocado-framework/


Okay, downgrade stevedore:


# pip install 'stevedore==1.2.0'


Another error:

pip install 'avocado-framework==36.0'
DEPRECATION: Python 2.6 is no longer supported by the Python core team,
please upgrade your Python. A future version of pip will drop support for
Python 2.6
Collecting avocado-framework==36.0
  Using cached avocado-framework-36.0.tar.gz
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
  File "", line 1, in 
  File "/tmp/pip-build-3f_bMj/avocado-framework/setup.py", line 22, in

from avocado import VERSION
  File "avocado/__init__.py", line 19, in 
from avocado.core.job import main
  File "avocado/core/job.py", line 34, in 
from . import runner
  File "avocado/core/runner.py", line 28, in 
from . import test
  File "avocado/core/test.py", line 31, in 
from . import multiplexer
  File "avocado/core/multiplexer.py", line 27, in 
from . import tree
  File "avocado/core/tree.py", line 53, in 
from . import output
  File "avocado/core/output.py", line 30, in 
import logutils
ImportError: No module named logutils


# pip install logutils

Another error:


# pip install 'avocado-framework==36.0'
DEPRECATION: Python 2.6 is no longer supported by the Python core team,
please upgrade your Python. A future version of pip will drop support for
Python 2.6
Collecting avocado-framework==36.0
  Using cached avocado-framework-36.0.tar.gz

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

2017-02-07 Thread Cleber Rosa 
On 02/07/2017 06:46 AM, Lucas Meneghel Rodrigues wrote:
> I'm not sure putting a file with references to a relatively independent
> plugin in the main avocado repo the correct thing to do. It's probably
> better to put a file with that summary in the avocado-vt repository instead.
> 

I think Andrei meant info about the 36lts branch (and 36.x release
series), and not specifically about Avocado-VT.

> On Tue, Feb 7, 2017 at 12:19 PM Andrei Stepanov  > wrote:
> 
> Hi,
> 
> How do you see an idea to create a file
> in https://github.com/avocado-framework/avocado with information
> from 
> https://www.redhat.com/archives/avocado-devel/2016-April/msg00038.html 
> ?
> 

Mentioning the LTS branches (currently 36lts and their related releases)
in indeed a good idea IMHO.  Just a few lines, with a pointer to the
proper (longer) explanation would suffice.

- Cleber.

> On Mon, Feb 6, 2017 at 2:41 PM, Cleber Rosa  > wrote:
> 
> 
> On 02/06/2017 08:34 AM, Cleber Rosa wrote:
> > Hello to all Avocado users and developers,
> >
> > This is a heads-up about an important change that is coming to
> Avocado:
> > we're dropping Python 2.6 support.
> >
> > Why?
> > 
> >
> > Initially, we planned Avocado to be supported on Python 2.7
> and Python
> > 3.x.  Then we realized that a lot of our users still depended
> on Python
> > 2.6 because of platforms such as EL6.
> >
> > Python 2.6 support came, and after a while our first LTS
> (36.0) version
> > was released.  This gives EL6 users a stable version they can
> rely on.
> >
> > Now it's time to look forward.  By dropping official support
> for Python
> > 2.6, we can focus our energy on other goals.  Since we're
> talking Python
> > versions, one of those if to support Python 3.x in the same
> code base.
> >
> > When?
> > =
> >
> > Pretty soon, that is, as early as the published PR is accepted:
> >
> > https://github.com/avocado-framework/avocado/pull/1748
> >
> > Users on EL6:
> > =
> >
> > We recommend our users running Avocado on EL6 to stick to the LTS
> > releases (currently version 36.3).  This will ensure that
> bugfixes will
> > be delivered to you.  For more information on how to use the LTS
> > versions please check the following link:
> >
> >
> 
> http://avocado-framework.readthedocs.io/en/36lts/GetStartedGuide.html#enterprise-linux
> >
> > For more information of LTS releases, check the following link:
> >
> 
> The proper link with info on LTS releases is:
> 
> https://www.redhat.com/archives/avocado-devel/2016-April/msg00038.html
> 
> Regards,
> - Cleber.
> 
> >
> 
> http://avocado-framework.readthedocs.io/en/36lts/GetStartedGuide.html#enterprise-linux
> >
> > Alternatively, if you need features not present in the 36.0
> series, you
> > may still use a version as recent as 45.0, but *without* the
> level of
> > support that LTS releases have.
> >
> > Please let us know if you have any issues or questions.
> >
> > Thanks!
> >
> 
> --
> Cleber Rosa
> [ Sr Software Engineer - Virtualization Team - Red Hat ]
> [ Avocado Test Framework - avocado-framework.github.io
>  ]
> 
> 

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



signature.asc
Description: OpenPGP digital signature

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

2017-02-06 Thread Cleber Rosa 

On 02/06/2017 08:34 AM, Cleber Rosa wrote:
> Hello to all Avocado users and developers,
> 
> This is a heads-up about an important change that is coming to Avocado:
> we're dropping Python 2.6 support.
> 
> Why?
> 
> 
> Initially, we planned Avocado to be supported on Python 2.7 and Python
> 3.x.  Then we realized that a lot of our users still depended on Python
> 2.6 because of platforms such as EL6.
> 
> Python 2.6 support came, and after a while our first LTS (36.0) version
> was released.  This gives EL6 users a stable version they can rely on.
> 
> Now it's time to look forward.  By dropping official support for Python
> 2.6, we can focus our energy on other goals.  Since we're talking Python
> versions, one of those if to support Python 3.x in the same code base.
> 
> When?
> =
> 
> Pretty soon, that is, as early as the published PR is accepted:
> 
> https://github.com/avocado-framework/avocado/pull/1748
> 
> Users on EL6:
> =
> 
> We recommend our users running Avocado on EL6 to stick to the LTS
> releases (currently version 36.3).  This will ensure that bugfixes will
> be delivered to you.  For more information on how to use the LTS
> versions please check the following link:
> 
> http://avocado-framework.readthedocs.io/en/36lts/GetStartedGuide.html#enterprise-linux
> 
> For more information of LTS releases, check the following link:
>

The proper link with info on LTS releases is:

https://www.redhat.com/archives/avocado-devel/2016-April/msg00038.html

Regards,
- Cleber.

> http://avocado-framework.readthedocs.io/en/36lts/GetStartedGuide.html#enterprise-linux
> 
> Alternatively, if you need features not present in the 36.0 series, you
> may still use a version as recent as 45.0, but *without* the level of
> support that LTS releases have.
> 
> Please let us know if you have any issues or questions.
> 
> Thanks!
> 

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



signature.asc
Description: OpenPGP digital signature