<div dir="ltr">Hmm - shovels are best for mostly static setups currently...<div><br></div><div>I experimented as well using federation awhile back, and that is dynamically configurable by setting policies using the mgt api.</div>
<div><br></div><div>It worked, but at the time federation was new, and I found shovels to be rugged and suitable for my use case. In our next internal release I think I will start deploying some federated links however.</div>
<div><br></div><div>So I would try federation if you really need to architect this way.</div><div><br></div><div>Good luck!</div><div><br></div><div>Michael</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Sat, Oct 26, 2013 at 5:09 PM, Julian Lyndon-Smith <span dir="ltr"><<a href="mailto:julian+rabbitmq@dotr.com" target="_blank">julian+rabbitmq@dotr.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks for the info. I still have a couple of questions ;)<br>
<br>
Is there an api for adding shovels ? The tenants are dynamic (ie they<br>
can be created at any time, and not known in advance) Or do you have<br>
to manually edit a file ?<br>
<br>
You have to restart the server to add a new shovel ? Really ? If<br>
that's a case, it's a no go - data is flying around from several<br>
sources and I couldn't stop 20 clients in order to add a 21st.<br>
<span class="HOEnZb"><font color="#888888"><br>
Julian<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
On 26 October 2013 22:00, Laing, Michael <<a href="mailto:michael.laing@nytimes.com">michael.laing@nytimes.com</a>> wrote:<br>
> We use shovels for inter-vhost communication like that.<br>
><br>
> Easy and quick. Except you have to restart a cluster member to pick up the<br>
> config...<br>
><br>
> Michael<br>
><br>
><br>
> On Sat, Oct 26, 2013 at 4:33 PM, Julian Lyndon-Smith<br>
> <<a href="mailto:julian%2Brabbitmq@dotr.com">julian+rabbitmq@dotr.com</a>> wrote:<br>
>><br>
>> I have a scenario where I need to be able to have a multi-tenant MQ<br>
>> server, so I started using vHosts.<br>
>><br>
>> However, I also need to be able to route / transfer / forward messages<br>
>> from a stomp client that is sending to the / vhost to another vhost<br>
>> based on the queue that the message was sent to<br>
>><br>
>> for example, the stomp client sends to /queue/api/foo.bar , I want to<br>
>> send the message to vHost foo<br>
>><br>
>> I can , obviously create a stomp client for each tenant, but that<br>
>> becomes real expensive in resources very quickly and was hoping that<br>
>> there would be a better way<br>
>><br>
>> Many thanks<br>
>><br>
>> Julian<br>
>> _______________________________________________<br>
>> rabbitmq-discuss mailing list<br>
>> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
>> <a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> rabbitmq-discuss mailing list<br>
> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
> <a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
><br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</div></div></blockquote></div><br></div>