ceph/qa
Sage Weil 26f00dd67c qa/suites: mon warn on pool no app = false for api tests
Among other things, the list.cc tests set pg_num which waits for cluster
healthy.

Signed-off-by: Sage Weil <sage@redhat.com>
2018-04-04 08:26:58 -05:00
..
archs
btrfs
cephfs
client
clusters
config
crontab test:qa:infra - teuthology crontab items as of 3/27/18 2018-03-29 06:31:03 -07:00
debug
distros
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_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 test: Replace bc command with printf command 2018-03-22 17:19:56 -07:00
suites qa/suites: mon warn on pool no app = false for api tests 2018-04-04 08:26:58 -05:00
tasks Merge PR #21180 into master 2018-04-03 06:51:18 -07:00
timezone
workunits Merge pull request #20460 from colletj/v1_image_creation_disallow 2018-04-03 09:18:39 -04: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
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