ceph/qa
Sage Weil 70ba58e9e8 Merge PR #22554 into master
* refs/pull/22554/head:
	qa/standalone/ceph-helpers.sh: Fixing comment for wait_for_health()
	tests: Protecting rados bench against endless loop
	qa/standalone/ceph-helpers.sh: Defining custom timeout for wait_for_clean()

Reviewed-by: Piotr Dałek <piotr.dalek@corp.ovh.com>
Reviewed-by: Willem Jan Withagen <wjw@digiware.nl>
2018-06-14 13:04:56 -05:00
..
archs
btrfs
cephfs mds: check for session import race 2018-05-14 12:52:50 -07:00
client
clusters
config
crontab qa/tests: removed all jewel runs and reduced runs on ovh 2018-06-12 09:49:09 -07:00
debug
distros tests/qa: adding rados/.. dirs 2018-05-11 14:03:15 -07:00
erasure-code
libceph
machine_types tests/qa - fix mimic subset for nightlies 2018-05-10 07:39:51 -07:00
mds
mon/bootstrap
mon_kv_backend
nightlies
objectstore
objectstore_cephfs
overrides qa/suites/rados: add coverage for osd_recovery_max_single_start > 1 2018-04-20 19:42:15 -04:00
packages
qa_scripts
rbd
releases
rgw_frontend
rgw_pool_type qa/rgw: disable testing on ec-cache pools 2018-05-21 13:29:01 -04:00
standalone qa/standalone/ceph-helpers.sh: Fixing comment for wait_for_health() 2018-06-14 11:06:52 +02:00
suites qa/suites/rados/upgrade: remove stray link 2018-06-07 11:25:55 -05:00
tasks Merge pull request #22303 from ricardoasmarques/wip-help-menu 2018-06-14 15:56:39 +02:00
timezone
workunits rbd: interlock object-map/fast-diff features together 2018-06-12 09:25:55 +08:00
.gitignore
find-used-ports.sh
loopall.sh
Makefile
README
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