1
0
mirror of https://github.com/ceph/ceph synced 2024-12-22 11:31:55 +00:00
ceph/qa
David Zafman 886475b5fe mon: Improvements to slow heartbeat health messages
Include crush parentage for each osd

Fixes: https://tracker.ceph.com/issues/43126

Signed-off-by: David Zafman <dzafman@redhat.com>
2020-01-14 18:06:44 +00:00
..
archs
btrfs
cephfs qa/cephfs/begin: libaio-devel on el8 2019-12-17 13:39:08 -06:00
client
clusters
config
crontab qa/tests: trying to fix syntax error that prevented mimic-x to be added to the schedule 2019-11-21 16:43:54 -08:00
debug
distros qa/distros: centos7 -> centos8, rhel7 -> rhel8 2019-12-12 13:10:07 -06:00
erasure-code
libceph
machine_types qa: update s3-test download code for s3-test tasks 2019-12-10 12:39:28 -05:00
mds
mon/bootstrap
msgr
nightlies
objectstore
objectstore_cephfs
overrides
packages qa/packages/packages: python[3]-ceph is no more 2019-12-13 11:03:11 -06:00
qa_scripts
rbd qa: update krbd tests for python3 2019-12-02 21:13:19 +01:00
releases
rgw_frontend
rgw_pool_type qa: update s3-test download code for s3-test tasks 2019-12-10 12:39:28 -05:00
standalone mon: Improvements to slow heartbeat health messages 2020-01-14 18:06:44 +00:00
suites Revert "qa/suites/rgw: ragweed on ubuntu" 2019-12-17 14:40:34 -06:00
tasks Merge PR into master 2019-12-17 15:23:27 -06:00
timezone
workunits Merge PR into master 2019-12-17 15:23:27 -06:00
.gitignore
CMakeLists.txt qa: Enable flake8 tox and fix failures 2019-12-12 10:21:01 +01:00
find-used-ports.sh
loopall.sh
Makefile
README
run_xfstests_qemu.sh
run_xfstests-obsolete.sh
run_xfstests.sh
run-standalone.sh test: run-standalone.sh: Only run execs in the subdirectories of qa/standalone 2019-12-06 09:19:54 -08:00
runallonce.sh
runoncfuse.sh
runonkclient.sh
setup-chroot.sh
tox.ini
valgrind.supp

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