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>
This commit is contained in:
Loic Dachary 2015-08-06 15:33:58 +02:00
parent 57f2e060f2
commit 12f4dffc35
12 changed files with 12 additions and 100 deletions

View File

@ -4,6 +4,7 @@ tasks:
ops: 4000
objects: 50
ec_pool: true
write_append_excl: false
op_weights:
read: 100
write: 0

View File

@ -5,6 +5,7 @@ workload:
ops: 4000
objects: 50
ec_pool: true
write_append_excl: false
op_weights:
read: 100
write: 0

View File

@ -4,6 +4,7 @@ tasks:
ops: 4000
objects: 50
ec_pool: true
write_append_excl: false
erasure_code_profile:
name: isaprofile
plugin: isa

View File

@ -4,6 +4,7 @@ tasks:
ops: 4000
objects: 50
ec_pool: true
write_append_excl: false
erasure_code_profile:
name: jerasure21profile
plugin: jerasure

View File

@ -10,6 +10,7 @@ tasks:
ops: 4000
objects: 50
ec_pool: true
write_append_excl: false
erasure_code_profile:
name: jerasure31profile
plugin: jerasure

View File

@ -4,6 +4,7 @@ tasks:
ops: 4000
objects: 50
ec_pool: true
write_append_excl: false
erasure_code_profile:
name: lrcprofile
plugin: lrc

View File

@ -4,6 +4,7 @@ tasks:
ops: 400
objects: 50
ec_pool: true
write_append_excl: false
erasure_code_profile:
name: shecprofile
plugin: shec
@ -22,8 +23,3 @@ tasks:
copy_from: 50
setattr: 25
rmattr: 25
overrides:
ceph:
conf:
global:
enable experimental unrecoverable data corrupting features: shec, ms-type-async

View File

@ -5,6 +5,7 @@ workload:
ops: 4000
objects: 50
ec_pool: true
write_append_excl: false
op_weights:
read: 100
write: 0

View File

@ -1,19 +0,0 @@
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"

View File

@ -0,0 +1 @@
../../../../../erasure-code/ec-rados-default.yaml

View File

@ -1,26 +0,0 @@
tasks:
- rados:
clients: [client.0]
ops: 4000
objects: 50
ec_pool: true
erasure_code_profile:
name: isaprofile
plugin: isa
k: 2
m: 1
technique: reed_sol_van
ruleset-failure-domain: osd
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 ec-rados-plugin=isa-k=2-m=1 9-workload"

View File

@ -0,0 +1 @@
../../../../../erasure-code/ec-rados-plugin=isa-k=2-m=1.yaml

View File

@ -1,19 +0,0 @@
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"

View File

@ -0,0 +1 @@
../../../../../erasure-code/ec-rados-default.yaml

View File

@ -1,31 +0,0 @@
#
# k=3 implies a stripe_width of 1376*3 = 4128 which is different from
# the default value of 4096 It is also not a multiple of 1024*1024 and
# creates situations where rounding rules during recovery becomes
# necessary.
#
tasks:
- rados:
clients: [client.0]
ops: 4000
objects: 50
ec_pool: true
write_append_excl: false
erasure_code_profile:
name: jerasure31profile
plugin: jerasure
k: 3
m: 1
technique: reed_sol_van
ruleset-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

View File

@ -0,0 +1 @@
../../../../../erasure-code/ec-rados-plugin=jerasure-k=3-m=1.yaml