Ceph is a distributed object, block, and file storage platform
Go to file
John Spray 951d6c297d tasks/cephfs: use set_conf() from test case class
...because this is the one that will store up
changes to roll back during teardown.

Doing this makes it easy to run lots of test cases
togeher in a single teuthology run, raher than
setting up/tearing down the ceph cluster for each
on.

Signed-off-by: John Spray <john.spray@redhat.com>
2015-01-09 10:09:52 +00:00
ceph-deploy-overrides added a test to use single disk for both data and journal. 2014-09-02 23:48:34 -07:00
clusters kcephfs/thrash: add standby mds 2014-07-31 21:22:09 -07:00
config_options added config_options to enable adding ceph config file entries to ceph-deploy task 2014-08-28 18:48:40 -07:00
debug turn on mds & client debugging 2013-10-15 12:05:28 -07:00
distros Added RHEL7 to matrix. 2014-09-11 11:07:54 -07:00
erasure-code Fixes #10269 http://tracker.ceph.com/issues/10269 2014-12-08 11:12:04 -08:00
fs xfs: enable sloppy crc 2013-10-02 13:30:13 -07:00
machine_types Update vps.yaml 2014-12-02 09:25:00 -08:00
overrides ceph config data goes in conf, not config 2013-04-26 11:25:14 -07:00
rgw_pool_type rgw: mark ec related rgw suites as slow backend 2014-10-20 14:50:48 -07:00
suites drop tiobench tests 2015-01-06 08:59:14 -07:00
tasks tasks/cephfs: use set_conf() from test case class 2015-01-09 10:09:52 +00:00
.gitignore gitignore: ignore vim temp files 2014-08-21 23:09:00 +01: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