Backport the latest stable OCF scripts for RabbitMQ and Galera MySQL for MOS 8.0/7.0/6.1/6.0/5.1

affects customer recovery time on 6.1

It's better to upgrade RabbitMQ/Erlang alongside with OCF script. Reason is that older versions of rabbitmq are very sensitive to network splits and sudden death of nodes - any such event can bring whole cluster to the knees. And there is an ongoing work on hardening rabbit - e.g. soon-to-be-released 3.6.2 contains at least one fix for a bug that was seen at customer environment.

Erlang also needs to be upgraded, to at least 18.3.1 which contains fix for a critical bug (we can backport it only to 18.X releases, so R14 and R16 should be replaced everywhere). But with erlang rebuild we can go the easy way: build only the parts that are required by rabbitmq, and skip all other goodies that are usually built into debian packages(X11/java/ODBC/ssl/documentation).

Galera OCF RA backports: https://review.openstack.org/#/c/316085/ (6.1)
https://review.openstack.org/#/c/316803/ (7.0)

Rabbit OCF RA is independent to the RabbitMQ/Erlang and may be addressed completely separately

Rabbit OCF backports can be tracked as https://review.openstack.org/#/q/I4c51f8608702f2284d835ba9c3c9070b2c329ed8,n,z

And a separate link to track backports for the Galera OCF as well
https://review.openstack.org/#/q/Ie64b4d89c3e3b9aa360a4175416c866ed1ae2620,n,z

Change abandoned by Dmitry Mescheryakov (dmitryme) (<email address hidden>) on branch: stable/6.1
Review: https://review.openstack.org/318348

https://docs.mirantis.com/openstack/fuel/fuel-6.1/operations.html#howto-backport-rabbitmq-pacemaker-ocf-script
on step 4 "Download the latest OCF script from the fuel-library repository to the Fuel Master node:"
wget --no-check-certificate -O /etc/puppet/modules/nova/files/ocf/rabbitmq \
https://raw.githubusercontent.com/stack\
forge/fuel-library/stable/6.0/deployment/puppet/nova/files/ocf/rabbitmq

Why in documentation for 6.1 we are downloading 6.0 script? Is it correct?

Won't Fix for 6.0- and 6.1-updates as we don't have enough test coverage to accept and validate such a huge change into stable 6.0 and 6.1 branches.

Won't Fix for 7.0- and 8.0-updates as this is too risky change to accept to stable branch

Change abandoned by Tony Breeds (<email address hidden>) on branch: stable/6.1
Review: https://review.openstack.org/316053
Reason: This branch (stable/6.1) is at End Of Life