ceph/qa/erasure-code/ec-rados-plugin=jerasure-k=2-m=1.yaml

tasks:
- rados:
    clients: [client.0]
    ops: 4000
    objects: 50
    ec_pool: true
    write_append_excl: false
    erasure_code_profile:
      name: jerasure21profile
      plugin: jerasure
      k: 2
      m: 1
      technique: reed_sol_van
      crush-failure-domain: osd
    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
erasure-code: fix bugous ec-rados-default.yaml in some suites 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/9549 Fixes: #9549 Signed-off-by: Loic Dachary <loic-201408@dachary.org> 2014-09-21 13:47:06 +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: fix bugous ec-rados-default.yaml in some suites 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/9549 Fixes: #9549 Signed-off-by: Loic Dachary <loic-201408@dachary.org> 2014-09-21 13:47:06 +00:00			`erasure_code_profile:`
			`name: jerasure21profile`
			`plugin: jerasure`
			`k: 2`
			`m: 1`
			`technique: reed_sol_van`
erasure-code: ruleset-* -> crush-* 1) ruleset is an obsolete term, and 2) crush-{rule,failure-domain,...} is more descriptive. Note that we are changing the names of the erasure code profile keys from ruleset-* to crush-*. We will update this on upgrade when the luminous flag is set, but that means that during mon upgrade you cannot create EC pools that use these fields. When the upgrade completes (users sets require_osd_release = luminous) existing ec profiles are updated automatically. Signed-off-by: Sage Weil <sage@redhat.com> 2017-06-30 18:59:39 +00:00			`crush-failure-domain: osd`
erasure-code: fix bugous ec-rados-default.yaml in some suites 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/9549 Fixes: #9549 Signed-off-by: Loic Dachary <loic-201408@dachary.org> 2014-09-21 13:47:06 +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`