Currently we test metal aio scenario for the upgrade, which is single
host without a cluster. Having the infra upgrade jobs will help to test
cluster functions after upgrade as we have 3 containers for galera in
that scenario.
Change-Id: I3f00eaad0feca7fe985a339c5b7ad3f8e0736e23
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: Ie6ec30dbd51f1344a98578c79dc1f03e99b78e15
This reverts commit 3d405dfd52.
See [1], thia ahould be fixed in 2.9.10 and we must either remove or
refactor this code to move past ansible 2.9.9
Change-Id: Ibf636be010edb30e4f186f4d8e411f514ff1b58d
This is a merge of two previous patches [1,2] which require each
other in order to merge in particular due to unpredictable behaviour
of MariaDB 10.4 during cluster status reporting which is addressed
through [2].
[1] https://review.opendev.org/735204
[2] https://review.opendev.org/735079
Co-Authored-By: Dmitriy Rabotyagov <drabotyagov@vexxhost.com>
Co-Authored-By: Marc Gariepy <gariepy.marc@gmail.com>
Change-Id: Id04fa994f527e2a15a87ba91d56d10eaadf8f58f
openSUSE Leap 42.3 is out of maintenance and end of life.
It has been superceded by Leap 15.0 and the current version
as of today is 15.1. by using opensuse-15 we point to the
latest 15.x nodeset.
Change-Id: I4cf89ee23e28ce20b4076d4eb81daa04a8055499
Currently this role doesn't test the integrated jobs.
This is a problem because this role can possibly break
the integrated, as we don't test it.
Change-Id: I109b3293df32c73969c39a17230881eddb338c78
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 '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: I7d1f07878dba7d21aecd59fa75e9117b50b886e6
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: I562a787360e051589a6ed6a90544f244dccf4525
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: I5f6a854795890ea9ec4a541a3e6b37d3bb8aa7f2
Story: #2002586
Task: #24319
In order to have more centralized configuration, switch the role
to use the project-template instead.
Depends-On: I2608fc5a0230436cebb0e6c579deae7bd4d7c209
Change-Id: Ib6f61b7b9e635aec154d9938376eea6ead50e254
The problems at the moment with setting up SSL support with
Galera are:
- The keys are not used when creating users in the mysql_user
Ansible module
- The private key must be converted to PKCS-1 in order to work
properly with Galera.
- The MySQL client configuration is missing the settings that
include the SSL certificates.
- Hard-coding the cipher causes problems for older clients,
so we instead enable SSL and let the client and server
negociate the ideal cipher.
This patch cleans up all of those issues, removes verbose
logging from the SSL job because we have ARA to gather all
the information we need and adds jobs for all the deployment
platforms that we support.
Change-Id: I27218c4086a50d238082895092fb8aa5e7fad807
Let's make sure that we upgrade Galera across all distributions.
Depends-On: I804ecab571f8e70fc01d86741246dd8cbafb15fb
Change-Id: I44246211f1af8fe484a7d1cb9d97758ef1ba2cf7
The role is functional and it can install a cluster succesfully
so there is nothing stopping us from gating on it today.
Change-Id: I6326b458039a4e9cd956c9f8a04e1fc4f66cdeb8
Now that all the patches to set the correct MariaDB version
have merged to all branches we can restore the upgrade check.
Change-Id: I6dc92fa9e5f60e6be558ffc8e4e0ec16ebda58af
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Idb767c68ef052e0a3924b42f6cc6480cff06350a
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: Ieb11ab9d45cdc03b13996bad9eea74f2b869e5e4
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: I24e87c33512108ae4ef4aef9f8f7699efb405415
Depends-On: I0391ec310c4eede436011a48490e3c524c8ddf4d
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: I1911542e61df7bed475eac199669773ae4e1a205
Dmitriy Rabotyagov