Bug 1186459

Summary:	Add puppet param to enable setting multiple rabbit_hosts
Product:	Red Hat OpenStack	Reporter:	Crag Wolfe <cwolfe>
Component:	openstack-foreman-installer	Assignee:	Crag Wolfe <cwolfe>
Status:	CLOSED ERRATA	QA Contact:	Alexander Chuzhoy <sasha>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.0 (Juno)	CC:	aberezin, dmacpher, jguiditt, jwaterwo, mburns, morazi, ohochman, racedoro, rhos-maint, sasha, yeylon
Target Milestone:	z1	Keywords:	ZStream
Target Release:	Installer
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-foreman-installer-3.0.14-1.el7ost	Doc Type:	Enhancement
Doc Text:	This enhancement adds the ability to use multiple RabbitMQ hosts instead of a single RabbitMQ host VIP. Using multiple hosts is more stable than a single VIP, which struggles to adapt if a host goes down. OpenStack services can use either rabbit_hosts or a single rabbit_host.	Story Points:	---
Clone Of:
Clones:	1186966 (view as bug list)		Environment:
Last Closed:	2015-03-05 18:19:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1175685, 1186966

Description Crag Wolfe 2015-01-27 17:14:29 UTC

Description of problem:

Right now, openstack-foreman-installer configures openstack config files to use a rabbit vip with traffic forwarded through haproxy.  Add a flag to allow the user to keep this behaviour (the default), or, configure openstack config files to set rabbit_hosts with the list of rabbit addresses (and set rabbit_ha_queues=True).  Note that with the latter setting, the openstack services themselves will not rely on the rabbit vip or haproxy.  However, this enhancement does not include removal of the rabbit vip and rabbit-configuration for haproxy (their continued existence should be inconsequential).

Comment 3 Jason Guiditta 2015-02-03 17:00:27 UTC

WIP patch:
https://github.com/redhat-openstack/astapor/pull/463

Comment 4 Jason Guiditta 2015-02-05 20:28:44 UTC

Merged

Comment 6 Omri Hochman 2015-02-06 21:09:44 UTC

In order to Verify - Check the .conf files on the controllers are set according to comment #1 at : https://github.com/redhat-openstack/astapor/pull/463

Comment 7 Mike Burns 2015-02-11 20:06:08 UTC

*** Bug 1191718 has been marked as a duplicate of this bug. ***

Comment 8 Alexander Chuzhoy 2015-02-12 21:16:07 UTC

Verified:
rhel-osp-installer-client-0.5.5-4.el7ost.noarch
ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el7ost.noarch
openstack-foreman-installer-3.0.14-1.el7ost.noarch
rhel-osp-installer-0.5.5-4.el7ost.noarch
ruby193-rubygem-staypuft-0.5.18-1.el7ost.noarch
openstack-puppet-modules-2014.2.8-2.el7ost.noarch


Verifying based on c#6:
Received the following output on the controllers:

[root@maca25400702875 ~]# grep -vP '^#' /etc/*/*.conf | grep rabbit_hos
/etc/glance/glance-api.conf:rabbit_hosts=<ip1>:5672,<ip2>:5672,<ip3>:5672
/etc/keystone/keystone.conf:rabbit_hosts=<ip1>:5672,<ip2>:5672,<ip3>:5672
/etc/neutron/neutron.conf:rabbit_hosts=<ip1>:5672,<ip2>:5672,<ip3>:5672
/etc/nova/nova.conf:rabbit_hosts=<ip1>:5672,<ip2>:5672,<ip3>:5672

[root@maca25400702875 ~]# grep -vP '^#' /etc/*/*.conf | grep rabbit_ha             
/etc/glance/glance-api.conf:rabbit_ha_queues=True
/etc/keystone/keystone.conf:rabbit_ha_queues=True
/etc/neutron/neutron.conf:rabbit_ha_queues=True
/etc/nova/nova.conf:rabbit_ha_queues=True

Comment 10 errata-xmlrpc 2015-03-05 18:19:17 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0641.html