Ceph is a distributed object, block, and file storage platform
Go to file
John Spray 8b846b9f2c tasks/cephfs: add vstart runner script
This is to allow running CephFSTestCase tests
against a vstart cluster, for much faster turnaround
during development than running teuthology against
built ceph packages.

Not everything will be runnable this way, but for
certain things like filesystem repair scenarios we
have everything we need within a vstart environment.

Signed-off-by: John Spray <john.spray@redhat.com>
2015-10-02 17:41:17 +01: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 erasure code: added shec's initial ceph-qa-suite 2015-07-01 15:58:22 +09:00
config_options Reduced ammount of nodes from 4 to 3 2015-04-30 09:39:02 -07:00
debug turn on mds & client debugging 2013-10-15 12:05:28 -07:00
distros do not duplicate CentOS 7 runs 2015-09-18 16:24:22 +02:00
erasure-code Merge pull request #523 from dachary/wip-10887-shec 2015-08-22 23:24:49 +02:00
fs xfs: enable sloppy crc 2013-10-02 13:30:13 -07:00
machine_types tasks/ceph_fuse.py: virtual machines need flexible mount timeout 2015-07-14 13:03:01 +02:00
overrides 3-size-2-min-size: keep 4 in during thrashing 2015-07-09 17:03:57 -07:00
releases releases/infernalis.yaml: final steps after infernalis upgrade 2015-09-24 23:37:35 -04:00
rgw_pool_type rgw: mark ec related rgw suites as slow backend 2014-10-20 14:50:48 -07:00
suites log-whitelist 'reached quota' for librados test.sh 2015-10-02 08:33:46 -04:00
tasks tasks/cephfs: add vstart runner script 2015-10-02 17:41:17 +01: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