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).
WIP patch: https://github.com/redhat-openstack/astapor/pull/463
Merged
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
*** Bug 1191718 has been marked as a duplicate of this bug. ***
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
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