TripleO traditionally deploys the cinder-backup service to run
A/P (active/passive) under pacemaker, but cinder itself supports
running A/A. This patch adds deploy_steps_tasks to remove the
service from pcmk control (essentially deleting the pcs resource)
prior to deploying it as a regular containerized (non-pcmk) service.
A new cinder-backup-active-active.yaml environment file helps the
user clarify their intent. The legacy cinder-backup.yaml file
continues to deploy the service under pacemaker (to preserve the
default deployment behavior), but rather than encouraging users to
edit the file to switch deployment modes (as a comment in the file
used to advise), users can proactively deploy the A/A mode (or switch
from A/P to A/A) by including the new environment file.
Change-Id: Ic94025f51083da77f4ba6ee934ebcf32bcb9909f
This change combines the previous puppet and docker files into a single
file that performs the docker service installation and configuration.
With this patch the baremetal version of cinder services has been removed.
Change-Id: I88f047a8ee9c3eed80e4c48ed9cabdb3035d518b
Related-Blueprint: services-yaml-flattening
Mark regular non-containerized services with FIXME
to be switched, once it is containerized
Do not mark yet an external/backend/plugin/host-config
related puppet services templates with that FIXME
Mark puppet/services/ceph- related templates as TODO
switch it to containerized ceph-ansible eventually, maybe.
Change-Id: Ib9fbad05eeb57dc641499fbf411cb5870da7a8e9
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
The cinder-backup service was not configured in mitaka, so
having it disabled by default does not change the existing
behavior.
Also adds an environment file to enable it in the pacemaker
scenario.
Change-Id: I9a238e0d4601c9f59aff94fdac837c7d0e90afa0