Open Stack

Hello,

I would like to start discussion regarding the issue we have discovered
recently [1].

In a nutshell, if RabbitMQ is configured to run in separate mgmt/messaging
network it fails on building cluster.
While RabbitMQ is managed by Pacemaker and OCF script, the cluster is built
using FQDN. Apparently, FQDN resolves to admin network which is different
in this particular case.
As a result, RabbitMQ on secondary controller node fails to join to primary
controller node.

I can suggest two ways to tackle the issue: one is pretty simple, while
other is not.

The first way is to accept by design using admin network for RabbitMQ
internal communication between controller nodes.

The second way is to dig into pacemaker and RabbitMQ reconfiguration. Since
it requires to refuse from using common fqdn/node names, this approach can
be argued.


--
[1] https://bugs.launchpad.net/fuel/+bug/1528707

Best regards,
Kyrylo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151223/e265a16b/attachment.html>