ceph/qa
Kefu Chai 83d74a72f3
Merge pull request #29800 from Devp00l/wip-41372
mgr/dashboard: CephFS tab component

Reviewed-by: Tiago Melo <tmelo@suse.com>
Reviewed-by: Volker Theile <vtheile@suse.com>
2019-09-22 12:08:58 +08:00
..
archs
btrfs
cephfs
client
clusters
config
crontab qa/tests - upped priority for upgrades on master, otherwise they never lock nodes for testing and fail 2019-08-14 09:43:02 -07:00
debug
distros
erasure-code
libceph
machine_types
mds
mon/bootstrap
msgr
nightlies
objectstore
objectstore_cephfs
overrides
packages
qa_scripts
rbd Merge pull request #30502 from idryomov/wip-krbd-avoid-hexdump-s 2019-09-21 11:12:28 +02:00
releases
rgw_frontend
rgw_pool_type
standalone osd: Replace active/pending scrub tracking for local/remote 2019-09-10 13:33:27 -07:00
suites qa/rgw: rgw/website suite uses subdomain calling format 2019-09-17 08:24:52 -04:00
tasks Merge pull request #29800 from Devp00l/wip-41372 2019-09-22 12:08:58 +08:00
timezone
workunits Merge pull request #30363 from idryomov/wip-krbd-huge-osdmap 2019-09-13 22:35:57 +02:00
.gitignore
Makefile
README
find-used-ports.sh
loopall.sh
run-standalone.sh qa/run-standalone.sh: fix python path 2019-08-19 12:33:05 -05:00
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