---- On Wed, 19 Sep 2018 02:28:29 +0900 Doug Hellmann <d...@doughellmann.com>
wrote ----
> Excerpts from Clark Boylan's message of 2018-09-18 09:53:45 -0700:
> > On Tue, Sep 18, 2018, at 9:46 AM, Nate Johnston wrote:
> > > Hello python 3.6 champions,
> > >
> > > I have looked around a little, and I don't see a method for me to
> > > specifically select the version of python that the tempest and grenade
> > > jobs for my project (neutron) are using. I assume one of four things
> > > is at play here:
> > >
> > > A. These projects already shifted to python 3 and I don't have to worry
> > > about it
> > >
> > > B. There is a toggle for the python version I just have not seen yet
> > >
> > > C. These projects are still on python 2 and need help to do a conversion
> > > to python 3, which would affect all customers
> > >
> > > D. Something else that I have failed to imagine
> > >
> > > Could you elaborate which of these options properly reflects the state
> > > of affairs? If the answer is "C" then perhaps we can start a discussion
> > > on that migration.
> >
> > For our devstack and grenade jobs tempest is installed using tox [0]. And
> > since the full testenv in tempest's tox.ini doesn't specify a python
> > version [1] I expect that it will attempt a python2 virtualenv on every
> > platform (Arch linux may be an exception but we don't test that).
> >
> > I think that means C is the situation here. To change that you can set
> > basepython to python3 (see [2] for an example) which will run tempest
> > under whichever python3 is present on the system. The one gotcha for this
> > is that it will break tempest on centos which does not have python3. Maybe
> > the thing to do there is add a full-python2 testenv that centos can run?
> >
> > [0]
> > https://git.openstack.org/cgit/openstack-dev/devstack/tree/lib/tempest#n653
> > [1] https://git.openstack.org/cgit/openstack/tempest/tree/tox.ini#n74
> > [2] https://git.openstack.org/cgit/openstack-infra/zuul/tree/tox.ini#n7
> >
> > Hope this helps,
> > Clark
> >
>
> While having tempest run under python 3 would be great, I'm not sure
> that's necessary in order to test a service.
>
> Don't those jobs use devstack to install the system being tested? And
> devstack uses some environment variables to control the version of
> python. For example the tempest-full-py3 job [1] defines USE_PYTHON3 as
> 'true'.
>
> What's probably missing is a version of the grenade job that allows us
> to control that USE_PYTHON3 variable before and after the upgrade.
>
> I see a few different grenade jobs (neutron-grenade,
> neutron-grenade-multinode,
> legacy-grenade-dsvm-neutron-multinode-live-migration, possibly others).
> Which ones are "current" and would make a good candidate as a base for a
> new job?
All these are legacy job, only name changed so i will not recommend them to
use as base. Currently those are on neutron repo instead of grenade. We
discussed this in PTG about finishing the grenade base zuul v3 job work so that
other project can use as base. Work is in progress[1] and on priority[2] for us
to finish as early as possible.
[1]
https://review.openstack.org/#/q/topic:grenade_zuulv3+(status:open+OR+status:merged)
[2] https://etherpad.openstack.org/p/qa-stein-priority
-gmann
>
> Doug
>
> [1] http://git.openstack.org/cgit/openstack/tempest/tree/.zuul.yaml#n70
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
