[qa] [all] Opinion on dropping the py2.7 support from Tempest & Tempest plugin

Ghanshyam Mann gmann at ghanshyammann.com
Thu Oct 24 01:47:29 UTC 2019

 ---- On Wed, 23 Oct 2019 15:06:04 -0500 Alex Schultz <aschultz at redhat.com> wrote ----
 > On Wed, Oct 23, 2019 at 1:40 PM Matt Riedemann <mriedemos at gmail.com> wrote:
 > On 10/23/2019 2:36 PM, Alex Schultz wrote:
 > > My concern is that in tripleo/puppet we currently rely on 
 > > centos7/python2 as centos8 is still not yet available.  So this pretty 
 > > much means we likely won't be able to run the latest tempest anymore and 
 > > there goes our validations.
 > How much stuff do you think is going to land in tempest that is going to 
 > be useful validation between the time you could use a tagged version of 
 > tempest before py27 support is dropped and when you can roll to centos8? 
 > I can't imagine it's much and you're still going to get all of the 
 > interop style smoke tests we already have.
 > It's probably not going to cause problems, but it's not like we haven't had issues in previous cycles. The concern is really we don't currently have an ETA when RDO will be fully up on CentOS8. So it could be weeks or months.  We're hoping for sooner rather than later but once py2 support is officially dropped, who knows what folks might want to try and start working on. Also, you can't run tempest from a py3 virtual environment or container?

A month or so is all fine. Dropping py2 from Tempest is going to be the last in phase-2 (Ussuri milestone-2 ) (final schedule to be discussed tomorrow ). 
- https://etherpad.openstack.org/p/drop-python2-support


 > puppet no, tripleo maybe. It's already a container in tripleo and we do have a rhel8 container but the issue is reallly packaging for both. 
 > -- 
 > Thanks,
 > Matt

More information about the openstack-discuss mailing list