ceph/qa
Sage Weil 1ab352dd31 qa/tasks/ceph.py: move methods from teuthology.git into ceph.py directly; support mon bind * options
Having these live in teuthology.git is silly, since they are only consumed
by the ceph task, and it is hard to revise the behavior.

Revise the behavior by adding mon_bind_* options.

Signed-off-by: Sage Weil <sage@redhat.com>
2019-01-03 11:17:31 -06:00
..
archs
btrfs
cephfs qa/suites: fix bluestore links 2018-12-05 10:30:14 -06:00
client
clusters
config
crontab qa/tests: added "-n 7" to make sure mimic-x runs on built master branch 2018-11-10 10:18:49 -08:00
debug
distros qa/tests: update links for centos latest to point to 7.5 2018-11-01 11:09:12 -07:00
erasure-code
libceph
machine_types
mds
mon/bootstrap
mon_kv_backend
nightlies
objectstore qa/objectstore: bluestore -> bluestore-{bitmap,stupid} 2018-12-04 14:05:49 -06:00
objectstore_cephfs qa/suites: fix bluestore links 2018-12-05 10:30:14 -06:00
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 qa/suites/rados/upgrade: set require-osd-release to nautilus 2018-11-29 14:35:17 +08:00
rgw_frontend
rgw_pool_type
standalone qa/standalone/mon/misc.sh: tweak test to be more robust 2019-01-03 11:17:31 -06:00
suites qa/suites/rados/upgrade: spread mons a bit 2019-01-03 11:17:31 -06:00
tasks qa/tasks/ceph.py: move methods from teuthology.git into ceph.py directly; support mon bind * options 2019-01-03 11:17:31 -06:00
timezone
workunits qa/workunits/cephtool: fix blacklist test 2018-12-21 15:31:32 -06: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