ext4 seems to be a better choice for our purposes -- less test churn,
rather small and reliable exclude list.
All excluded tests but generic/050 fail with no krbd in the mix, most
have popped up on linux-ext4 list at least once.
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
- factor out install and ceph into ceph/ceph.yaml
- pg_num thrashing + 20 minute health timeout for thrashosds
- common thrashosds-health.yaml whitelist
- drop iozone workload
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
The default tunables for luminous allow straw2 buckets, which aren't
supported by pre-single-major.yaml kernel. The map is generated before
crush_tunables override takes effect, so set the bucket algorithm to
straw manually.
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
Keep the pool flag around so we can distinguish between a pool that
should maintain hashes for each chunk, and a missing one is a bug, vs
an overwrites pool where we rely on bluestore checksums for detecting
corruption.
Signed-off-by: Josh Durgin <jdurgin@redhat.com>
qa/suites: drop 'fs' facet, and add 'objectstore' facet where missing
Reviewed-by: Josh Durgin <jdurgin@redhat.com>
Reviewed-by: Jason Dillaman <dillaman@redhat.com>
This is based on a script that I've been using for a while for basic
smoke testing. The matrix has exploded with the addition of data-pool
and now it's primarily a data-pool test fixture that takes minutes to
run, so turning it into a workunit.
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
