Ceph is a distributed object, block, and file storage platform
Go to file
2014-03-18 13:55:13 -07:00
clusters add multi-region tests 2013-08-16 19:17:22 -07:00
debug turn on mds & client debugging 2013-10-15 12:05:28 -07:00
distros distros: test rhel/centos 6.5 instead of 6.4 2014-03-18 13:55:13 -07:00
fs xfs: enable sloppy crc 2013-10-02 13:30:13 -07:00
overrides ceph config data goes in conf, not config 2013-04-26 11:25:14 -07:00
suites symlink all distros facets to a common set of 'supported' targets 2014-03-18 13:39:13 -07:00
.gitignore .gitignore: ignore emacs backups 2011-07-05 02:45:02 -07:00
README README: update for new flexible structure. 2013-08-28 11:30:25 -07:00

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