The ec-rados-default.yaml started with:
workload:
sequential:
which is only suitable for suites/upgrade/giant-x/parallel/2-workload/sequential_run/ec-rados-default.yaml
because suites/upgrade/giant-x/parallel/1-giant-install/giant.yaml has
- parallel:
- workload
- upgrade-sequence
The same file was included in contexts where the parallel task was not
used and the workload did not run:
./suites/upgrade/firefly-x/stress-split-erasure-code/5-workload/ec-rados-default.yaml
./suites/upgrade/giant-x/stress-split-erasure-code/5-workload/ec-rados-default.yaml
./suites/upgrade/giant-x/stress-split-erasure-code-x86_64/5-workload/ec-rados-default.yaml
The ec-rados-default.yaml is modified to be a task instead of a
sequential task in a parallel tasks. The ec-rados-sequential.yaml is
added and is linked in
suites/upgrade/giant-x/parallel/2-workload/sequential_run instead of ec-rados-default.yaml.
http://tracker.ceph.com/issues/11221Fixes: #11221
Signed-off-by: Loic Dachary <loic@dachary.org>
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>
The erasure-code directory is populated with files describing rados
workloads suitable to test the default erasure code plugins. They are
linked to the rados suite. The pre-existing rados workloads from the
rados suite are replaced with those. Two workloads only differed by the
fact that one of them had less operations than the other. The more
complete set of operations is kept and used for all workloads to
maximize coverage.
Signed-off-by: Loic Dachary <loic-201408@dachary.org>
