Ceph is a distributed object, block, and file storage platform
Go to file
Sage Weil dccdb2eb0f tasks/ceph_manager: add bdev_inject_crash_probability support
Only do the failure injection 50% of the time; otherwise, just
kill as usual.

Signed-off-by: Sage Weil <sage@redhat.com>

# Conflicts:
#	tasks/ceph_manager.py
2016-09-21 17:07:28 -04:00
archs arch: teuthology must use aarch64, not arm64 2016-04-06 21:02:31 +02:00
ceph-deploy-overrides
clusters Fix review comments 2016-03-12 02:15:39 -05:00
config config: add osd_debug_verify_missing_on_start 2016-07-22 14:35:59 -07:00
config_options
debug openstack: add 15GB for debugging purposes 2015-11-26 22:10:24 +01:00
distros distros: add ubuntu 16.04 / xenial 2016-04-07 18:39:13 +02:00
erasure-code
fs rados: specify xfs 2016-04-14 14:31:44 -04:00
machine_types Reduce number of jobs for hammer branch 2016-07-25 08:53:29 -07:00
mon_kv_backend rados: vary mon kv backend 2016-05-15 19:20:32 -04:00
nightlies Added stderr to the log file in addition to stdout 2016-08-10 13:15:00 -07:00
objectstore tasks/ceph_manager: add bdev_inject_crash_probability support 2016-09-21 17:07:28 -04:00
overrides short_pg_log: double params to avoid failures from dup detection failure 2016-05-24 12:38:21 -07:00
packages Revert "packages.yaml: reflect python-ceph package split" 2016-08-23 18:36:23 +02:00
releases Initial check in for a complete jewel-x suite 2016-05-18 14:19:04 -07:00
rgw_pool_type
suites rados/basic/tasks/repair_test: enable bluestore error injection 2016-09-21 16:28:00 -04:00
tasks tasks/ceph_manager: add bdev_inject_crash_probability support 2016-09-21 17:07:28 -04:00
timezone timezone: add eastern, pacific, random timezone snippets 2015-09-18 17:29:31 -04:00
.gitignore
README
tox.ini tox.ini: exclude .tox dir from flake8 2016-07-28 14:44:54 -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