Ceph is a distributed object, block, and file storage platform
Go to file
John Spray acf33b5cdb suites/fs: enable debug on recovery tests
Signed-off-by: John Spray <john.spray@redhat.com>
2014-10-08 16:34:02 +01:00
ceph-deploy-overrides
clusters
config_options
debug
distros
erasure-code Merge remote-tracking branch 'origin/giant' into wip-merge 2014-10-01 18:17:01 +01:00
fs
machine_types
overrides
rgw_pool_type
suites suites/fs: enable debug on recovery tests 2014-10-08 16:34:02 +01:00
tasks erasure-code: unfound test needs a non empty file 2014-10-02 08:06:42 +02:00
.gitignore
README

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