ceph/qa
Sage Weil dc7a2aaf7a erasure-code: ruleset-* -> crush-*
1) ruleset is an obsolete term, and
2) crush-{rule,failure-domain,...} is more descriptive.

Note that we are changing the names of the erasure code profile keys
from ruleset-* to crush-*.  We will update this on upgrade when the
luminous flag is set, but that means that during mon upgrade you cannot
create EC pools that use these fields.

When the upgrade completes (users sets require_osd_release = luminous)
existing ec profiles are updated automatically.

Signed-off-by: Sage Weil <sage@redhat.com>
2017-07-06 15:01:03 -04:00
..
archs
btrfs
ceph-deploy-overrides
cephfs
client
clusters osd: do not default-abort on leaked pg refs 2017-05-26 14:43:26 -07:00
config
config_options
debug
distros
erasure-code erasure-code: ruleset-* -> crush-* 2017-07-06 15:01:03 -04:00
libceph
machine_types Removed all 'default_idle_timeout' due to chnage in rwg task 2017-06-01 14:01:30 -07:00
mds
mon/bootstrap
mon_kv_backend
nightlies
objectstore qa: stop testing btrfs 2017-06-30 09:28:03 -04:00
objectstore_cephfs
overrides
packages
qa_scripts
rbd
releases osd: replace require_*_osds flags with require_osd_release field 2017-05-29 21:33:17 -04:00
rgw_pool_type erasure-code: ruleset-* -> crush-* 2017-07-06 15:01:03 -04:00
suites erasure-code: ruleset-* -> crush-* 2017-07-06 15:01:03 -04:00
tasks erasure-code: ruleset-* -> crush-* 2017-07-06 15:01:03 -04:00
timezone
workunits erasure-code: ruleset-* -> crush-* 2017-07-06 15:01:03 -04:00
.gitignore
loopall.sh
Makefile
README
run_xfstests_krbd.sh
run_xfstests_qemu.sh
run_xfstests-obsolete.sh
run_xfstests.sh
runallonce.sh
runoncfuse.sh
runonkclient.sh
setup-chroot.sh
tox.ini

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