With changing cinder code we potentially can break some backends.
In order to detect this in time we are adding ceph and nfs scenarios.
We also fix lvm backend for use on RedHat.
Depends-On: https://review.opendev.org/c/openstack/openstack-ansible/+/859339
Change-Id: Ifceb2b816199339ec7725bd95cc890595eed95d9
We've created integrated linters check job a while back and it's successfully
working for several releases. At the moment we experience difficulties
with future maintenance of the linters check from the openstack-ansible-tests
repo. So instead of fixing current one, we replace it with modern version of
the test.
Change-Id: I16531da2fb45dde15b57dcd1b09ec1e471d1addb
Since we copy all release notes to the integrated repo there is not need
in publishing release notes for each repository. We should only verify their
validity and linting.
Change-Id: I51d0f20c05a7949dfbb802a19fcb491dcc410618
In order to do a more complete verification of any patches,
we add a full uncontainerised OpenStack deployment to the
functional testing using the integrated repo. This replaces
the previous role functional test mechanism.
Any additional role tests are left as-is. They will require
some extra implementation in the integrated build before they
can be transferred.
Depends-On: https://review.openstack.org/647840
Depends-On: https://review.openstack.org/648502
Depends-On: https://review.openstack.org/648551
Change-Id: I1255361809c14a3a2742092414a38e3f5a612719
In order to do a more complete verification of any patches,
we add a full uncontainerised OpenStack deployment to the
functional testing using the integrated repo.
Depends-On: https://review.openstack.org/629542
Change-Id: I16939a348327ab4a3d5b617d33ba312a3466c73f
Now that we're using the general templates, we can slim down
the role test definitions. We can also remove tests which are
not being watched, or which are fundamentally broken. With
this we can also remove unused scripts/plays.
We do the following:
1. We remove the 'ssl' job, given that the person working on
that is no longer doing so, and no-one else has picked up
the work.
2. We remove the 'upgrade' job, given that it's been broken
all cycle due to the way the job executes and we need to
regroup to figure out another way to do it.
Change-Id: I28ff7b95d3b2cc064c59c9966e9c25c7ad9184da
This is a mechanically generated patch to switch the documentation
jobs to use the new PTI versions of the jobs as part of the
python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I7b77be296d0f4014ce37e803b855160e5b6b0e0e
Story: #2002586
Task: #24319
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I47442caa4d7f977701f8bc4b394f1524613afa80
Story: #2002586
Task: #24319
There will be no Rocky packages for Xenial so there is little point
in testing Xenial against current and upcoming releases. As such,
lets switch to Bionic. This also makes the functional jobs in Bionic
voting again.
In addition, this change switches to use smoke tests only because
there is no upstream coverage to use the cinder_tempest_plugin which
seems to have some broken jobs.
It seems that we're currently configuring the LVM config after
the service is setup which can cause it to go up with missing
LVM configuration.
This moves the tasks up so that the underlying storage is prepared
before the service is installed and deployed.
This is a squashed commit that covers a few topics because dropping
the Xenial jobs fails because the cinder_tempest_plugin tests
are failing. Also, the LVM config running later seems to cause
the process to spin, possibly causing some troubles for RabbitMQ
connectivity.
Depends-On: https://review.openstack.org/#/c/591966/
Depends-On: https://review.openstack.org/#/c/591968/
Change-Id: I592691358f8dc587182052f9a079886dfc442744
The necessary packages are now shipping for CentOS so we can deploy
and ship Cinder directly from packages and gate on that.
Change-Id: I16710c2b8e4ee2f11f85d6db1c5270481bd1fc70
In order to have more centralized configuration, switch the role
to use the project-template instead.
Change-Id: I9cffa19870edec8df244a97412670049b199ad14
The extra jobs that we have are not something that is needed, we simply can
set the jobs to non-voting in the project definition and avoid having non
voting jobs.
Change-Id: If7e15b57302a9ff80dc8ae0824ce850468b85985
The cinder_distro_packages contain packages which are build dependencies
to the 'PIP' ones so we don't need to install them when we are using the
Cinder distribution packages. This also renames the '*cinder_wsgi_bin'
to '*cinder_uwsgi_bin' since it refers to the actual uwsgi package.
Finally, we add the missing 'install_method' conditional when recording
the local facts.
Change-Id: Ib6f3a85dd20c61611e968baffd4e3c725d9e39b3
Implements: blueprint openstack-distribution-packages
Distributions provide packages for the OpenStack services so we add
support for using these instead of the pip ones.
Change-Id: I4ff3cbf5e1e1ce04cd4cdc9c1ce97afdeace5159
Depends-On: I5a78e2120e596d36629b4ba978b2b5df76b149b0
Implements: blueprint openstack-distribution-packages
There isn't a need to run non-voting jobs in gate, as it ends up just
wasting CI resources. Results can be obtained from the check pipeline
results.
Change-Id: I017a5d979fd70f086860b0604b4cec4d8891b1ba
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Ib61a6f00eba2a60aa35d232e6f65ce2f4a839222
When 'cinder_galera_use_ssl' is True, use an encrypted connection to
the database using either a self-signed or user-provided CA certificate.
A new non-voting test has been added to verify that the role remains
functional when enabling SSL features.
Partial-Bug: 1667789
Change-Id: Ifeda0acb4b70ba313e6572c806125d31ab3eb300
Depends-On: I95cc994df5118fce7ce588fc0bff979bc283a6f3
Initially the intent for adding this was to better test
any patches for roles together before they merge, but it
has had the unintended side-effect of causing patches to
take much longer to merge (because they all get lined up
in a single queue, rather than independent queues) and
a lot more infra resources are used (because a patch
that fails at the top of the queue will result in all
subsequent patches restarting all their tests).
As discussed in the channel, we'd prefer to revert back
to the previous independent queue method of testing. It
has served us well.
Change-Id: Iaf062e3707b320104361beffc4cf48254492509f
Currently the linters test is in the project-config
repository, but those are meant to be used for standard
jobs which do not require any repository other than the
one given. Our lint tests use the 'openstack-ansible-tests'
repository, so we should rather use our own job definition.
Change-Id: Ie6f7265084471efd0ab6e1a14f9d214162a57d8e
Depends-On: I0391ec310c4eede436011a48490e3c524c8ddf4d
This changes the a-r-r with the proper version, and fixes
the repo path for role upgrades:
The role will, during test-upgrade-pre, have its current branch
checked out, and will deploy the current branch infrastructure,
including the generation of the constraints.
Then, the installation of previous branch of the role will use
the constraints for its previous version, but will have no
constraints for it, and fail.
We need to generate the constraints for the previous version too.
This should do it.
On top of that, we needed to update the work for Zuul v3:
This implements the initial OSA zuul v3 role jobs.
This patch implements an initial set of jobs intended to match
the current job execution method. It does not intend to improve
how the jobs are executed - only to replicate what is currently
in openstack-infra/openstack-zuul-jobs and provide the platform
to iterate on.
Change-Id: I2d455e9a47c85b77655e3b55847cf45959901b77
Dmitriy Rabotyagov