ceph/qa
Sungmin Lee f81b1b61c9 qa: add validation stage for deduplication.py
To validate sample-dedup actually works, validate() runs
separated thread from sample-dedup and verifies
two following things.
1. check sample-dedup starts properly.
2. check references of all the chunk objects' in chunk tier
   exists in designated base pool.
This routune repeats for max_valication_cnt times while
sample-dedup is running. If it doesn't raise any fail while the loop,
we can pretend sample-dedup works accurately.
If not, assert() will stop this test.

In case that a reference of chunk object doesn't exist in base pool,
validate() gives a second chance after repairing it (chunk-repair op)
to deal with false-positive reference inconsistency.

Signed-off-by: Sungmin Lee <sung_min.lee@samsung.com>
2022-09-19 13:21:00 +09:00
..
archs
btrfs
cephfs qa: increase mds balancer debug 2022-06-13 08:03:42 -04:00
client
clusters
config qa/config: override bluestore_zero_block_detection default for rados suite tests 2022-05-27 13:36:18 -05:00
crontab qa/tests: Typos and spacing 2022-07-01 16:40:20 -04:00
debug
distros qa: Default to RHEL8.6 instead of 8.5 2022-06-15 14:13:35 -04:00
erasure-code
libceph
machine_types schedule_subset.sh: Default to ceph.git 2022-06-08 16:13:29 -04:00
mds
mgr_ttl_cache mgr: TTLCache basic implementation 2022-01-05 10:11:58 +01:00
mon/bootstrap
mon_election
msgr
nightlies
objectstore
objectstore_cephfs
objectstore_debug bluestore: Revert "os/bluestore: Add CoDel to BlueStore for Bufferbloat mitigation" 2022-04-25 12:33:45 -07:00
overrides Rename/re-symlink whitelist_*.yaml 2022-05-24 14:14:04 -06:00
packages
qa_scripts
rbd qa/suites/krbd: add rbd_default_map_options override coverage 2022-02-18 17:19:45 +01:00
releases
rgw rgw: add .yaml that configures s3tests branch for rgw suite 2022-07-12 16:21:27 -04:00
rgw_bucket_sharding
rgw_frontend
rgw_pool_type
standalone tests/osd: fix a test to follow an output formatting change 2022-08-04 15:46:11 +00:00
suites qa/suites/fs/upgrade: added upgrade_without_reducing_max_mds for testing the fail_fs option 2022-08-10 00:13:43 +05:30
tasks qa: add validation stage for deduplication.py 2022-09-19 13:21:00 +09:00
timezone
workunits qa: add test case for sample_dedup operation of dedup_tool 2022-08-26 00:52:01 +00:00
.gitignore
.qa qa: move .qa terminator 2022-02-03 10:08:30 -05:00
CMakeLists.txt
find-used-ports.sh
loopall.sh
Makefile
mypy.ini
README
run_xfstests_qemu.sh Merge pull request #44282 from orozery/qa-qemu-nbd-ide-interface 2022-01-25 15:06:14 +01:00
run_xfstests-obsolete.sh
run_xfstests.sh
run-standalone.sh
runallonce.sh
runoncfuse.sh
runonkclient.sh
setup-chroot.sh
test_import.py
tox.ini qa: fix teuthology master branch ref 2022-06-02 12:27:02 +02:00
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