ceph/README

42 lines
1.4 KiB
Plaintext
Raw Normal View History

2011-07-07 23:44:45 +00:00
ceph-qa-suite
-------------
2011-08-10 20:36:34 +00:00
clusters/ - some predefined cluster layouts
suites/ - sets of collections
2011-08-10 20:36:34 +00:00
We have several collections, each a subdirectory within suites/*/.
2011-08-10 20:36:34 +00:00
Each collection directory consists of a set facets. The basic idea is
that, for each collection, the set of tests to run consists of all
2011-07-07 23:44:45 +00:00
combinations of taking one yaml fragment from each facet.
2011-08-10 20:36:34 +00:00
For example, given the files
2011-07-07 23:44:45 +00:00
suite/collection/
suite/collection/foo/
suite/collection/foo/clusters/
suite/collection/foo/clusters/fixed-3.yaml
suite/collection/foo/clusters/fixed-9.yaml
suite/collection/foo/tasks/
suite/collection/foo/tasks/a
suite/collection/foo/tasks/b
suite/collection/foo/tasks/c
suite/collection/bar/
suite/collection/bar/clusters/fixed-3.yaml
suite/collection/bar/tasks/
suite/collection/bar/tasks/d
suite/collection/bar/tasks/e
2011-07-07 23:44:45 +00:00
2011-08-10 20:36:34 +00:00
teuthology-suite would run tasks a, b, and c on both fixed-3 and
fixed-9 clusters. It would also run tasks d and e on the fixed-3
cluster.
2011-07-07 23:44:45 +00:00
Note that the 'clusters' and 'tasks' terminology is actually
meaningless here. All teuthology-suite does is stick the yaml
fragments together (one from each facet) and run teuthology on the
result (optionally combined with any additional fragments passed on
the command line).
2011-08-10 20:36:34 +00:00
In practice, we can keep common/shared task and cluster definitions in
the top-level clusters/ (which are otherwise ignored), and symlink to
them from the collections that want to use them.