Switch cinder-backup default to active-active
Currently, cinder-backup deployment defaults to active-passive. This patch will update the environment file cinder-backup.yaml to use active-active deployment. Change-Id: I2164d3a921903d6886aa5fa66b300e01081b93a7
This commit is contained in:
parent
ab4004e4aa
commit
0bb289c558
2
environments/cinder-backup-active-passive.yaml
Normal file
2
environments/cinder-backup-active-passive.yaml
Normal file
@ -0,0 +1,2 @@
|
||||
resource_registry:
|
||||
OS::TripleO::Services::CinderBackup: ../deployment/cinder/cinder-backup-pacemaker-puppet.yaml
|
@ -1,3 +1,3 @@
|
||||
resource_registry:
|
||||
OS::TripleO::Services::CinderBackup: ../deployment/cinder/cinder-backup-pacemaker-puppet.yaml
|
||||
# Use cinder-backup-active-active.yaml for non-pcmk managed implementation
|
||||
OS::TripleO::Services::CinderBackup: ../deployment/cinder/cinder-backup-container-puppet.yaml
|
||||
# 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…
x
Reference in New Issue
Block a user