Ceph is a distributed object, block, and file storage platform
Go to file
Yan, Zheng 75fc41c604 cephfs/test_auto_repair.py: flush journal after umount
When client capabilities get released, MDS may update corresponding
inodes' client writable range and mark those inodes dirty. The auto
repair test expects MDS to trim inodes from its cache, but MDS can't
trim dirty inodes. So we should flush journal after umount.

Fixes: #12172
Signed-off-by: Yan, Zheng <zyan@redhat.com>
(cherry picked from commit 835ad8b8f3)
2015-07-01 11:47:14 +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 add log-rotate configs to the userspace suite 2015-06-08 17:37:42 -07: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 Added RHEL7 to matrix. 2014-09-11 11:07:54 -07:00
erasure-code erasure-code: enable ec-rados-default.yaml 2015-03-25 17:33:31 +01:00
fs xfs: enable sloppy crc 2013-10-02 13:30:13 -07:00
machine_types Added script to schedule 1/14th part of rados 2015-05-19 13:44:36 -07:00
overrides overrides/short_pg_log: 30/50 was too short, make 100/200 2015-02-04 14:39:38 -08:00
rgw_pool_type rgw: mark ec related rgw suites as slow backend 2014-10-20 14:50:48 -07:00
suites upgrade-x: use compatible rados api tests 2015-06-15 15:47:48 -07:00
tasks cephfs/test_auto_repair.py: flush journal after umount 2015-07-01 11:47:14 +01:00
.gitignore ignore tox hidden dir 2015-02-26 11:18:28 -05:00
README README: update for new flexible structure. 2013-08-28 11:30:25 -07:00
tox.ini exclude the virtualenv from being linted in tox.ini 2015-02-26 16:22:58 -05: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