Deploying cinder-backup without pacemaker in Active/Active mode

[Sandeep Yadav]

Description
===========

Currently we are deploying cinder-backup in Active/Passive mode under pacemaker; refer[1].

By default, In the current deployments because of Active/Passive mode the Cinder-backup status shows down on the other two controllers(Passive instances)[2].

It has been possible to do deploy cinder-backup in Active/Active from many releases(mitika based on information gathered from some storage experts).

With this launchpad we would like to track :-

* Deploying cinder-backup without pacemaker in Active/Active mode.
* Also, We need to cope on upgrade with deployments where it was previously managed by pacemaker

Steps to reproduce
==================

* Deploy an environment with cinder-backup and you will find cinder-backup under pacemaker in Active/backup

 ~~~
  openstack overcloud deploy --templates -e /usr/share/openstack-tripleo-heat-templates/environments/cinder-backup.yaml
 ~~~

Expected result
===============

Cinder-backup in Active/Active mode and not under pacemaker.

Actual result
=============

Default deployment results in cinder-backup running in Active/backup under pacemaker

Logs & Configs
==============

[1] https://github.com/openstack/tripleo-heat-templates/blob/master/environments/cinder-backup.yaml

~~~
resource_registry:
  OS::TripleO::Services::CinderBackup: ../deployment/cinder/cinder-backup-pacemaker-puppet.yaml
  # For non-pcmk managed implementation
  # OS::TripleO::Services::CinderBackup: ../deployment/cinder/cinder-backup-container-puppet.yaml
~~~

[2]
~~~
# pcs status
.
.
podman container: openstack-cinder-backup [192.168.24.1/openstack-cinder-backup:pcmklatest]
   openstack-cinder-backup-podman-0 (ocf::heartbeat:podman): Started controller01

+------------------+------------------------+------+---------+-------+----------------------------+
| Binary | Host | Zone | Status | State | Updated At |
+------------------+------------------------+------+---------+-------+----------------------------+
| cinder-scheduler | controller00 | nova | enabled | up | 2019-10-24T15:28:01.000000 |
| cinder-scheduler | controller01 | nova | enabled | up | 2019-10-24T15:28:01.000000 |
| cinder-scheduler | controller02 | nova | enabled | up | 2019-10-24T15:28:03.000000 |
| cinder-volume | hostgroup@tripleo_ceph | nova | enabled | up | 2019-10-24T15:28:02.000000 |
| cinder-backup | controller00 | nova | enabled | down | 2019-10-24T14:30:03.000000 |
| cinder-backup | controller01 | nova | enabled | up | 2019-10-24T15:28:04.000000 |
| cinder-backup | controller02 | nova | enabled | down | 2019-10-24T14:30:03.000000 |
+------------------+------------------------+------+---------+-------+--------------------------
~~~

[Alan Bishop (alan-bishop)]

[1] just merged, and it makes it possible to switch the cinder-backup service from active/passive under pacemaker to active/active. I forgot about this LP, and neglected to reference it in the commit message.

To facilitate running A/A there's a new environments/cinder-backup-active-active.yaml file [2].

[1] https://review.opendev.org/c/openstack/tripleo-heat-templates/+/786722
[2] https://opendev.org/openstack/tripleo-heat-templates/src/branch/master/environments/cinder-backup-active-active.yaml