Open Stack

 ---- On Wed, 13 Jun 2018 05:09:03 +0900 Doug Hellmann <doug at doughellmann.com> wrote ---- 
 > I would like to create a version of the jobs that run as part of
 > lib-forward-testing (legacy-tempest-dsvm-neutron-src) that works under
 > python 3. I'm not sure the best way to proceed, since that's a legacy
 > job.
 > 
 > I'm not sure I'm familiar enough with the job to port it to be
 > zuulv3 native and allow us to drop the "legacy". Should I just
 > duplicate that job and modify it and keep the new one as "legacy"
 > too?
 > 
 > Is there a different job I should base the work on? I don't see anything
 > obvious in the tempest repo's .zuul.yaml file.

I had a quick glance of this job (legacy-tempest-dsvm-neutron-src) and it is similar to tempest-full-py3 job except it override the LIBS_FROM_GIT with corresponding lib. tempest-full-py3 job is py3 based with tempest-full tests running and disable the swift services 

You can create a new job (something tempest-full-py3-src) derived from 'tempest-full-py3' if all set var is ok for you like disable swift OR derived  'devstack-tempest' and then build other var similar to 'tempest-full-py3'.  Extra things you need to do is to add libs you want to override in 'required_project' list (FYI- 
Now LIBS_FROM_GIT is automatically set based on required projects [2]) .

Later, old job (legacy-tempest-dsvm-neutron-src) can be migrated separately if needed to run or removed. 

But I am not sure which repo  should own this new job.

[1] https://github.com/openstack/tempest/blob/67e99b5b45d18f8fd28dbe3b09bd75008267176e/.zuul.yaml#L61
[2] https://review.openstack.org/#/c/549252/

-gmann

 > 
 > Thanks,
 > Doug
 > 
 > __________________________________________________________________________
 > OpenStack Development Mailing List (not for usage questions)
 > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
 > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 >