ceph/qa
Noah Watkins ea15b625f3 qa/mgr/selftest: handle always-on module fall out
need a non-always-on module. hello doesn't work because it isn't
installed. so switch to selftest.

Signed-off-by: Noah Watkins <nwatkins@redhat.com>
2018-08-28 13:45:58 -07:00
..
archs
btrfs
cephfs qa: use recent kernel to kernel build testing 2018-08-16 09:16:39 -07:00
client
clusters
config
crontab qa/tests: changed ceph qa email address to bypass dreamhost's spam filter 2018-08-06 13:59:21 -07:00
debug
distros
erasure-code
libceph
machine_types
mds
mon/bootstrap
mon_kv_backend
nightlies
objectstore
objectstore_cephfs
overrides
packages qa: do not install python3 packages in task.install 2018-08-03 17:02:51 +08:00
qa_scripts
rbd
releases
rgw_frontend
rgw_pool_type
standalone Merge pull request #23376 from dzafman/wip-25108 2018-08-23 13:23:55 -07:00
suites Merge PR #23439 into master 2018-08-25 13:04:58 -07:00
tasks qa/mgr/selftest: handle always-on module fall out 2018-08-28 13:45:58 -07:00
timezone
workunits test/rbd: Improve/update rbd-ggate 2018-08-21 14:16:49 +02:00
.gitignore
find-used-ports.sh
loopall.sh
Makefile
README
run_xfstests_qemu.sh
run_xfstests-obsolete.sh
run_xfstests.sh
run-standalone.sh qa/standalone/ceph-helpers.sh: fix mgr module path 2018-08-17 15:21:57 -07: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