ceph/qa
Kefu Chai b4a5f76243 qa: add librados3 to exclude list of pre-nautilus install tasks
Signed-off-by: Kefu Chai <kchai@redhat.com>
2018-11-02 00:15:31 +08:00
..
archs
btrfs
cephfs
client
clusters
config
crontab Merge pull request #24139 from tchaikov/wip-fix-typos 2018-09-21 16:56:31 +08:00
debug
distros qa/distros: add openSUSE Leap 42.3 and 15.0 2018-10-02 21:36:49 +02:00
erasure-code qa/suites/rados/thrash-erasure-code: add clay 4+2 2018-09-27 18:56:21 +08:00
libceph
machine_types
mds
mon/bootstrap
mon_kv_backend
nightlies
objectstore
objectstore_cephfs
overrides
packages qa: s/librados2/librados3/ 2018-11-02 00:15:31 +08:00
qa_scripts qa: s/librados2/librados3/ 2018-11-02 00:15:31 +08:00
rbd
releases
rgw_frontend
rgw_pool_type
standalone Merge PR #24809 into master 2018-10-30 15:09:45 -05:00
suites qa: add librados3 to exclude list of pre-nautilus install tasks 2018-11-02 00:15:31 +08:00
tasks Merge pull request #22833 from rjfd/wip-dashboard-jwt 2018-10-30 10:50:20 +01:00
timezone
workunits qa: update test_envlibrados_for_rocksdb.sh for libradospp split 2018-11-02 00:15:31 +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