ceph/qa/erasure-code/ec-rados-default.yaml

tasks:
  - rados:
      clients: [client.0]
      ops: 4000
      objects: 50
      ec_pool: true
      write_append_excl: false
      op_weights:
        read: 100
        write: 0
        append: 100
        delete: 50
        snap_create: 50
        snap_remove: 50
        rollback: 50
        copy_from: 50
        setattr: 25
        rmattr: 25
  - print: "**** done rados ec task"
erasure-code: enable ec-rados-default.yaml 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/11221 Fixes: #11221 Signed-off-by: Loic Dachary <loic@dachary.org> 2015-03-24 16:41:12 +00:00			`tasks:`
			`- rados:`
			`clients: [client.0]`
			`ops: 4000`
			`objects: 50`
			`ec_pool: true`
erasure-code: add write_append_excl: false Add write_append_excl: false to all erasure-code workloads and use the same workload in all upgrade tests. write_append_excl: false is not meaningfull for all Ceph versions but when it's not it will just be ignored. Signed-off-by: Loic Dachary <ldachary@redhat.com> 2015-08-06 13:33:58 +00:00			`write_append_excl: false`
erasure-code: enable ec-rados-default.yaml 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/11221 Fixes: #11221 Signed-off-by: Loic Dachary <loic@dachary.org> 2015-03-24 16:41:12 +00:00			`op_weights:`
			`read: 100`
			`write: 0`
			`append: 100`
			`delete: 50`
			`snap_create: 50`
			`snap_remove: 50`
			`rollback: 50`
			`copy_from: 50`
			`setattr: 25`
			`rmattr: 25`
			`- print: "**** done rados ec task"`