Re: [openstack-dev] [fuel] RabbitMQ in dedicated network

2016-01-14 Thread Bogdan Dobrelya
On 28.12.2015 10:12, Bogdan Dobrelya wrote: > On 23.12.2015 18:50, Matthew Mosesohn wrote: >> I agree. As far as I remember, rabbit needs fqdns to work and map >> correctly. I think it means we should disable the ability to move the >> internal messaging network role in order to fix this bug until

Re: [openstack-dev] [fuel] RabbitMQ in dedicated network

2016-01-14 Thread Vladimir Kuklin
+1 to Bogdan here. On Thu, Jan 14, 2016 at 4:27 PM, Bogdan Dobrelya wrote: > On 28.12.2015 10:12, Bogdan Dobrelya wrote: > > On 23.12.2015 18:50, Matthew Mosesohn wrote: > >> I agree. As far as I remember, rabbit needs fqdns to work and map > >> correctly. I think it

Re: [openstack-dev] [fuel] RabbitMQ in dedicated network

2015-12-28 Thread Bogdan Dobrelya
On 23.12.2015 18:50, Matthew Mosesohn wrote: > I agree. As far as I remember, rabbit needs fqdns to work and map > correctly. I think it means we should disable the ability to move the > internal messaging network role in order to fix this bug until we can > add extra dns entries per network role

Re: [openstack-dev] [fuel] RabbitMQ in dedicated network

2015-12-28 Thread Andrew Woodward
On Mon, Dec 28, 2015 at 1:13 AM Bogdan Dobrelya wrote: > On 23.12.2015 18:50, Matthew Mosesohn wrote: > > I agree. As far as I remember, rabbit needs fqdns to work and map > > correctly. I think it means we should disable the ability to move the > > internal messaging

Re: [openstack-dev] [fuel] RabbitMQ in dedicated network

2015-12-23 Thread Andrew Maksimov
Hi Kirill, I don't think we can give up on using fqdn node names for RabbitMQ because we need to support TLS in the future. Thanks, Andrey Maximov Fuel Project Manager On Wed, Dec 23, 2015 at 8:24 PM, Kyrylo Galanov wrote: > Hello, > > I would like to start discussion

Re: [openstack-dev] [fuel] RabbitMQ in dedicated network

2015-12-23 Thread Matthew Mosesohn
I agree. As far as I remember, rabbit needs fqdns to work and map correctly. I think it means we should disable the ability to move the internal messaging network role in order to fix this bug until we can add extra dns entries per network role (or at least addr) On Dec 23, 2015 8:42 PM, "Andrew

Re: [openstack-dev] [fuel] RabbitMQ in dedicated network

2015-12-23 Thread Alexey Lebedeff
When long node names are enabled (controlled by RABBITMQ_USE_LONGNAME environment variable), you could actually use IP-address as a node name. Matthew Mosesohn writes: > I agree. As far as I remember, rabbit needs fqdns to work and map > correctly. I think it means we should disable the ability

[openstack-dev] [fuel] RabbitMQ in dedicated network

2015-12-23 Thread Kyrylo Galanov
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.

Re: [openstack-dev] [fuel] RabbitMQ in dedicated network

2015-12-23 Thread Vladimir Kuklin
Kyrylo One comment here. Hostname on the nodes resolves to its management network as it is put into /etc/hosts file during the deployment. On Wed, Dec 23, 2015 at 9:27 PM, Alexey Lebedeff wrote: > > When long node names are enabled (controlled by RABBITMQ_USE_LONGNAME >