Port the legacy legacy-tempest-dsvm-multibackend-matrix job to the
native Zuul v3 syntax, and rename it following the guidelines
(cinder-multibackend-matrix-migration).
This job tests the migration between two different backends
specified through the volume.backend_names configuration
key in tempest.conf.
Now the job leverages the existing zuul code, namely the
run-tempest role, which is called multiple times with all
the possible combinations of the 3 tested backends
(lvm, ceph, nfs) where the source and the destination differ.
The final JUnitXML output summarizes the test results
for each of the tested combinations.
Change-Id: I34e7e48ee63c4c269f82ae178a7118ed402cad6d
The functional tests are executed from the tempest node(s), which means
that the collection must happen from the same place, not all nodes;
otherwise the playbook code fails on pure compute nodes.
Change-Id: Ibe1796e1380add34b6d8f19606bb55fda13c3c08
Follow the same pattern of the other jobs which deploy devstack
but runs also functional tests (see devtack-tox-functional
and devstack-tox-functional-consumer).
Without this, the older branches where cinderlib functional tests
use Python 2 (stein, and soon train when that is branched) fails
because they try to install packages part of which are Python 3
only.
The same change was applied to the branchless jobs defined
inside cinder-tempest-plugins: https://review.opendev.org/738078/
Change-Id: I2e8af74bae63c487e786da6e99aa4827029a05a2
Specialize the grenade-multinode job and test the variations
on upgrade where a few services are available on the subnode only
(c-bak only, c-bak+c-vol, c-bak+c-sch+c-vol).
Also, use grenade instead of grenade-py3. The former is now used
(after Iea355514ec7cc2a52ed5e88c356bcb1cdeadd639) in
integrated-gate-storage instead of the latter, which means
that we need to change it in order to apply the value of
irrelevant-files.
Depends-On: https://review.opendev.org/548936
Change-Id: I3eac1afcbb69e25e9b2a916910caf3291aa7c1fe
- cinder-tempest-lvm-multibackend is the simple LVM multibackend job
and replaces legacy-tempest-dsvm-lvm-multibackend.
- remove legacy-tempest-dsvm-zeromq-multibackend, as ZeroMQ
support was deprecated in Rocky and removed in Stein.
It could be replaced by inheriting from
cinder-tempest-lvm-multibackend in older branches
when this patch is backported;
- replace cinder-tempest-dsvm-lvm-lio-barbican with
cinder-tempest-dsvm-lvm-lio-barbican provided by
cinder-tempest-plugins;
- replace legacy-tempest-dsvm-full-devstack-plugin-nfs with
devstack-plugin-nfs-tempest-full, now provided by
devstack-plugin-nfs;
- update cinder-plugin-ceph-tempest to also run cinderlib tests
and make it inherit from devstack-plugin-ceph-tempest-py3.
Change-Id: Icdafaf55494b6dd74ec31c3572d7344fcc028166
below grenade jobs for cinder are present in opensatck-zuul-jobs
repo. These needs to run on py3 from Ussuri onwards and py2 for
stable/branch.
py2 version has been kept in opensatck-zuul-jobs and for ussuri
onwwards these has been migrated to cinder repo with py3 version.
- legacy-grenade-dsvm-cinder-mn-sub-bak
- legacy-grenade-dsvm-cinder-mn-sub-volbak
- legacy-grenade-dsvm-cinder-mn-sub-volschbak
Change-Id: I67d2504dd80214e615a45f605b0023ca6919fb73
tox:
- bumped tox minversion to 3.1.0 to get 'ignore_basepython_conflict'
- tox 'ignore_basepython_conflict' allows us to factor basepython=
python3 to the [testenv] but override it when using '-e py37'
(that way you actually get python 3.7 instead of whatever the system
has for python3)
gate:
- adjusted tempest-dsvm-lvm-lio-barbican to use python 3 for devstack
- removed openstack-python-jobs template as these tests are covered
in py3 by openstack-python3-ussuri-jobs
- dropped integrated-gate template as these tests are covered by the
integrated-gate-storage template, which is already python3
- dropped tempest-full jobs as these are covered in py3 by tempest-
integrated-storage
- changed openstack-tox-functional to openstack-tox-functional-py37
and made it voting
The legacy-grenade-dsvm-cinder-mn-sub-* jobs are converted to py3
in a different patch, https://review.opendev.org/#/c/695787/
Left py2 requirements and did not adjust setup.cfg to require py3.
This prevents breakage for any projects still installing cinder under
py2. These can be changed by a follow up patch in January.
Co-authored-by: Sean McGinnis <sean.mcginnis@gmail.com>
Co-authored-by: Brian Rosmaita <rosmaita.fossdev@gmail.com>
Closes-bug: #1853372
Change-Id: I376bd708ecc864f29c35b7225f875bb20a98cd3c
There is a typographical error in tempest-and-cinderlib-run.yaml.
Correcting spelling from enviroment to environment.
Change-Id: Iaebfd31bc2c4fd304a11c49da23f5f5efc513757
This patch replaces job devstack-plugin-ceph-tempest with
cinder-plugin-ceph-tempest that inherits from it.
This job runs the same devstack-tempest.yaml playbook but also runs the
cinderlib-run.yaml playbook for the cinderlib functional tests.
Since the openstack/cinderlib project is a required project for this job
we'll be able to run cross-repo dependencies with cinderlib.
Change-Id: Ia532b3fcfbecee7c6dc7aa302e6d90a8067b7ff0
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I394887884fb90778a6704bd6cf29783885cb5972
This patch adds the openstack/cinderlib project as a required project
for cinder-tempest-dsv-lvm-lio-barbican job and then runs its functional
tests as part of the CI job.
With this we'll be able to run cross-repo dependencies with cinderlib
for the cinder-tempest-dsv-lvm-lio-barbican job.
Change-Id: I25c19cf1f7da6881807e729a326cd94d07b4c42d
We're running a fair number of scenario tests
that we don't need to be here. Just grab the
ones that are interesting for Cinder.
Change-Id: If17a249bc99d3e16bd57cdf7ce73e1ce3a739455
We would likely benefit by running
tempest.scenario.test_encrypted_cinder_volumes tests
and
TestVolumeBootPattern.test_create_server_from_volume_snapshot
Change-Id: I5082926cc5ede463d67e3ab995e17983b5db3855
Pull os-brick from git instead of pip
when testing on master. For stable branches,
still pull os-brick from pip.
Change-Id: Ib9ebfa67020d99d83ebb33552677e9e2e334f9a7
