ceph/qa
David Zafman 007cb45fe5 osd rados command: Change error name snapset_mismatch to snapset_error
Signed-off-by: David Zafman <dzafman@redhat.com>
2018-04-10 13:26:08 -07:00
..
archs
btrfs
cephfs Merge PR #19856 into master 2018-02-01 14:50:12 -08:00
client
clusters
config
crontab qa/tests - minor clean ups and made perf-suite run 3 times, so we can have more data points 2018-04-09 09:17:10 -07:00
debug
distros qa/suites/fs: use ubuntu_latest for libcephfs_java 2017-12-19 11:12:28 -06:00
erasure-code
libceph cleanup: src/.libs -> build/lib 2018-03-06 14:44:47 -06:00
machine_types Try crontab github connection 2018-03-22 13:18:47 -07:00
mds
mon/bootstrap
mon_kv_backend
nightlies
objectstore objectstore/bluestore.yaml: enable bdev discard 2018-02-21 00:00:52 +09:00
objectstore_cephfs
overrides
packages
qa_scripts
rbd qa: krbd whole-object-discard test 2018-03-07 12:06:33 +01:00
releases
rgw_frontend
rgw_pool_type
standalone osd rados command: Change error name snapset_mismatch to snapset_error 2018-04-10 13:26:08 -07:00
suites qa/suites/rados: Disable scrub backoff 2018-04-09 17:21:01 +10:00
tasks qa/tasks: wait_for_clean is called after ceph task as well after osd's are up, 2018-04-09 17:24:42 -07:00
timezone
workunits Merge PR #21039 into master 2018-04-09 21:33:15 -07:00
.gitignore
find-used-ports.sh
loopall.sh
Makefile
README Document the new '$' suite file 2018-03-23 00:02:11 +00:00
run_xfstests_qemu.sh
run_xfstests-obsolete.sh
run_xfstests.sh
run-standalone.sh qa/standalone: change PATH to allow finding sysctl 2018-04-06 04:18:22 +01:00
runallonce.sh
runoncfuse.sh
runonkclient.sh
setup-chroot.sh
tox.ini

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