ceph/qa
Sebastian Wagner bbd18f1986
Merge pull request #32049 from mgfritch/wip-cd-timeout
cephadm: add ability to specify a timeout

Reviewed-by: Sebastian Wagner <sebastian.wagner@suse.com>
2020-01-17 08:32:06 +01:00
..
archs
btrfs
cephfs qa/cephfs: don't run kclient tests on latest RHEL 2020-01-13 10:27:02 +05:30
client
clusters
config
crontab
debug
distros
erasure-code
libceph
machine_types qa: remove force-branch from overrides of s3-tests 2020-01-02 09:16:43 -05:00
mds
mon/bootstrap
msgr
nightlies
objectstore
objectstore_cephfs
overrides
packages Merge PR #32232 into master 2019-12-24 08:17:35 -06:00
qa_scripts
rbd
releases
rgw_frontend
rgw_pool_type qa: remove force-branch from overrides of s3-tests 2020-01-02 09:16:43 -05:00
standalone test: Sort pool list because the order isn't guaranteed from "balancer pool ls" 2020-01-06 21:35:19 -08:00
suites Merge pull request #32620 from cbodley/wip-qa-rgw-hadoop-versions 2020-01-14 13:36:29 -05:00
tasks Merge PR #32411 into master 2020-01-15 08:39:48 -06:00
timezone
workunits Merge pull request #32049 from mgfritch/wip-cd-timeout 2020-01-17 08:32:06 +01:00
.gitignore
CMakeLists.txt
Makefile
README
find-used-ports.sh
loopall.sh
run-standalone.sh
run_xfstests-obsolete.sh
run_xfstests.sh
run_xfstests_qemu.sh
runallonce.sh
runoncfuse.sh
runonkclient.sh
setup-chroot.sh
tox.ini
valgrind.supp

README

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 represents a test where one of the other
items is chosen randomly. For example,

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

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

Symlinks are okay.

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