ceph/qa
Douglas Fuller 75f55f2dfc osd/filestore: Change default filestore_merge_threshold to -1
Performance evaluations of medium to large size Ceph clusters have
demonstrated negligible performance impact from unnecessarily deep
directory hierarchies but significant performance impact from filestore
split and merge activity. Disable merges by default.

Fixes: http://tracker.ceph.com/issues/24686
Signed-off-by: Douglas Fuller <dfuller@redhat.com>
2018-06-29 11:45:12 -04:00
..
archs
btrfs
cephfs mds: check for session import race 2018-05-14 12:52:50 -07:00
client
clusters
config
crontab qa/tests - added mimic-p2p suite 2018-06-26 16:05:44 -07:00
debug
distros tests/qa: adding rados/.. dirs 2018-05-11 14:03:15 -07:00
erasure-code
libceph
machine_types tests/qa - fix mimic subset for nightlies 2018-05-10 07:39:51 -07:00
mds
mon/bootstrap
mon_kv_backend
nightlies
objectstore
objectstore_cephfs
overrides qa/suites/rados: add coverage for osd_recovery_max_single_start > 1 2018-04-20 19:42:15 -04:00
packages
qa_scripts
rbd qa: krbd_msgr_segments.t: filter lvcreate output 2018-06-21 20:51:23 +02:00
releases
rgw_frontend rgw: beast frontend no longer experimental 2018-04-10 12:26:37 -04:00
rgw_pool_type qa/rgw: disable testing on ec-cache pools 2018-05-21 13:29:01 -04:00
standalone osd/filestore: Change default filestore_merge_threshold to -1 2018-06-29 11:45:12 -04:00
suites Merge PR #22560 into master 2018-06-27 14:19:03 -07:00
tasks Merge pull request #22672 from tspmelo/wip-encode-uri 2018-06-26 17:03:29 +02:00
timezone
workunits Merge PR #22725 into master 2018-06-27 11:13:37 -07:00
.gitignore
find-used-ports.sh
loopall.sh
Makefile
README
run_xfstests_qemu.sh
run_xfstests-obsolete.sh
run_xfstests.sh
run-standalone.sh Merge PR #22343 into master 2018-06-19 07:07:55 -05: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

A directory with a magic '$' file represents a test where one of the other
items is chosen randomly. For example,

suites/foo/$
suites/foo/a.yaml
suites/foo/b.yaml
suites/foo/c.yaml

is a single test.  It will be either a.yaml, b.yaml or c.yaml.  This can be
used in conjunction with the '%' file in other directories to run a series of
tests without causing an unwanted increase in the total number of jobs run.

Symlinks are okay.

The teuthology code can be found in https://github.com/ceph/teuthology.git