... because the current master should be compatible with the Zed
release of the other projects. This effectively removes testing on
Python 3.6 and only Python 3.8 and 3.9 will be tested.
Because the Xena release is not being created for TripleO repos, test
runtime is not updated by automation tools. This change updates
the job template to use the tested runtime for Yoga.
- Use version agnostic "py" inside tox default envs
- Enable py39 testing jobs (new template contains them)
- Address deprecation warning in setup.cfg regarding use of dashes
instead of underlines (avoid future breakage with setuptools)
As part of  - optimize the zuul layout so that content-provider
doesn't run if openstack-tox-pep8 and openstack-tox-tht are not
These jobs are voting so they block us anyway, may as well
save running anything else if these small jobs aren't complete
This file, and its tests, are not useful for tripleo so we're
removing because they're now becoming problematic.
Signed-off-by: Kevin Carter <firstname.lastname@example.org>
This change switches c8-standalone job to the content provider
dependency relation so the jobs share the produced artifacts.
It has been forgot previously.
Nuke c7 jobs from master layout.
"tripleo-ci-centos-8-standalone-on-multinode-ipa" is a job
to create a multinode setup of two nodes having FreeIPA
server along with standalone deployment will trigger when
there are code changes related to TLS and IPA services.
They were deprecated in Train and aren't used anywhere.
This also remove scenario006 which wasn't working anyway, and was
deploying the kubernetes service.
Like other functional jobs, make the new
tripleo-ci-centos-7-containers-undercloud-minion to depend on the pep8
job results to avoid consuming resources if pep failed.
openstack-tox-tht is a dependency of functional testing jobs, which can
be problematic now because it only runs if some files are touched.
If e.g. common/container_puppet.py is the only file that is changed,
zuul will complain because the dependency graph is broken.
Let's relax openstack-tox-tht to run all the times; and stay a
dependency of other functional testing jobs (which brings value).
Until now if there is a nit inside any
Ansible task part of tripleo-heat-templates we will
need to wait until the end-to-end test imports
the actual tasks to fail.
This submission adds the hability to run a syntax
check for any Ansible task part of any role
defined by default in the resource registry.
Also it will allow to reduce the CI CO2 footprint
by not executing unneeded jobs meant to fail.
Let's save the planet and some CI cycles.
OpenShift deployed by TripleO support has been removed in a downstream
version of Stein which make the upstream support difficult to maintain.
OpenShift can be deployed using OpenShift-Ansible and
users who desire to deploy OpenShift 3.11 onto bare metal nodes can
still do so using openshift-ansible directly. The provisioning of
the Operating System on baremetal can be done with OpenStack Ironic on
the Overcloud or also can be done with deployed-servers, achieving the
... and move the services into the deployment directory.
The extraconfig/services directory was initially created for
experimental services using an interface that was work in progress but
is now stable enough, so the services can live among the others for
We've excluded most jobs from running if the tox jobs fail but we were
still running the standalone jobs. Let's skip those too if pep8 or the
unit tests fail.
octavia-api's cli app doesn't behave well with haproxy so let's run
under apache and save ourselves some grief. Also adds cleanup for the
octavia-api tls proxy in update and upgrade tasks if it was previously
Also updates zuul layout for multinode job to track changes to new
flattened octavia service files.