ceph/qa/erasure-code/ec-rados-plugin=lrc-k=4-m=2-l=3.yaml

tasks:
- rados:
    clients: [client.0]
    ops: 400
    objects: 50
    ec_pool: true
    write_append_excl: false
    erasure_code_profile:
      name: lrcprofile
      plugin: lrc
      k: 4
      m: 2
      l: 3
      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
rados/thrash: add ec workloads Adds ec workloads for snaps, small objects, read-write. copy-from is not yet enabled. Signed-off-by: Samuel Just <sam.just@inktank.com> 2014-02-18 21:43:31 +00:00			`tasks:`
			`- rados:`
			`clients: [client.0]`
erasure-code: lrc plugin workload Add a workload that uses the lrc erasure code plugin. Instead of adding it to suites/rados/thrash-erasure-code/workloads, a new suite is created at suites/rados/thrash-erasure-code-big because it needs more OSDs than other erasure code plugins. The alternative would be to increase the number of OSDs for all erasure code plugins, but that would needlessly increase the resources requirements. * cluster/12-osds.yaml creates a 12 OSDs, 3 MONs cluster * thrash-erasure-code-big/thrashers/.yaml are the same as thrash-erasure-code/thrashers/.yaml except they require that at least 8 OSDs are in at all times (instead of 4) because lrc PGs with k=4, m=2, l=3 are undersized if they do not have 8 OSDs. It is possible that crush fails to map 8 OSDs when only 8 OSDs are available, but that must not disturb the workload because min_size is 4. http://tracker.ceph.com/issues/11666 Fixes: #11666 Signed-off-by: Loic Dachary <ldachary@redhat.com> 2015-05-26 08:38:50 +00:00			`ops: 400`
rados/thrash: add ec workloads Adds ec workloads for snaps, small objects, read-write. copy-from is not yet enabled. Signed-off-by: Samuel Just <sam.just@inktank.com> 2014-02-18 21:43:31 +00:00			`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: add various erasure-code workloads 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> 2014-08-29 22:49:33 +00:00			`erasure_code_profile:`
			`name: lrcprofile`
			`plugin: lrc`
			`k: 4`
			`m: 2`
			`l: 3`
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`
rados/thrash: add ec workloads Adds ec workloads for snaps, small objects, read-write. copy-from is not yet enabled. Signed-off-by: Samuel Just <sam.just@inktank.com> 2014-02-18 21:43:31 +00:00			`op_weights:`
			`read: 100`
			`write: 0`
			`append: 100`
			`delete: 50`
			`snap_create: 50`
			`snap_remove: 50`
			`rollback: 50`
rados/thrash/workloads: enable copy_from for the ec workloads Signed-off-by: Samuel Just <sam.just@inktank.com> 2014-02-23 22:56:10 +00:00			`copy_from: 50`
erasure-code: add various erasure-code workloads 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> 2014-08-29 22:49:33 +00:00			`setattr: 25`
			`rmattr: 25`