After discussing this topic again during the PTG I spent some time
checking our scenario jobs which runs in the check and gate queues.
After analysis this patch proposes to:
* remove neutron-ovs-tempest-slow job from both check and gate queue as
slow tests are already run also in the
neutron-ovs-tempest-multinode-full job,
* remove neutron-ovn-tempest-slow job from both check and gate queue as
slow tests are already run also in the
neutron-ovn-tempest-ipv6-only job - of course this job is using IPv6
instead of IPv4 but I don't really think it's big issue in that case,
neutron-ovn-tempest-slow job was multinode job, unfortunately
neutron-ovn-tempest-ipv6-only is single node job and for now it isn't
possible to make ipv6-only job to be multinode job so we will keep it
like single node job and hopefully move to be multinode job when zuul
will provide required data in the job's inventory,
* move neutron-ovn-tempest-ovs-release and
neutron-ovn-tempest-ovs-release-ipv6-only jobs to periodic queue - I
think that running those tests once per day should be enough.
Additionally this patch removes definition of the neutron-ovs-tempest-slow
and neutron-ovn-tempest-slow jobs are those jobs aren't used anywhere now.
Conflicts:
doc/source/contributor/testing/ci_scenario_jobs.rst
zuul.d/project.yaml
zuul.d/tempest-multinode.yaml
Change-Id: I657881c319d425470277885545240d6a8b66a1f6
(cherry picked from commit 5357689002)
0082d93f17