<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 21, 2013, at 9:16 AM, Armando Migliaccio <<a href="mailto:amigliaccio@vmware.com">amigliaccio@vmware.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">In my view a cell should only know about the queue it's connected to, and let the 'global' message queue to do its job of dispatching the messages to the right recipient: that would solve the problem altogether.<div>
<div><br></div><div>Were <a href="http://www.rabbitmq.com/federation.html">federated</a> queues and topic <a href="http://blog.springsource.org/2011/04/01/routing-topologies-for-performance-and-scalability-with-rabbitmq/">routing</a> not considered fit for the purpose? I guess the drawback with this is that it is tight to Rabbit.</div></div></blockquote><div><br></div><div>If you're referring to the rabbit federation plugin, no, it was not considered. I'm not even sure that via rabbit queues is the right way to talk cell to cell. But I really do not want to get into a full blown cells communication design discussion here. We can do that in another thread, if we need to do so. :)</div><div><br></div><div>It is what it is today and this thread is just about how to express the configuration for it.</div><div><br></div><div>Regarding Mark's config suggestion:</div><div><br></div><blockquote type="cite"><div><div><div class="gmail_quote">On Mon, Jun 17, 2013 at 2:14 AM, Mark McLoughlin <span dir="ltr"><<a href="mailto:markmc@redhat.com" target="_blank">markmc@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">
<div class="im">I don't know whether I like it yet or not, but here's how it might look:</div>
<br>
[cells]<br>
parents = parent1<br>
children = child1, child2<br>
<br>
[cell:parent1]<br>
transport_url = <a href="qpid://host1/nova">qpid://host1/nova</a><br>
<br>
[cell:child1]<br>
transport_url = <a href="qpid://host2/child1_nova">qpid://host2/child1_nova</a><br>
<br>
[cell:child2]<br>
transport_url = <a href="qpid://host2/child2_nova">qpid://host2/child2_nova</a><br></blockquote></div></div></div></blockquote>[…]</div><div><div><br></div><div>Yeah, that's what I was picturing if going that route. I guess the code for it is not bad at all. But with oslo.config, can I reload (re-parse) the config file later, or does the service need to be restarted?</div><div><br></div><div>- Chris</div><div><br></div><div><br></div></div></body></html>