ceph/qa
Venky Shankar ef3f512306
Merge pull request #51766 from zhsgao/mds_clear_session_failed
mds: session in the importing state cannot be cleared if an export subtree task is interrupted while the state of importer is acking

Reviewed-by: Venky Shankar <vshankar@redhat.com>
2024-11-14 12:38:35 +05:30
..
archs
cephfs Merge PR #60386 into main 2024-10-25 12:21:34 -04:00
client
clusters
config qa/config/seastore: enable all subsystem debug 2024-08-29 08:34:49 +00:00
crontab qa/crontab: Add weekly crimson-rados suites 2024-09-08 12:14:03 +00:00
debug
distros qa/distros: reinstall nvme-cli on centos 9 nodes 2024-08-22 15:30:44 -04:00
erasure-code
libceph
machine_types
mds
mgr_ttl_cache
mon/bootstrap
mon_election
msgr
nightlies
objectstore
objectstore_cephfs
objectstore_debug
overrides
packages
qa_scripts
rbd qa: cover a custom object size in krbd_discard_granularity.t 2024-08-09 18:00:40 +02:00
releases
rgw
rgw_bucket_sharding
rgw_frontend
rgw_pool_type
standalone Merge pull request #60071 from shraddhaag/fix-mon-cluster-log-test 2024-11-06 07:34:58 -08:00
suites Merge pull request #60067 from VallariAg/wip-nvmeof-healthcheck 2024-11-14 08:40:43 +05:30
tasks qa: add test for importer's unexpected client eviction after an export subtree task is interrupted 2024-11-13 17:39:16 +08:00
timezone
workunits Merge pull request #59483 from kamoltat/wip-ksirivad-exit-stretch-mode 2024-11-05 13:07:06 -05:00
.gitignore
.qa
CMakeLists.txt
find-used-ports.sh
loopall.sh
lsan.supp
Makefile os: remove unused btrfs_ioctl.h and tests 2024-09-17 10:07:54 -04:00
mypy.ini
README Add cosbench deprecation warning to qa/README 2024-10-10 11:24:32 +01:00
run_xfstests_qemu.sh
run_xfstests-obsolete.sh
run_xfstests.sh
run-standalone.sh
runallonce.sh
runoncfuse.sh
runonkclient.sh
setup-chroot.sh
test_import.py
tox.ini
valgrind.supp

ceph-qa-suite
-------------

clusters/    - some predefined cluster layouts
suites/      - set suite

The suites directory has a hierarchical collection of tests.  This can be
freeform, but generally follows the convention of

  suites/<test suite name>/<test group>/...

A test is described by a yaml fragment.

A test can exist as a single .yaml file in the directory tree.  For example:

 suites/foo/one.yaml
 suites/foo/two.yaml

is a simple group of two tests.

A directory with a magic '+' file represents a test that combines all
other items in the directory into a single yaml fragment.  For example:

 suites/foo/bar/+
 suites/foo/bar/a.yaml
 suites/foo/bar/b.yaml
 suites/foo/bar/c.yaml

is a single test consisting of a + b + c.

A directory with a magic '%' file represents a test matrix formed from
all other items in the directory.  For example,

 suites/baz/%
 suites/baz/a.yaml
 suites/baz/b/b1.yaml
 suites/baz/b/b2.yaml
 suites/baz/c.yaml
 suites/baz/d/d1.yaml
 suites/baz/d/d2.yaml

is a 4-dimensional test matrix.  Two dimensions (a, c) are trivial (1
item), so this is really 2x2 = 4 tests, which are

  a + b1 + c + d1
  a + b1 + c + d2
  a + b2 + c + d1
  a + b2 + c + d2

A directory with a magic '$' file, or a directory whose name ends with '$',
represents a test where one of the non-magic items is chosen randomly.  For
example, both

 suites/foo/$
 suites/foo/a.yaml
 suites/foo/b.yaml
 suites/foo/c.yaml

and

 suites/foo$/a.yaml
 suites/foo$/b.yaml
 suites/foo$/c.yaml

is a single test, either a, b or c.  This can be used in conjunction with the
'%' file in the same (see below) or other directories to run a series of tests
without causing an unwanted increase in the total number of jobs run.

Symlinks are okay.

One particular use of symlinks is to combine '%' and the latter form of '$'
feature.  Consider supported_distros directory containing fragments that define
os_type and os_version:

 supported_distros/%
 supported_distros/centos.yaml
 supported_distros/rhel.yaml
 supported_distros/ubuntu.yaml

A test that links supported_distros as distros (a name that doesn't end with
'$') will be run three times: on centos, rhel and ubuntu.  A test that links
supported_distros as distros$ will be run just once: either on centos, rhel or
ubuntu, chosen randomly.

The teuthology code can be found in https://github.com/ceph/teuthology.git

Note: The performance suites clone CBT from master here: https://github.com/ceph/cbt.git
CBT will not support cosbench beyond release tag v0.3, therefore no qa suite should use cosbench.
cosbench support has been removed from qa/tasks/cbt.py.