Browse Source

Fix NovaEnableRbdBackend to be role specific

This [1] change enabled to have role specific NovaEnableRbdBackend
parameter, however global parameter were allways overriding role
specific hiera after it was set via RoleParametersValue

[1]: I9f40a2a3561fcb1d1fec9d9c3c1f9cabaf02650c

Change-Id: Iab58223a6140e42028d4d2a7305c05fd7ae3a9f0
(cherry picked from commit eb5251ad9f)
tags/10.6.1
Piotr Kopec 3 weeks ago
parent
commit
0febc015d8
1 changed files with 0 additions and 1 deletions
  1. 0
    1
      deployment/nova/nova-compute-container-puppet.yaml

+ 0
- 1
deployment/nova/nova-compute-container-puppet.yaml View File

@@ -478,7 +478,6 @@ outputs:
478 478
             nova::compute::instance_usage_audit: true
479 479
             nova::compute::instance_usage_audit_period: 'hour'
480 480
             nova::compute::consecutive_build_service_disable_threshold: {get_param: NovaAutoDisabling}
481
-            nova::compute::rbd::ephemeral_storage: {get_param: NovaEnableRbdBackend}
482 481
             nova::compute::live_migration_wait_for_vif_plug: {get_param: NovaLiveMigrationWaitForVIFPlug}
483 482
             # TUNNELLED mode provides a security improvement for migration, but
484 483
             # can't be used in combination with block migration. So we only enable it

Loading…
Cancel
Save