On Fri, May 18 2012, Doug Hellmann wrote: > While I see the benefit of discussing requirements for the message bus > platform in general, I'm not sure we need to dictate a specific > implementation. If we say we are going to use the nova RPC library to > communicate with the bus for sending and receiving messages, then we can > use all of the tools for which there are drivers in nova -- rabbit, qpid, > zeromq (assuming someone releases a driver, which I think is being worked > on somewhere), etc. This leaves the decision of which bus to use up to the > deployer, where the decision belongs. It also means we won't end up > choosing a tool for which the other projects have no driver, leading us to > have to create one and add a new dependency to the project.
+1 -- Julien Danjou // eNovance http://enovance.com // ✉ julien.dan...@enovance.com ☎ +33 1 49 70 99 81 _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
