Replace "legacy" style jobs with native zuulv3
ones built within the manila-tempest-plugin
repository. This refactoring is driven by a
community wide goal to stop relying on devstack-gate,
a deprecated component of the OpenDev CI system [1]
Remove in-tree devstack gate hook script portions
that are no longer necessary; and mark the rest as
deprecated, since third party CI could still be
relying on these hooks.
Replace "manila-tempest-dsvm-mysql-generic",
"manila-tempest-dsvm-postgres-generic-singlebackend",
"manila-tempest-dsvm-generic-no-share-servers" and
"manila-tempest-dsvm-scenario" jobs with
"manila-tempest-plugin-generic" which preserves
coverage for the generic driver, while removing
unnecessary duplication/separation. See commit
message in [2] for more details.
Remove older CentOS and HDFS jobs since they
were not being executed.
Remove "custom" image jobs targeting custom
manila-image-element based builds, the jobs
now originate in the manila-image-elements
repository. [3]
The dummy driver job has been split into two parts
for testing DHSS=True and DHSS=False in separate
jobs. Read more about the motivation in the commit
message for the change that created that job [4]
While some name tags such as "postgres" and
"ipv6-only" have been removed from the job
names, the functionality of the job hasn't
been changed.
This change will not be backported. Instead, new
changes akin to this may directly target older
branches of manila.
[1] https://governance.openstack.org/tc/goals/selected/victoria/native-zuulv3-jobs.html
[2] https://review.opendev.org/726291/
[3] d9d2f16360/zuul.d/manila-image-elements-jobs.yaml (L34-L67)
[4] https://review.opendev.org/740534/
Change-Id: I2be6fc12c787c05c7df68297990fcdca96f57c5d
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
The existing "manila-grenade" job relies on
devstack-gate, a deprecated project. The Grenade
project now has a native zuulv3 style job that
we can inherit and run manila's upgrade tests.
Manila's grenade tests are only going to run
API tests, and hence this grenade job doesn't
have to enable nova, cinder, glance, neutron
and swift. However, bug #1887835 prevents
us from disabling nova at the moment,
and nova requires glance, placement and neutron
to be deployed, so we'll be enabling these
services too until that bug is addressed.
Depends-On: Id5a9467247df1d8f0ec6dee3fae842ba673c34ed
Depends-On: Ieaf37ec10db9a8bdce6bb195b76335fea9b2b52f
Change-Id: I1636c612ac2475f7a00c0888ef62daa6c516eef2
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
Switch to using the LVM driver in the grenade
job that allows us to add a minor data
path test to prove that upgrading manila
has no impact on data path connectivity
to resources created by manila.
Change-Id: I8588e8f988d85dc64e19e7a44a25c3dd0b776892
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
The CephFS driver optionally advertised snapshot
support to manila, based on a configuration
option "cephfs_enable_snapshots". Manila does not
provide snapshots by default to users, unless an
administrator chooses to set the "snapshot_support"
extra-spec in the share type they're using. So this
configuration option is really an unnecessary safeguard
at this point.
Moreover, CephFS snapshots are fully supported from
Ceph Nautilus, and with Id847b1b5e6623172f2600afd69e51182067444cb,
manila added a support statement for the Victoria
release that indicates that Nautilus is the minimum
version of ceph supported. So let's default this
option to True, and deprecate this option at the same
time to eliminate this duplicate safeguard.
Partially-implements: bp update-cephfs-drivers
Depends-On: I885ff78586540d01590f98cca2a00d55161dbe04
Change-Id: I1ef42b414f8af0b8f9a912655757ec200a75c309
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
To set up some first party backends such as
ZFSOnLinux, CephFS via NFS gateway, Container
(where the NAS server is containerized) and LVM,
manila's devstack plugin creates a NAS server
on the devstack host.
On test machines, access to this NAS server is
firewalled from networks outside of the host's
internal network namespace (including from private
project networks that are in different network
namespaces, on the same devstack host).
We currently use a legacy devstack-gate script
to disable firewall on NFS ports; however,
anyone that installs devstack with LVM, Container,
ZFSOnLinux, CephFS-NFS drivers will need these
firewall ports to be opened to be able to mount
shares exported off their devstack host machines.
Move these firewall commands to the devstack plugin.
These commands can be invoked by setting the localrc
variable MANILA_ALLOW_NAS_SERVER_PORTS_ON_HOST to True.
The value of this variable is False by default,
to preserve existing behavior.
Change-Id: Ic9cad47662f1edf2e5c710dbe64d580bc5f01d44
manila-tempest-minimal-py35-dsvm-cephfs-native-centos-7
and
manila-tempest-minimal-py35-dsvm-cephfs-nfs-centos-7
have been unused for a long time, and they are not
used anywhere in any repository. So lets get rid of
them.
Change-Id: I51647efa12cee6c428bfd299d6b047174e1316ef
We needed this plugin because neutron-dynamic-plugin's
code base included its tempest plugin in-tree. This
issue was addressed in https://review.opendev.org/#/c/695014/.
So we no longer need to install neutron-tempest-plugin
in manila jobs.
Change-Id: I34b77c95aad7ee2b67ba876db8aa64bbc44adb79
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
As part of Train community goal 'Support IPv6-Only Deployments and Testing'[1],
we need to define the integration job which deploy services
on IPv6 and perform testing to make sure service listen and communicate
over IPv6 properly.
Manila has legacy zuul jobs only so base zuulv3 IPv6 job 'devstack-ipv6' and
'devstack-tempest-ipv6' cannot be used and we have to copy the whole
run.yaml to set the IPv6 setting and run the IPv6 verification
script via post_test_hook.
This commit adds the new job 'manila-tempest-minimal-lvm-ipv6-only'
run on gate and set the required IPv6 setting'.
Story: #2005477
Task: #35903
[1] https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
Change-Id: I761b2f244a257e86c3032e0b33aa2600c1d9d2a3
- Change post_test_hook in the gluster CI takes arguments
- Enable glusterfs-nfs CI
Depends-On: https://review.opendev.org/#/c/674738/
Change-Id: If6d233ffd658cd75599eec36eb8027f35771e224
The old/legacy job depends on components
from OpenStack infra that are not maintained
any longer.
Depends-On: I6b1d0e97ecdf9a2befa2a052a1743916d662d136
Change-Id: I143b78a8abf7ce714a574adef1698affd5956b1b
manila-tempest-plugin can be installed with its
devstack plugin; Installing it via manila's plugin
is unnecessary. So, deprecate its installation
in the DevStack plugin.
Change-Id: I21c08069ff82b3bfb52ef7ac960183ddc866c2ee
Add py2 dummy jobs to keep some python 2 coverage through the
Train release, but convert all the other tempest jobs to python 3.
Change-Id: Ia5fd26c30c6aaeb97ae1b524c5fd58b890fdb054
Add required components for scenario
testing and enable api and scenario tests
on the same job. The experimental
cephfs-nfs-centos-7 job has not been modified.
Depends-On: https://review.opendev.org/#/c/657669/
Depends-On: https://review.opendev.org/#/c/665039/
Change-Id: I74508fd02d7d4ff54270e91743c7ea06103299b1
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: I4df9f22a60ef50677867eaf4baf9e7e55a951dda
legacy-dsvm-base now [1] runs with bionic nodeset so use it
directly instead of overriding locally to use bionic.
[1] https://review.openstack.org/#/c/639096/
Change-Id: I2a136f84e7d5d5be8a23830c0b334dc609092004
Enabling tls-proxy allows devstack to
set up a tls proxy server that front-ends
interactions with the manila-api and
terminates tls connections.
Also enable tls-proxy in dummy and lvm
jobs. The dummy driver job is configured
to run the in-built wsgi server, the lvm
job is configured to use mod-wsgi.
Closes-Bug: #1816836
Change-Id: I48b0ccc082604d78242ba61bee94a45efeb2467b
We need these for python3 support since the CentOS
jobs will not run correctly under python3.
Depends-on: https://review.openstack.org/#/c/627037/
Change-Id: I0e4baaaca5046f9c0ee32cf3de78133f743fd66d
And use a 'file://' url for the custom manila image.
See also https://review.openstack.org/#/c/623330. These
are interdependent patches but no harm is done by merging
this one first and having 623330 depend on it since retrieval
of the image name is not working correctly anyways.
Partial-Bug: #1807969
Change-Id: Ib3a74d170f159dfbc38b5302f00800f3530f4921
These jobs often fail due to timeouts so only enable the services
required for devstack tests with these back ends.
Change-Id: Ib620ec3c2a9999ea9908a7c23aa7172c40a4cbd9
When upgrading from Queens to Rocky,
since neither release has the tempest plugin in-tree,
it has to be explicitly installed
in the job.
Closes-Bug: #1785370
Change-Id: I77b5e0eb8824a8a00633aacb45ebea07572503d5
Require running the job with neutron-tempest-plugin
since neutron-dynamic-routing relies on it,
and does not specify it in its requirements.
Change-Id: Ic8e8033b77f82c3264270ba042a44177babaff9b
Closes-Bug: #1772077
There was a recent change announced on the CentOS
mailing lists [1] regarding housing centos-release-SIG
repos for CPU architectures other than x86_64. We rely on
centos-release-pike within our test jobs and the
repo centos-qemu-ev is found under [2].
There is now a YUM variable called $contentdir
which determines where the repos may be, and this
variable isn't set in the base images.
With $contentdir set, the URLs resolve correctly
within /etc/yum.repos.d/CentOS-QEMU-EV.repo.
See corresponding fixes for kolla [3] and
tripleo-quickstart-extras [4]
[1] https://lists.centos.org/pipermail/centos-devel/2018-March/016542.html
[2] http://mirror.centos.org/centos/7/virt/x86_64/kvm-common
[3] Ieb26c0aa65ba3ec1a45a33f87f670e5ecb782f82
[4] I6279bd4088bd87f37c58b7da25b675c5456506d6
Change-Id: Idcacfb6dbfb0760128f10dbc0573856e4250b3bc
Closes-Bug: #1771969
Replace tox-genconfig legacy job with native Zuul v3 job.
Also, remove name from project stanza, this is not needed anymore.
Change-Id: Ic79f5a018faab4d0de6296808dd5e8621ea9d498
This change complements the work of preceding IPv6 scenario
test changes [1,2] by enabling the settings that allow the tests
to be run in the Upstream CI.
[1] I4ca727f92618998242af18908bbbda6bb5f86303
[2] Id8b005cdd429d53a75624885fe7ca795746c3ede
Change-Id: I705b7d9cbc14d4bbc4d89b4c343205908758a5cb
Depends-on: Id8b005cdd429d53a75624885fe7ca795746c3ede
Depends-on: I4ca727f92618998242af18908bbbda6bb5f86303
This patch makes necessary changes to devstack manila
plugin in order to be able to run IPv6 scenario tests.
Part of the changes included the dependency of
neutron-dynamic-routing plugin and the installation
of quagga, so routes in devstack host can be created
automatically for each router and private network
created by tempest during the tests.
Also, added a new config option "override_ip_for_nfs_access"
for manila tempest plugin that overrides the access rules used
for NFS scenario tests. This option can be set by exporting the
environment variable "OVERRIDE_IP_FOR_NFS_ACCESS" with the
intended value before running devstack.
This change is enabled by a following change and
tested alongside a change on manila-tempest-plugin
project.
Please note that we are temporarily disabling IPv6
functionality in Host-assisted Share Migration, as
the Data Service is not able to handle IPv4 + IPv6
scenarios.
Change-Id: I4ca727f92618998242af18908bbbda6bb5f86303
Needed-By: Id8b005cdd429d53a75624885fe7ca795746c3ede
Goutham Pacha Ravi