[rabbitmq-discuss] Automated deployment of rabbit and clustering.

[Laing, Michael]

In your example you have:

[{rabbit,
  [{cluster_nodes, {['rabbit at rabbit1', 'rabbit at rabbit2',
'rabbit at rabbit3'], disc}}]}].

What we do is just leave it like that and have a separate part of the
automated install which sets /etc/hosts to resolve those names.

ml


On Thu, Sep 5, 2013 at 6:24 AM, Simon MacMullen <simon at rabbitmq.com> wrote:

> Hmm. I'm not sure how well that would work; it's not something we have
> tested. I'm not sure whether the hostname of the machine(s) specified here
> get assumed to be part of the cluster.
>
> Cheers, Simon
>
>
> On 02/09/2013 4:49PM, Joe Higgins wrote:
>
>> So if I were to point it at a load balancer, this would work as the load
>> balancer should automatically add new nodes as they become available?
>>
>>
>> On 2 September 2013 15:55, Simon MacMullen <simon at rabbitmq.com
>> <mailto:simon at rabbitmq.com>> wrote:
>>
>>     That list is a list of hosts to contact to find out about the
>>     cluster. It is not required to contain the details of the entire
>>     cluster.
>>
>>     So I'm not sure how you can automatically generate it. You need to
>>     tell the new node where to find the cluster...
>>
>>     Cheers, Simon
>>
>>
>>     On 02/09/13 13:24, Joe Higgins wrote:
>>
>>         So I'm currently working on a project where we build deb
>>         packages for
>>         each component for automated deployment. In looking at the docs
>>         around
>>         clustering I have 1 main question.
>>
>>         In the naming of a node, or more specifically a rabbit broker,
>> what
>>         wildcard can I use so that the hosts name (which is automatically
>>         generated when we need more capacity) of the conf file?
>>
>>         IE.
>>
>>         [{rabbit,
>>             [{cluster_nodes, {['rabbit at rabbit1', 'rabbit at rabbit2',
>>         'rabbit at rabbit3'], disc}}]}].
>>
>>         "@rabbit1" needs to be an automatically generated hostname in
>>         the config
>>         file as this is to be an automated process.
>>
>>         Any help appreciated.
>>         --
>>
>>         Joe Higgins | junior project manager
>>         GlobalLogic
>>         www.globallogic.com <http://www.globallogic.com>
>>         <http://www.globallogic.com/>
>>         <http://www.globallogic.com/>
>>         http://www.globallogic.com/__**email_disclaimer.txt<http://www.globallogic.com/__email_disclaimer.txt>
>>         <http://www.globallogic.com/**email_disclaimer.txt<http://www.globallogic.com/email_disclaimer.txt>
>> >
>>
>>
>>         ______________________________**___________________
>>         rabbitmq-discuss mailing list
>>         rabbitmq-discuss at lists.__rabbi**tmq.com <http://rabbitmq.com>
>>         <mailto:rabbitmq-discuss@**lists.rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
>> >
>>         https://lists.rabbitmq.com/__**cgi-bin/mailman/listinfo/__**
>> rabbitmq-discuss<https://lists.rabbitmq.com/__cgi-bin/mailman/listinfo/__rabbitmq-discuss>
>>
>>         <https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**
>> rabbitmq-discuss<https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
>> >
>>
>>
>>
>>     --
>>     Simon MacMullen
>>     RabbitMQ, Pivotal
>>
>>
>>
>>
>> --
>>
>> Name | Title
>> GlobalLogic
>> P +x.xxx.xxx.xxxx  M +x.xxx.xxx.xxxx  S skype
>> www.globallogic.com <http://www.globallogic.com/>
>> <http://www.globallogic.com/>
>> http://www.globallogic.com/**email_disclaimer.txt<http://www.globallogic.com/email_disclaimer.txt>
>>
>
> --
> Simon MacMullen
> RabbitMQ, Pivotal
> ______________________________**_________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.**rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
> https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**rabbitmq-discuss<https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130905/04b0f37b/attachment.htm>