The ec-rados-default.yaml was linked to suites as if it was a task
although it is a workload intended for parallel upgrade tests.
The ec-rados-plugin=jerasure-k=2-m=1.yaml task is defined and used
instead, where relevant.
http://tracker.ceph.com/issues/9549Fixes: #9549
Signed-off-by: Loic Dachary <loic-201408@dachary.org>
And replace the ec-readwrite.yaml custom workloads with links to the
workloads found in the erasure-code directory.
Signed-off-by: Loic Dachary <loic-201408@dachary.org>
Add + to 2-workload, 4-workload and 6-final-workload
suites. Reduce 5-upgrade-sequence to only run two
tests and make sure upgrades to emperor occur in each
sequence. Fix swift.yaml to not include rgw: clause
(this is already done by s3tests.yaml).
Fixes: #8051
Signed-off-by: Warren Usui <warren.usui@inktank.com>
Reformatted many of the yaml files.
Fixed duplication of workunit definitions.
Do not do install.upgrade on clients.
Included branch: definition in final workload files.
Signed-off-by: Warren Usui <warren.usui@inktank.com>
The encoded full osdmaps can differ due to a series of issues that were
fixed well after emperor. We also whitelist this for dumpling-x.
Signed-off-by: Sage Weil <sage@inktank.com>
