Open Stack

David Moreau Simard <dms at redhat.com> writes:

> I'm OK with this.
> Should we get to a point where the scripts can be used by both Zuul v2
> and Zuul v3 simultaneously so that there is no "migration" or "cutover" so
> to speak ?
>
> It might mean some amount of work but it shouldn't be too bad, I think ?
> Ansible (Zuul v3) will potentially end up running Ansible but we've seen
> worse and it'll be temporary.
>
> It would allow for a smooth transition because we would just essentially
> stop running the v2 jobs when we are ready.

Yes, I'm working on that in this series of changes to create the
devstack-legacy job:

  https://review.openstack.org/497699

However, there will still be work for the migration script to do.
Essentially, the JJB shell snippet will need to be transformed into a
Zuul job variable, the usage of the local_conf macro transformed into a
different job variable, and any projects which appear in "PROJECTS=..."
variable assignments in the job shell will need to be detected and added
to the required-projects job attribute.  I believe these are all
relatively straightforward transformations.

-Jim