The manila post_test_hook.sh script still
uses jenkins as user, but with zuulv3 that
should be zuul. $USER solves that issue.
Change-Id: I23299a15249be292e3a60450db2adea0abab64bb
Change [1] removed the tempest pin from the
pre test hook in manila proper.
Remove it here as well.
Closes-Bug: #1711812
[1] Ia402fb79e1de5c9925f575d635b9928475095f86
Change-Id: I7f06610820b81788b3d536a8114c69623ccf0896
When running with the manila plugin on ubuntu Xenial,
devstack fails with a message when attempting to create
a logical volume within the glusterfs VG with a message
about insufficient allocatable extents [1].
Change the hard-coded number of extents supplied to
the lvcreate command to a percentage of the VG.
Closes-bug: #165238
Change-Id: Ia53f0e1b9b80ae0012d720a3f7b3696cadbd843c
Replace not available anymore "JOB_NAME" env var with
"GLUSTERFS_MANILA_DRIVER_TYPE" one in devstack hooks to unblock
CI jobs.
Change-Id: Ice8395325d20060df511b9de82c944200ceea2aa
The log files created during the Tempest run
get scp-d to their final location via Ansible.
Some root-owned log files are not readable
for the Ansible process and that results in
getting an EPERM and thus the gateway job
is qualified as UNSTABLE.
We don't have a hook in between the gluster
invocations creating those log files and the
call to the Ansible upload job, so we are not
able to chmod the logs as needed.
Instead we apply the following hack: we create
and mount a VFAT file system onto the log directory
where the trouble strikes; and VFAT does not implement
POSIX file permissions therefore all files within it
qualify as world readable.
Change-Id: I9a85888166b5b9c28a049e7c17335e2082a61f92
The two manila gluster drivers, glusterfs and glusterfs native do
not yet support 'ro' access level. So disable 'ro' access level
tempest tests for the two drivers by making the CI post hook
script modify the tempest config file appropriately.
Change-Id: I32f255eafe4938196c54108a45d7ddb48eceb8bf
With the change [1] to DevStack project, preconfigured creds for Tempest,
required by Manila, cannot be used anymore. And for now, latest Tempest
interfaces do not allow use of preconfigured creds due to bug #1524717.
So, until this bug is fixed, workaround Devstack changes by setting legacy
options explicitly.
This workaround fix was carried over from the change [2] in the Manila
project.
[1] I65b56ff681d6c27094380693c953fbc3664eceb0
[2] I516a6c9ab4396b14e3984d5f810210e4fcf7ec85
Change-Id: I09df56aa611ba755c282c575f712261c48385fe9
Related-Bug: #1531049
Remove inline comments after line escape that isn't understood by the
tox's parser.
This is due to the backward incompatible fix,
https://bitbucket.org/hpk42/tox/issues/181
Related Bug: #1527562
Change-Id: Ib92b65b510fc3a6261e0e890c91af0718f24fc33
Also took the opportunity to move to test_with_retry
instead of using a hand-rolled retry loop.
Closes-Bug: #1524656
Change-Id: I0fff95b434a6572efd2af3ac2ec89b5772459cd5
Another take on the problem described
in 5b4dd3c, ie. Manila Tempest update
in
6b8319e32a (diff-e0705abec56bf0f83781d686e109d63eR63)
Instead of checking out $MANILA_TEMPEST_COMMIT
blindly (ie. even if it's unset), we add a
fallback to the Tempest commit used prior to
5b4dd3c.
Change-Id: Idec3924a1b5476683e5520f83df8561d0bd0ccfd
Closes-Bug: #1524642
Some of the loop control variables are global. This as expected has
lead to corruption of their values, and produced undesired results.
Fix this issue by setting the scope of these variables to local.
Closes Bug: #1523348
Change-Id: I0f5676c5a0b97d3e027a1e7677b4b5a21470913b
The tempest code base used by the CI is outdated. So update tempest
tests as done for the generic driver CI in the Manila code base,
6b8319e32a (diff-e0705abec56bf0f83781d686e109d63eR63)
Change-Id: Ide7966b44482dd13aadd5ef34a97c980e5752bfb
Closes-Bug: #1519012
This patch does the following:
* Moved variable setting part from plugin.sh to settings file.
* By default all Gluster-[Glance|Nova|Cinder|Manila] integrations
disabled. Look at README file to know how to enable.
* Keeping CINDER_ENABLED_BACKENDS intact when
CONFIGURE_GLUSTERFS_CINDER=False (Bug #1500381)
* Renamed CONFIGURE_GLUSTERFS_BACKUP to
CONFIGURE_GLUSTERFS_CINDER_BACKUP
* Avoid setting unnecessary variable when speicific configuraiton
is disabled.
* Documented the steps to enable in README.md file of this project.
Closes-Bug: #1500381
Depends-On: Id6967499729dfaa12d8a338d8f72471ebc90fb0d
Change-Id: I36f35f8af8e3491c8b0cffb40ba3980b7beab5df
The newly introduced Tempest config option,
'capability_snapshot_support' allows glusterfs_native driver
that can support snapshot support to run with snapshot Tempest tests
disabled. Set this option to True to let the glusterfs_native driver
CI not run snapshot tests - the present status-quo of the
glusterfs_native driver CI, and yet succeed to run.
Change-Id: I7e605502a9d6d3a42a26313a7c3bbb53ec08d8bc
This patch modifies devstack-plugin-glusterfs code to install
glusterfs 3.7 for manila specific jobs.
Change-Id: Ica4a44cd8dfe65a2330f65a1dcbb69a24fb2c805
The glusterfs (NFS) driver CI that currently uses directly mapped
layout sometimes fails since the backend GlusterFS volume within
which the driver creates shares does not have sufficient space to
allow Tempest to create shares for testing.
Closes-Bug: #1498792
Change-Id: If9ac508834637908bb91df55e856e08bca01e88f
The tempest config option, "storage_protocol" for glusterfs_native
driver CI needs to be "glusterfs" instead of "GLUSTERFS", as the
glusterfs_native driver reports its storage_protocol to be
"glusterfs" using update_share_stats share driver method.
Closes-Bug: #1498624
Change-Id: I1031cfaeab629b5aab316e611e9aae1833cf857b
During glusterfs (NFS) CI run, the extra spec "snapshot_support" used
for the default share-type is set to "True" even though the CI tests
the glusterfs backend with directory based share layout scheme that
does not support snapshot. So set the extra_spec to False which would
allow the Manila scheduler to pick up the glusterfs backend as a valid
host.
Change-Id: I7357417774cd16a2c114abd48a7bdb65a9eefc51
Closes-Bug: #1498399
Disable Tempest configuration that creates "ip" access type
rules for Manila CI using "glusterfs_native" driver.
Change-Id: I14061af63c3fddec5ec727f24c3aebba76080e11
Closes-Bug: #1498313
The two glusterfs drivers in Manila do not yet support consistency
groups feature. So disable the related Tempest tests during the
CI runs of the two drivers.
Change-Id: I07e860971451c4aa875272a34ebf845603f9f0be
Closes-Bug: #1498101
This patch modifies the pre_, post_ test_hook.sh scripts to use
new tempest plugin interface as per below patch:
https://review.openstack.org/#/c/201955/
Closes-Bug: #1493802
Change-Id: I267fd14eb6324e533b32ae0bea2f3ecafac6fbc4
As we modified Manila-GlusterFS job definition to use manila/pre_,
post_ test_hook scripts, now devstack/pre_, post_ test_hook scripts
not required.
This patch removes devstack/pre_, post_ test_hook scripts in
devstack/ directory.
Change-Id: I52d962a231c1b2bbc89a160fdc65ea218170a241
This patch modifies the pre_test_hook.sh script to set
ENABLE_ISOLATED_METADATA in localrc for Neutron configuration.
Closes-Bug: #1486550
Change-Id: I7708c29998e5c0f46770c54e0c7d184aed388821
This patch avoids creation of zero sized glusterfs log files by
changing the file permissions from 600 to 755.
Change-Id: I2c88781052f5cb334de21ffe1f98f13240820fa5
This patch allows devstack-plugin-glusterfs to configure GlusterFS
as Cinder backup target. Below are the new configuration options
added:
* CONFIGURE_GLUSTERFS_BACKUP (Set it to True to enable glusterfs backup)
* CINDER_GLUSTERFS_BACKUP_SHARE (ex: 127.0.0.1:/backup_vol)
Depends-On: I4f0c36cdaa7cc417cb26bc1e908c6d107a71da35
Change-Id: I03f1daa0c32fda20dc1900ed73e6ad586aee37a7
Add pre_test_hook and post_test_hook scripts that enables Manila to
be setup with one of the GlusterFS based drivers as the backend
share_drive, and allows Tempest test cases to run with the Manila
setup.
Change-Id: I60c715350b8e53a7e19667574ce0e5ef02e51f22
This patch enables GlusterFS as a backend for Manila. This
patch also introduces two new configuration parameters:
* CONFIGURE_GLUSTERFS_MANILA - set to 'True', to enable GlusterFS
as a backend for Manila.
* GLUSTERFS_MANILA_DRIVER_TYPE - set Manila GlusterFS backend type
to either 'glusterfs' or 'glusterfs-native'.
Change-Id: I53e5b9e88b6ebc131c64dabc421875c06a3fafd4
This patch enables GlusterFS as a backend for Nova. This
patch also introduces two new configuration parameters
* CONFIGURE_GLUSTERFS_NOVA - set to 'True', to enable GlusterFS
as a backend for Nova.
* NOVA_GLUSTERFS_SHARE - which specifies the GlusterFS share
to store compute instances.
Change-Id: Iaebc0aff704d1203b91967af06b06bb08fde51bd
This patch enables GlusterFS as a backend for Glance. This
patch introduces two new configuration parameters:
* CONFIGURE_GLUSTERFS_GLANCE - set to 'True', to enable GlusterFS
as a backend for Glance. By default set to True.
* GLANCE_GLUSTERFS_SHARE - which specifies the GlusterFS share
to store glance images.
Change-Id: I613e4c7a3e359235f5d54abc820df95b521b8697
Patch @ https://review.openstack.org/#/c/164527/14 changed the default
prov type to thin, which causes the volume backup tests in tempest
to fail, as we don't yet support backup for thin(qcow2) files.
This patch fixes the issue by making the default prov type as thick
for the CI job
Change-Id: I9edd0e0d0a82f08305b62951a87cf45b4df8d2f7
Closes-bug: #1483126
This patch introduces a new configuration parameter (knob)
CONFIGURE_GLUSTERFS_CINDER to enable/disable glusterfs as a
backend for Cinder. And added below error conditions:
* glusterfs plugin enabled but CONFIGURE_GLUSTERFS_CINDER set to
False
* CONFIGURE_GLUSTERFS_CINDER set to True, but CINDER_ENABLED_BACKENDS
doesn't have at least one backend of type glusterfs.
Change-Id: Ic802a2f2bbbdc1af04fd1220d2055be1e853fef8
