[all][goals] Switch legacy Zuul jobs to native - update #2

Luigi Toscano ltoscano at redhat.com
Mon Aug 17 13:57:27 UTC 2020


Much progress has happened since the first report, almost 4 weeks ago.

Let's summarize the main documents:

- the goal: https://governance.openstack.org/tc/goals/selected/victoria/native-zuulv3-jobs.html
- the document above now includes the reference to the up-to-date Zuul v3 porting guide: https://docs.openstack.org/project-team-guide/zuulv3.html
- the etherpad which tracks the current status: https://etherpad.opendev.org/p/goal-victoria-native-zuulv3-migration
- the previous report: http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016058.html

If you still have legacy jobs around, please prioritize this porting work. Victoria branching is not far away (actually, quite close for client libraries).

This is the list of projects which still need to complete the work. Most of the legacy jobs derive from legacy-dsvm-base, and those are the most important ones. There is a limited amount of jobs which derive from legacy-base that should be taken into account as well, though.

- barbican (*)
- blazar (*)
- cinder (/) (-> yes, this is my fault for the record :)
- designate (+)
- ec2-api (*)
- freezer (*)
- heat (/)
- infra (/)
- ironic (*)
- karbor (*)
- magnum (*)
- manila (/) - but only devstack-base
- monasca (+)
- murano (/)
- neutron (*)
- nova (*)
- oslo (*)
- senlin
- trove (+)
- vitrage
- zaqar

The symbol close to the project name provides more detals about the status: 
(+) means that the project cores are at least aware of the issue, 
(*) means that there was active pending reviews for some of the remaining jobs, 
(/) means that there was past activity but no open reviews currently

I'd just like to remind everyone that, while not part of the main goal, backporting the new jobs to the older branches when possible will make future maintenance easier.


More information about the openstack-discuss mailing list