Sunday, 2019-11-17

*** rcernin has joined #openstack-qa05:46
*** gcheresh_ has joined #openstack-qa07:09
*** bonguardo2 has joined #openstack-qa08:46
*** yoctozepto has quit IRC09:08
*** early has quit IRC09:25
*** early has joined #openstack-qa09:30
*** rcernin has quit IRC09:47
*** rcernin has joined #openstack-qa10:50
*** bonguardo2 has quit IRC12:02
*** rcernin has quit IRC12:09
*** rcernin has joined #openstack-qa12:10
*** rnoriega- has joined #openstack-qa12:12
*** rnoriega_ has quit IRC12:14
*** rcernin has quit IRC12:48
*** tosky has joined #openstack-qa13:36
openstackgerritGhanshyam Mann proposed openstack/devstack master: Add centos-8 devstack nodeset and job  https://review.opendev.org/69469714:37
toskygmann: please leave sahara py2 removal to me; it's a bit tricky14:53
gmanntosky: ohk, sure.14:59
gmanntosky: you want me to leave sahara-plugin-* too and you will take care of those ?15:00
toskygmann: those should be probably fixed after sahara is fixed15:00
toskyso yes, I'd say please leave them around15:00
gmanntosky: but is there any dependency ? i cannot see scenario jobs there - https://github.com/openstack/sahara-plugin-ambari/blob/master/.zuul.yaml15:01
toskyI may have lost the email - was the phase1/phase2 plan documented somewhere?15:01
toskygmann: the image building jobs15:01
gmanntosky: here is the schedule - https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html#schedule15:01
gmanntosky: ok. i will leave sahara repo to you. except lib and testing tools we need to complete those by milestone-115:02
toskygmann: if I remember the discussion, we will use the tempest (and the plugins) with python 3 also against the older branches, right?15:04
gmanntosky: yeah, as long as it run otherwise tempest tag15:04
toskyshould I do the same for other testing jobs defined in branchless repositories as well?15:04
gmannyou mean sahara-tests right ?15:05
toskyor better: should I keep them in a way that the scenario test runner itself works with python3, even when run against a python 2 deployment??15:05
tosky(s/\?$//)15:05
gmanntosky: for all stable branches we do not need to change, so yea we need to keep all jobs for them but master will run only py3 jobs15:06
gmannlike i did in this patch, all master jobs even stable testing job on master are switched to py3 - https://review.opendev.org/#/c/694699/415:07
gmannbasically, ussuri gate (even branhcless repo_ needs to drop py2 jobs, they cannot be run due to dependency like oslo etc dropping the py2 support. and no change in gate for stable branches15:09
toskygmann: for sahara-scenario there are two levels of python 3 usage:15:10
tosky- the python used to run sahara-scenario; this should be switched to python3 also for stable branches, in order to follow the policy15:11
tosky- the python used to deploy the environment in sahara-scenario tests: that must remain python 2, but that shouldn't be a problem15:11
toskyas all the dependencies come from the branch, apart from the dependencies of sahara-scenario itself15:11
tosky(sahara-scenario is the test runner for the scenario tests)15:12
toskyand that's the same, I guess, as tempest when run against a stable branch15:12
gmanntosky: both has to change to py3. it is like deployment tools where image and image building env both needs to run on py3.15:12
toskygmann: no15:12
gmanntosky: say ussuri is for where there is no py2.15:13
toskygmann: no, one moment15:13
toskygmann: it's like tempest: when you run tempest/master against a stable branch (like rocky), the deployed environment is py2, tempest is (going to be) py315:13
toskyotherwise you are testing something which is not working on that stable branch15:13
gmannfor stable branch yes but for master both has to be py315:14
toskya stable branch where a py3 openstack may not work15:14
toskyyes, that's my point15:14
toskybut that means that I need to tune the master job so that it runs against a py2 environment when run against a stable branch15:14
gmannyes so stable branches has to keep testing the py2 as it is, its jobs we have to modify between <ussuri and > ussuri15:14
toskyjust setting USE_PYTHON3 also for devstack is just going to break all stable branches15:14
gmannno, i did for congress , let me check15:15
toskyjust the testing tool (tempest, sahara-scenario) needs to use py3 when running against an older branch15:15
toskydo you mean that enable USE_PYTHON3 on a branchless job which run against a stable branch, thus deploying everything with py3?15:16
gmannlike this - https://review.opendev.org/#/c/691766/10/.zuul.yaml15:16
toskyoh, perfect - and that needs some work on sahara-tests too15:17
gmannwe have to use the branch variant for those. like i did for xenial to bionic migration. <stein was xenial and >stein was bionic for same job15:17
gmanntosky: yeah, i can do that or you want those buts ?15:17
gmannbits15:17
toskyI'd prefer to recheck it15:18
gmannsure.15:18
gmanntempest plugins are but tricky for those that is why i am pushing the patches for those now and keeping WIP till phase-2. otherwise it get mixedup15:19
toskylet's see if I can manage to make it working now15:19
tosky... but tomorrow - today I'm technically not working and still my TODO list is full :)15:19
gmann+1, ping me any help. and feel free to take over those patches15:19
gmanntosky: :)15:19
*** gcheresh_ has quit IRC15:39
*** lennyb has joined #openstack-qa16:27
*** trident has joined #openstack-qa16:43
*** tosky has quit IRC17:26
openstackgerritGhanshyam Mann proposed openstack/devstack master: Add centos-8 devstack nodeset and job  https://review.opendev.org/69469717:49
*** tosky has joined #openstack-qa18:44
*** gcheresh_ has joined #openstack-qa20:18
*** gcheresh_ has quit IRC21:05
*** mvkr has quit IRC22:16
*** mvkr has joined #openstack-qa22:18
*** rcernin has joined #openstack-qa22:50

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!