Wait for rabbitmq to respond to commands

Sometimes rabbitmq service starts but rabbitmq
server is not ready to accept requests. This
commit adds wait loop for rabbitmq and then
allows rabbitmq_* resources to work with
rabbitmq server.

Change-Id: Ic01773a4f84bbc1fa1a4139a0a6eb366191a8b9b
Closes-bug: #1377491
Set explisit mysql-wsrep package name for zabbix

So as there is trend to support wsrep mysql package only and
seems that normal package works not so good, so I set wsrep
install for zabbix explicitly.

Change-Id: I87e62a34d7cbc572cc1f9ec6baded1404c76f0e3
Closes-Bug: #1368151

Conflicts:
	deployment/puppet/osnailyfacter/manifests/cluster_ha.pp
	deployment/puppet/osnailyfacter/manifests/cluster_simple.pp
Improve wait-for-* execs

Right after start haproxy marks all backends as UP. It marks
problem ones as DOWN only after health-checks. So we should not
rely on BACKEND status while INI is in process.

Change-Id: Ia3743d446826ee1a9d42799a83e14a911a577966
Related-bug: #1391180
(cherry picked from commit 360ef59e8f828243304a669328257be8504b8df6)

Conflicts:
	deployment/puppet/osnailyfacter/manifests/cluster_ha.pp

(cherry picked from commit add3fdd)
Always wait for keystone haproxy backends

We wait for haproxy backend only for nova-network case, but neutron case
*does* rely on keystone as well. If we don't wait for keystone haproxy
backends, we could end up with neutron net-list failures.

Closes-bug: #1394140

Change-Id: I951f77cf5216c185756c4f430eb078df00319de2
Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>

Conflicts:
	deployment/puppet/osnailyfacter/manifests/cluster_ha.pp
conflicts with previous cherry-picked commit
Set nova shell to /bin/bash

Nova requires shell as nova user on remote compute hosts for VM resize.

Change-Id: I7e549f58903fd94af5e04dc2c058673d0b182965
Closes-Bug: #1385227
(cherry picked from commit 15b5216f7d272e0a33773af370131e3077141734)
Merge branch 'fix-bugs' into msdd448-current
Merge branch 'msdd448-patches' into msdd448-current