| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Validate whether creation of maximum supported
blockvolumes doesn't have any impact to the
functionality of gluster-block.
Change-Id: I2a1503f527da2d1d916e87ce154e88bf9b5e1fa8
|
|
|
|
|
|
|
| |
Add a device, check there are no bricks on the device and verify
the device deletion.
Change-Id: I0e6adafb730e8d82926ce4e1d7b6b3c4799efc1b
|
|
|
|
|
|
|
|
|
| |
By default, we create replica-3 file volumes.
And when we have more than 3 Heketi nodes located in unique zones,
we should check that our file volume is located in 3 unique zones,
not bigger. So, fix this bug.
Change-Id: Id82626425473f5e480ad73b0e17b7a0d675ba8ba
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix consists of -
- Use "**kwargs" approach in the "heketi_node_list"
function as it is done in lots of other functions.
- Parse the CLI output in the "heketi_node_list" function
using regex instead of the splitting and stripping strings.
- Combine test cases related to the same feature into one
module - test_heketi_node_operations.py
- Remove redundant checks which already exist in common
libraries.
- Remove unnecessary logging.
Change-Id: I815ddfbbacb765140229e7630ec87a6bbaa6255b
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
|
|
| |
Stop glusterd on 2 of the nodes/pods in the cluster containing alteast
5 gluster nodes and verify creation of volume using heketi.
Change-Id: I94570f5bbfa20c19f11f4e14e29d2b1a40612fc5
|
|
|
|
|
|
|
|
|
|
| |
Add 10 test cases for testing Heketi zones feature.
To make all the Heketi zones test cases run in the single suite using the same
cluster set 'common.allow_heketi_zones_update' config option to "True" value.
By default it is set to "False" and only small set of test cases can run
having such value.
Change-Id: I69a1f7c96c9f52a06134e715e113ccd9b06764e6
|
|
|
|
|
|
|
|
|
|
|
| |
In test case when we use large disk size, heketi takes time to create
volume and due to timeout it gives error.
Add fix in such test cases to check if volume created after getting
an exception, get details of such volumes or raise exception in case
it fails to create volume.
Change-Id: I1c23a8c6558c23edf8947771e4f41a4bd3ffd66a
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
| |
Change-Id: I5886680a0d5666c68c677893e0fb327be0e80760
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
|
|
|
|
|
|
|
| |
Add test case where we set and test Heketi config options
to limit lower/upper allowed volume size
and amount of bricks per volume.
Change-Id: Ifb5cf64bba34dbf4e89f2fe9364263385a04cfa7
|
|
|
|
|
|
|
|
| |
Verify creation of replica 2 volume and validate the bricks
created in gluster backend are same.
Change-Id: I9fcc090e909d9bf578cf8eca6e12e4f785140e3f
Signed-off-by: Sri Vignesh <sselvan@redhat.com>
|
|
|
|
|
|
|
| |
Validate creation of block volume with name
Change-Id: I08ee31201d42a95f8a829eb54ce68421903fdbbf
Signed-off-by: Sri Vignesh <sselvan@redhat.com>
|
|
|
|
|
|
|
| |
Add new TC where we verify given heketi mount point in volume info
is working.
Change-Id: Ia03af9ea6729cdfadf663abe46db7184a8b6fe2c
|
|
|
|
|
|
|
|
| |
validate creation and deletion of
distributed-replicated bhv.
Change-Id: Ia42ace7e5be53fa7a00f88378575205e7fd5ba97
Signed-off-by: Sri Vignesh <sselvan@redhat.com>
|
|
|
|
|
|
|
|
| |
validate block volume creation with
different auth values
Change-Id: I820f65a5aaa5adc6cb58b16b18b6c93b22177d45
Signed-off-by: Sri Vignesh <sselvan@redhat.com>
|
|
|
|
| |
Change-Id: I26c750c68055c6cc50de8015942d0d9725819aaf
|
|
|
|
|
|
|
|
| |
This test case validates bhv options like
features.shard,shard.size,shd max threads,
and performance related ones
Change-Id: I991f13e1b744486281e98813f169630a666eeb59
|
|
|
|
|
|
|
|
| |
Create 3 volumes using heketi-cli command, verify their presence in
heketi topology info, delete 2 volumes and validate their deletions
and presence of 3rd volume in heketi topology info
Change-Id: I78298d2aec21ff8031ff01efd53f11ba31e269c9
|
|
|
|
|
| |
Change-Id: I7ead23c46a472fee70d684c45f32f5e4efb0674f
Signed-off-by: kasturiNarra <knarra@redhat.com>
|
|
|
|
|
|
|
|
| |
It happens that heketi client located out of the Heketi POD may fail
not reaching the server side. So, add back-up approach where we run
Heketi commands on a Heketi POD when main commands fail.
Change-Id: Ie6ae5be82082f34426f9288b02575e3abd4940f5
|
|
|
|
|
|
|
| |
Rename TC modules to appropriate name and move them to correct
component.
Change-Id: I87c9bb7822c17c955dd9c2d780ef08e4d4e0d7ee
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Required steps to run test cases using py3:
1) Install py3
2) Install 'tox' package using "pip3"
3) Run test cases using tox package installed via pip3
Note that full py3 support is not tested yet. It only allows you to run
it on py3 not providing any guarantees.
Example:
$ python3 -m tox -e functional3 -- \
glusto -c /path/to/the/config/file.yaml \
'--pytest=-v -rsx tests -k test_glusterblock_logs'
Change-Id: I610faac0b75364c401734b6f892649893ca2320e
|
|
|
|
|
|
|
|
|
|
|
|
| |
Move all the files of 'cns-libs/cnslibs/common' dir
to the 'openshift-storage-libs/openshiftstoragelibs',
because 'common' is the only dir there, which doesn't really makes sense.
And "cns" is old project name, so, replace it with
"openshift-storage-libs".
Also, fix all the imports of these libs.
Change-Id: Ife00a73554e73b21b214b15016b0c8dbbf423446
|
|
Move all the files of 'tests/functional/common/' dir
to the 'tests/functional/', because 'common' is the only
dir there, which doesn't really makes sense.
Do the same about 'tests/functional/common/heketi/heketi_tests'
and 'tests/functional/common/heketi/'.
Change-Id: I1fa55e2e7bf09e9b9115629b06e1fd160e291a36
|