[rabbitmq-discuss] Multiple nodes on single box

[Steve Powell]

My outline of a solution with a wrapper script was designed to allow a
common code installation to be shared by multiple broker instances
running the same machine.

By 'the generic installation in multiple locations' I'm assuming you
mean installing the Generic-Unix package muiltiple times. (You just have
to unpack the archive once and copy the directory structure.) If you do
this, then no adjustment of the RABBITMQ variables is necessary, just
invoke the appropriate script and each one will (by default) use it's
own code directory for its configuration, log and Mnesia files.

You still have to ensure their use of global resources do not clash.

I would prefer to have one shared code-base (upgrades are easier).

Let us know if you come across any problems.

Steve Powell
steve at rabbitmq.com
[wrk: +44-2380-111-528] [mob: +44-7815-838-558]

On 30 Mar 2012, at 07:22, Timya Tortus wrote:

> Thanks for the great information shared, this will be interesting to have a wrapper script for each node. 
> 
> I think, the generic installation in multiple locations, having the rabbitmq-defaults, rabbitmq-env and rabbitmq.config considering all the listeners modified will work. Having installations on multiple locations will make rabbitmq embed-able in one's application (required Erlang is already available on the machine). Using this approach will free me, by having the required properties to be picked-up externally. These properties will then be used to create or modify the rabbitmq-defaults, rabbitmq-env and rabbitmq.config as required. 
> 
> Any thoughts ?
> 
> Regards,
> Timya