4 clusters/ - some predefined cluster layouts
7 The suites directory has a hierarchical collection of tests. This can be
8 freeform, but generally follows the convention of
10 suites/<test suite name>/<test group>/...
12 A test is described by a yaml fragment.
14 A test can exist as a single .yaml file in the directory tree. For example:
19 is a simple group of two tests.
21 A directory with a magic '+' file represents a test that combines all
22 other items in the directory into a single yaml fragment. For example:
29 is a single test consisting of a + b + c.
31 A directory with a magic '%' file represents a test matrix formed from
32 all other items in the directory. For example,
42 is a 4-dimensional test matrix. Two dimensions (a, c) are trivial (1
43 item), so this is really 2x2 = 4 tests, which are
50 A directory with a magic '$' file, or a directory whose name ends with '$',
51 represents a test where one of the non-magic items is chosen randomly. For
65 is a single test, either a, b or c. This can be used in conjunction with the
66 '%' file in the same (see below) or other directories to run a series of tests
67 without causing an unwanted increase in the total number of jobs run.
71 One particular use of symlinks is to combine '%' and the latter form of '$'
72 feature. Consider supported_distros directory containing fragments that define
73 os_type and os_version:
76 supported_distros/centos.yaml
77 supported_distros/rhel.yaml
78 supported_distros/ubuntu.yaml
80 A test that links supported_distros as distros (a name that doesn't end with
81 '$') will be run three times: on centos, rhel and ubuntu. A test that links
82 supported_distros as distros$ will be run just once: either on centos, rhel or
83 ubuntu, chosen randomly.
85 The teuthology code can be found in https://github.com/ceph/teuthology.git