ceph/qa
Sage Weil 59bdada5d5 mon/OSDMonitor: accept crush_device_class in 'osd new' json input
If provided, set the OSD device_class at OSD creation time.  This is
simpler than writing a file that the OSD has to read in and use to
set its initial device class, and also avoids a bit of sticky state
at the OSD that will make it keep trying to reset its device class on
startup if it ever gets cleared.

Note that we now ignore json input fields we don't understand, so remove
a test case.

Signed-off-by: Sage Weil <sage@redhat.com>
2018-02-08 12:34:49 -06:00
..
archs
btrfs
cephfs qa/cephfs: test ec data pool 2017-10-23 21:11:24 -05:00
client
clusters
config
debug
distros qa/suites/fs: use ubuntu_latest for libcephfs_java 2017-12-19 11:12:28 -06:00
erasure-code
libceph
machine_types
mds
mon/bootstrap
mon_kv_backend
nightlies
objectstore
objectstore_cephfs
overrides
packages
qa_scripts
rbd qa/suites/krbd: add krbd BLKROSET test 2017-10-31 13:40:16 +01:00
releases
rgw_frontend qa/rgw: add beast frontend to some rgw suites 2017-10-27 11:20:52 -04:00
rgw_pool_type
standalone qa/standalone/scrub/osd-scrub-repair.sh: remove extents flag from object_info_t 2018-01-08 20:10:16 +03:00
suites qa/workunits/rbd: Add tests for consistency groups 2018-01-11 10:38:23 -05:00
tasks Merge pull request #19765 from liewegas/wip-force-backfill-cleanups 2018-01-08 12:50:18 -08:00
timezone
workunits mon/OSDMonitor: accept crush_device_class in 'osd new' json input 2018-02-08 12:34:49 -06:00
.gitignore
find-used-ports.sh qa: add simple and dirty script to find ports being used 2017-11-22 16:58:34 +00:00
loopall.sh
Makefile
README
run_xfstests_qemu.sh
run_xfstests-obsolete.sh
run_xfstests.sh
run-standalone.sh qa: respect $TEMPDIR 2017-09-15 12:19:50 +08: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