ceph/qa
xie xingguo afcb617dc9 osd/PrimaryLogPG: do not generate data digest for BlueStore by default
BlueStore enables CRC by default, so this is a dup and gains
no more benefits.

Turn this off by default, which is good for performance.

Signed-off-by: xie xingguo <xie.xingguo@zte.com.cn>
2017-09-13 12:17:16 +08:00
..
archs
btrfs
cephfs mds: MDS_DAMAGED to MDS_DAMAGE 2017-08-04 13:01:33 -07:00
client
clusters qa/clusters/fixed-[23]: 4 osds per node, not 3 2017-08-07 13:36:05 -04:00
config
debug
distros
erasure-code qa/suites/rados/thrash-erasure-code-big: add k=4 m=2 2017-08-03 22:50:16 -04:00
libceph
machine_types Merge pull request #16494 from asomers/bin_bash 2017-08-27 10:14:14 +08:00
mds
mon/bootstrap
mon_kv_backend
nightlies
objectstore qa/objectstore/bluestore*: less debug output 2017-09-05 17:43:28 -04:00
objectstore_cephfs
overrides qa/overrides/2-size-2-min-size: whitelist REQUEST_STUCK 2017-08-24 15:50:45 -04:00
packages
qa_scripts Merge pull request #16494 from asomers/bin_bash 2017-08-27 10:14:14 +08:00
rbd
releases qa/suites/rados/upgrade: jewel-x -> luminous-x 2017-08-28 23:11:27 -04:00
rgw_pool_type
standalone osd/PrimaryLogPG: do not generate data digest for BlueStore by default 2017-09-13 12:17:16 +08:00
suites osd/PrimaryLogPG: do not generate data digest for BlueStore by default 2017-09-13 12:17:16 +08:00
tasks Merge pull request #17536 from ceph/wip-cd-rbd-pool 2017-09-07 15:13:32 -07:00
timezone
workunits Merge pull request #17536 from ceph/wip-cd-rbd-pool 2017-09-07 15:13:32 -07:00
.gitignore
loopall.sh
Makefile
README
run_xfstests_qemu.sh
run_xfstests-obsolete.sh
run_xfstests.sh qa/run_xfstests.sh: quit building xfstests on test nodes 2017-08-29 16:08:27 +02:00
run-standalone.sh tests: run-standalone.sh skip core_pattern if already set 2017-08-18 10:27:12 -07:00
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