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.
Change-Id: I75172f2f55e8ef9adc207320e6f0bdebb310d2f8
The added files contain composable services that define
certificate_specs and therefore create certificates when
configured with tls-everywhere.
Change-Id: I08fe238da5cf379b1d5c607b2c544f971e0211be
"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.
Depends-On: https://review.opendev.org/#/c/706288/
Change-Id: I979d32cbc22799df79e9ea7da7d9360c708b76e8
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.
Change-Id: Id2ea4944c688039e28c4d16635bb4f2b0ed23154
Switch to openstack-python3-ussuri-jobs instead of openstack-python-jobs
which means we'll get py3 jobs only.
Partial-Bug: #1861803
Change-Id: I60b111a19090601155769833a267f8e97ab29192
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.
Change-Id: I0b986d70bb04c23494d7fb7b59d44441dc77d400
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).
Change-Id: I3f05ca26064a2897a724876033a5cc4a602c38a2
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.
Change-Id: I6eb7c873cc9a4b7d765e745dc260475bff7b268a
We haven't tested this in many cycles and is not currently being
persued as a supported service to install via TripleO.
Change-Id: Iec607ab6a5ba5b5156009073a264fa88ac59331e
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
same result.
Change-Id: I6a73f7f22dda69bef324ffdaecdcd6be693c1257
... 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
simplification.
Change-Id: I2bd0b169ed18ea2fccfea4475402dd73076924c8
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.
Change-Id: I17d7f3c1a48f6f8d4f52e01cd26af825450c099a
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
deployed.
Also updates zuul layout for multinode job to track changes to new
flattened octavia service files.
Closes-Bug: #1815811
Change-Id: Ied7cb31fbf1222694250e4769573bcbb82ba5bea
We now have a deployment directory where we are moving all services.
This is new in Stein and it won't be backported.
Change-Id: I52039deaa8ff459de5afbfeb3e2c54eb8908bb3f
Change order of default tox envlist in order of likeliness to fail on a
new change and add py37 and py36.
Change-Id: If72e480c12385463088e2e0962801cd7095a6f12
We should be running a python3 job for tripleo-heat-templates and since
we dropped the old 3.5 job, let's add the correct 3.6 job.
Change-Id: I93bd7bf988c881496ecee0c5d4e2bc97a5047571
We are running the regular jobs with constraints now so we don't need to
be running this job. Additionally it's not functioning correctly with
the switch to bionic
Change-Id: I41bf5002bd40654d55456a5cdafcef6b76b1f62e
..for Greater Good.
NOTE: for example, standalone jobs are defined as a template in
tripleo-ci, and here we are adding and override the listed jobs for the
dependencies/files options. If a job is added to the standlone template
in tripleo-ci, we need to add the job and dependency here manually.
If we won't, that job will be consumed as is and run w/o dependencies.
That is the price to pay for not having overrides managed centrally in
tripleo-ci. The latter wouldn't work neither as a single template
cannot fit all the specific needs of numerous tripleo repos. So the
final call was made to manage overrides via local overrides for tripleo
repos.
Save CI resources and shorten wait-in-zuul-queue times
for other patches, when pep8 checks failed (that is YAML validation
for this t-h-t repo).
For core openstack python projects it might make sense to
not split them apart and run them all together. For things like
TripleO/Kolla/Puppet/etc where we have layers of interactions that can
be affected by the results from the linters/unit jobs it makes
sense to split them out.
For example, in tripleo since we use packages, if the unit test fails
the integration test may fail because when we go to built the package
with the new source, the unit test int he package build fails. Thus
we know that'll be a wasted execution and you won't actually get any
results.
An alternative Today:
patchset one:
pep8 SUCCESS
integration FAILURE
patchset two:
pep8 SUCCESS
integration FAILURE
patchset three:
pep8 SUCCESS
integration SUCCESS
Future:
patchset one:
pep8 FAILURE
integration SKIPPED
patchset two:
pep8 SUCCESS
integration FAILURE
patchset three:
pep8 SUCCESS
integration SUCCESS
This may not be true for devstack but if the unit
tests are failing, then the code is likely bad (backwards
compatibility/wrong assumptions about change/etc) and we shouldn't be
running an actual deployment.
Related upstream ML threads:
* http://lists.openstack.org/pipermail/openstack-dev/2018-March/
127869.html
* http://lists.openstack.org/pipermail/openstack-discuss/
2019-February/003142.html
Change-Id: I2216773113f8d4e4a2bdff35709ff739f5164a32
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
Congress doesn't seem to be used anywhere, we never had a bug report or
any sign of somebody out there actually using it.
Let's remove its support in TripleO, to reduce the codebase.
Change-Id: Idca6b12f1c0ca3bc15bedf6469d4063a4dac31fa
The ceph-ansible tasks are now invoked with the tripleo-admin user,
which doesn't by default have write access to /var/lib/mistral, but it
does have sudo access.
This change makes /var/lib/mistral/overcloud/ceph-ansible be owned by
the tripleo-admin user so that subsequent tasks can write to that
directory.
Related-Bug: #1813832
Change-Id: I98bb38078be84cbda3e9a9e338af0d054dc53420
In I7cf36baa80e91d87b1b41c45204c61cf87846d34 we started using the
tripleo-standalone-scenarios-full instead of carrying custom
layout for the standalone jobs in projects. Looks like we forgot
to remove the gate definitions here.
Change-Id: I2c3940c7903f9fd4b9d0ec1aca8741182b9c76cd