ceph/qa
Sridhar Seshasayee b637909a91
Merge pull request #38007 from sseshasa/wip-qa-rados-perf-scheduler
qa/suite/rados: Introduce "scheduler" directory within rados perf suite.

Reviewed-by: Neha Ojha <nojha@redhat.com>
Reviewed-by: Samuel Just <sjust@redhat.com>
2020-11-16 12:56:09 +05:30
..
archs
btrfs
cephfs qa: use more OSDs for workload tests 2020-11-03 13:00:42 -08:00
client
clusters
config
crontab qa: remove kcephfs suite 2020-11-03 13:00:36 -08:00
debug
distros Merge pull request #37922 from mgfritch/project-kubic 2020-11-12 10:40:24 +08:00
erasure-code qa: drop hammer branch qa tests 2020-10-15 17:32:06 +05:30
libceph
machine_types qa: drop hammer branch qa tests 2020-10-15 17:32:06 +05:30
mds
mon/bootstrap
mon_election
msgr
nightlies
objectstore
objectstore_cephfs
overrides
packages
qa_scripts
rbd rbd: make common options override krbd-specific options 2020-09-24 10:50:24 +02:00
releases
rgw_bucket_sharding
rgw_frontend
rgw_pool_type
standalone Merge pull request #37908 from dzafman/wip-47930 2020-11-16 01:00:56 +08:00
suites Merge pull request #38007 from sseshasa/wip-qa-rados-perf-scheduler 2020-11-16 12:56:09 +05:30
tasks Merge PR #34842 into master 2020-11-15 12:39:11 -08:00
timezone
workunits mgr/dashboard: fix cephadm e2e test failure on deleting OSDs 2020-11-12 17:20:48 +08:00
.gitignore
.teuthology_branch
CMakeLists.txt cmake: do not always add py3 to TOX_ENVS 2020-10-14 15:30:37 +08:00
find-used-ports.sh
loopall.sh
Makefile
mypy.ini
README
run_xfstests_qemu.sh
run_xfstests-obsolete.sh
run_xfstests.sh
run-standalone.sh
runallonce.sh
runoncfuse.sh
runonkclient.sh
setup-chroot.sh
test_import.py
tox.ini
valgrind.supp

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