ceph/qa/suites/powercycle/osd/tasks/radosbench.yaml

tasks:
- full_sequential:
  - radosbench:
      clients: [client.0]
      time: 150
  - radosbench:
      clients: [client.0]
      time: 150
  - radosbench:
      clients: [client.0]
      time: 150
  - radosbench:
      clients: [client.0]
      time: 150
  - radosbench:
      clients: [client.0]
      time: 150
  - radosbench:
      clients: [client.0]
      time: 150
  - radosbench:
      clients: [client.0]
      time: 150
  - radosbench:
      clients: [client.0]
      time: 150
marginal/osd_powercycle: OSD powercycle thrashing Tasks to run while thrashing osds using ipmi to powercycle. This currently runs in the marginal suite only. Signed-off-by: Sam Lang <sam.lang@inktank.com> 2013-01-31 14:44:09 +00:00			`tasks:`
suites: run rados bench for max 180 seconds If we want a longer runtime than that, run it several times in sequence. This limits the amount of disk space we'll consume. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-26 13:18:41 +00:00			`- full_sequential:`
			`- radosbench:`
			`clients: [client.0]`
suites: radosbench 180 -> 150s I hit an ENOSPC after 150s on bluestore. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-31 16:27:11 +00:00			`time: 150`
suites: run rados bench for max 180 seconds If we want a longer runtime than that, run it several times in sequence. This limits the amount of disk space we'll consume. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-26 13:18:41 +00:00			`- radosbench:`
			`clients: [client.0]`
suites: radosbench 180 -> 150s I hit an ENOSPC after 150s on bluestore. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-31 16:27:11 +00:00			`time: 150`
suites: run rados bench for max 180 seconds If we want a longer runtime than that, run it several times in sequence. This limits the amount of disk space we'll consume. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-26 13:18:41 +00:00			`- radosbench:`
			`clients: [client.0]`
suites: radosbench 180 -> 150s I hit an ENOSPC after 150s on bluestore. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-31 16:27:11 +00:00			`time: 150`
suites: run rados bench for max 180 seconds If we want a longer runtime than that, run it several times in sequence. This limits the amount of disk space we'll consume. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-26 13:18:41 +00:00			`- radosbench:`
			`clients: [client.0]`
suites: radosbench 180 -> 150s I hit an ENOSPC after 150s on bluestore. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-31 16:27:11 +00:00			`time: 150`
suites: run rados bench for max 180 seconds If we want a longer runtime than that, run it several times in sequence. This limits the amount of disk space we'll consume. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-26 13:18:41 +00:00			`- radosbench:`
			`clients: [client.0]`
suites: radosbench 180 -> 150s I hit an ENOSPC after 150s on bluestore. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-31 16:27:11 +00:00			`time: 150`
suites: run rados bench for max 180 seconds If we want a longer runtime than that, run it several times in sequence. This limits the amount of disk space we'll consume. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-26 13:18:41 +00:00			`- radosbench:`
			`clients: [client.0]`
suites: radosbench 180 -> 150s I hit an ENOSPC after 150s on bluestore. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-31 16:27:11 +00:00			`time: 150`
suites: run rados bench for max 180 seconds If we want a longer runtime than that, run it several times in sequence. This limits the amount of disk space we'll consume. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-26 13:18:41 +00:00			`- radosbench:`
			`clients: [client.0]`
suites: radosbench 180 -> 150s I hit an ENOSPC after 150s on bluestore. Signed-off-by: Sage Weil <sage@redhat.com> 2016-03-31 16:27:11 +00:00			`time: 150`
			`- radosbench:`
			`clients: [client.0]`
			`time: 150`