Ceph is a distributed object, block, and file storage platform
Go to file
John Spray 9e202b44c8 tasks/cephfs: support old mdsmap command during setup
While Filesystem at large requires the new commands, for
use from the `ceph` task we must support old style commands,
as the ceph task is used to instantiate old clusters during
upgrade testing.

Fixes: #15124, #15049, #15106

Signed-off-by: John Spray <john.spray@redhat.com>
2016-03-15 16:52:49 +00:00
ceph-deploy-overrides
clusters erasure code: added shec's initial ceph-qa-suite 2015-07-01 15:58:22 +09:00
config suites/rados: test random queue options 2016-01-29 13:22:10 -05:00
config_options Reduced ammount of nodes from 4 to 3 2015-04-30 09:39:02 -07:00
debug openstack: add 15GB for debugging purposes 2015-11-26 22:10:24 +01:00
distros Merge pull request #854 from SUSE/wip-opensuse-distros 2016-03-04 09:22:53 +07:00
erasure-code Merge pull request #523 from dachary/wip-10887-shec 2015-08-22 23:24:49 +02:00
fs
machine_types Made rados runs in ovh call vps.yaml 2016-02-02 13:50:24 -08:00
overrides 3-size-2-min-size: keep 4 in during thrashing 2015-07-09 17:03:57 -07:00
packages packages: update for all the new debug packages we have in jewel 2016-03-10 17:21:23 -08:00
releases Added point-to-point suite 2016-01-27 14:41:17 -08:00
rgw_pool_type rgw: mark ec related rgw suites as slow backend 2014-10-20 14:50:48 -07:00
suites upgrade/client-upgrade: only use supported features for RBD tests 2016-03-13 16:32:34 -04:00
tasks tasks/cephfs: support old mdsmap command during setup 2016-03-15 16:52:49 +00:00
timezone timezone: add eastern, pacific, random timezone snippets 2015-09-18 17:29:31 -04:00
.gitignore ignore tox hidden dir 2015-02-26 11:18:28 -05:00
README
tox.ini do not ommit syntax errors in linter checks 2015-08-06 08:38:52 -04: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