ceph/qa
Joao Eduardo Luis 0b30a1538a qa: add simple and dirty script to find ports being used
Seriously, having this is way better than realizing that one needs to
find an unused port each time a new test is created.

It's far from a perfect script. It's downright not elegant.

Signed-off-by: Joao Eduardo Luis <joao@suse.de>
2017-11-22 16:58:34 +00:00
..
archs
btrfs
cephfs qa/cephfs: test ec data pool 2017-10-23 21:11:24 -05:00
client
clusters
config
debug
distros tests: CentOS 7.4 is now the latest 2017-09-18 18:01:17 +02:00
erasure-code
libceph
machine_types
mds
mon/bootstrap
mon_kv_backend
nightlies
objectstore qa/objectstore/bluestore*: less debug output 2017-09-05 17:43:28 -04:00
objectstore_cephfs
overrides
packages
qa_scripts
rbd qa/suites/krbd: add krbd BLKROSET test 2017-10-31 13:40:16 +01:00
releases qa/suites/rados/upgrade: jewel-x -> luminous-x 2017-08-28 23:11:27 -04:00
rgw_frontend qa/rgw: add beast frontend to some rgw suites 2017-10-27 11:20:52 -04:00
rgw_pool_type
standalone Merge pull request #18449 from dzafman/wip-zafman-misc 2017-10-27 10:21:25 -07:00
suites Merge pull request #17977 from cbodley/wip-rgw-beast-qa 2017-11-16 15:14:28 -05:00
tasks Merge PR #18274 into master 2017-11-20 21:48:19 -08:00
timezone
workunits qa/workunits/rbd: wait for status propagated only if daemon started 2017-11-21 22:29:16 +02:00
.gitignore
find-used-ports.sh qa: add simple and dirty script to find ports being used 2017-11-22 16:58:34 +00:00
loopall.sh
Makefile
README
run_xfstests_qemu.sh
run_xfstests-obsolete.sh
run_xfstests.sh qa/run_xfstests.sh: quit building xfstests on test nodes 2017-08-29 16:08:27 +02:00
run-standalone.sh qa: respect $TEMPDIR 2017-09-15 12:19:50 +08: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

Symlinks are okay.

The teuthology code can be found in https://github.com/ceph/teuthology.git