Merge "Switch cinder-backup default to active-active"
This commit is contained in:
commit
09e8ccac77
|
@ -0,0 +1,2 @@
|
||||||
|
resource_registry:
|
||||||
|
OS::TripleO::Services::CinderBackup: ../deployment/cinder/cinder-backup-pacemaker-puppet.yaml
|
|
@ -1,3 +1,3 @@
|
||||||
resource_registry:
|
resource_registry:
|
||||||
OS::TripleO::Services::CinderBackup: ../deployment/cinder/cinder-backup-pacemaker-puppet.yaml
|
OS::TripleO::Services::CinderBackup: ../deployment/cinder/cinder-backup-container-puppet.yaml
|
||||||
# Use cinder-backup-active-active.yaml for non-pcmk managed implementation
|
# Use cinder-backup-active-passive.yaml for pcmk managed implementation
|
||||||
|
|
|
@ -0,0 +1,11 @@
|
||||||
|
---
|
||||||
|
features:
|
||||||
|
- |
|
||||||
|
When the cinder-backup service is deployed, it now defaults to
|
||||||
|
active-active and not active-passive.
|
||||||
|
upgrade:
|
||||||
|
- |
|
||||||
|
Cinder backup service will be switched from active-passive to active-active
|
||||||
|
if the service was originally deployed using the cinder-backup.yaml
|
||||||
|
environment file. Cloud administrators who wish to keep it active-passive
|
||||||
|
should use the new cinder-backup-active-passive.yaml env file.
|
Loading…
Reference in New Issue