Remove CrushRules coverage from scenario001
We see many issues in CI due to the missing hdd device class. This is something that can be related to the fact that only 1 OSD in this job is built on top of a loop device. For this reason, and in order to keep the CI healthy, it's safe removing the device classes coverage. In addition, since there is only 1 osd, add and configure tiering in this context makes no sense. Change-Id: I4638b9badd17a7a75642895623a63753534fd341
This commit is contained in:
parent
47ccf1cfc7
commit
e68ed6f7cc
@ -55,7 +55,6 @@ parameter_defaults:
|
||||
CeilometerQdrPublishMetrics: true
|
||||
ManageEventPipeline: true
|
||||
ManagePipeline: true
|
||||
|
||||
Debug: true
|
||||
CephSpecFqdn: true
|
||||
CephOsdSpec:
|
||||
@ -65,16 +64,10 @@ parameter_defaults:
|
||||
CephPoolDefaultPgNum: 8
|
||||
CephPoolDefaultSize: 1
|
||||
CinderRbdExtraPools: altrbd,pool2,pool3
|
||||
CephCrushRules:
|
||||
- name: HDD
|
||||
root: default
|
||||
type: host
|
||||
class: hdd
|
||||
default: true
|
||||
CephPools:
|
||||
- name: altrbd
|
||||
pg_num: 8
|
||||
rule_name: HDD
|
||||
rule_name: replicated_rule
|
||||
#NOTE: These ID's and keys should be regenerated for
|
||||
# a production deployment. What is here is suitable for
|
||||
# developer and CI testing only.
|
||||
|
Loading…
Reference in New Issue
Block a user