mirror of
https://github.com/ceph/ceph
synced 2025-03-25 11:48:05 +00:00
Ceph is a distributed object, block, and file storage platform
It is not enough to look for the first install task. In upgrade tests, the install.upgrade task requires more packages to be built. In more complicated tests using sequential and parallel tasks, the actual install or install.upgrade task may be deeper in the config tree. Signed-off-by: Loic Dachary <loic@dachary.org> |
||
---|---|---|
ceph-deploy-overrides | ||
clusters | ||
config_options | ||
debug | ||
distros | ||
erasure-code | ||
fs | ||
machine_types | ||
overrides | ||
releases | ||
rgw_pool_type | ||
suites | ||
tasks | ||
timezone | ||
.gitignore | ||
README | ||
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