On Fri, Jan 23, 2015 at 12:46 PM, ozamiatin ozamia...@mirantis.com wrote:
IMHO It should be created once per Reactor/Client or even per driver
instance.
Per driver, sounds good.
By the way (I didn't check it yet with current implementation of the
driver) such approach should break the
Hi, all!
Unexpectedly I met a pretty significant issue when I have been solving a
small bug
https://bugs.launchpad.net/ubuntu/+source/oslo.messaging/+bug/1367614. The
problem is in several parts:
* Topics used for several purposes: to set subscriptions and to determine a
type of sockets.
*
Please, provide a RabbitMQ logs from a controller and an oslo.messaging
version. Do you use up-stream oslo.messaging version? It looks like well
known heartbeat bug.
On Wed, Dec 10, 2014 at 1:45 PM, Timur Nurlygayanov
tnurlygaya...@mirantis.com wrote:
Hi Raghavendra Lad,
looks like Murano
Windisch e...@windisch.us wrote:
On Mon, Nov 17, 2014 at 5:44 AM, Ilya Pekelny ipeke...@mirantis.com
wrote:
We want to discuss opportunity of implementation of the p-2-p messaging
model in oslo.messaging for ZeroMQ driver. Actual architecture
uses uncharacteristic single broker architecture
Thank you, Li Ma!
Yes, sure I'm going to provide more detailed mail with a solid propositions
list. I need to do some knowledge updates before I provide it.
On Tue, Nov 18, 2014 at 10:40 AM, Li Ma skywalker.n...@gmail.com wrote:
On 2014/11/17 18:44, Ilya Pekelny wrote:
Hi, all!
We want
Hi, all!
We want to discuss opportunity of implementation of the p-2-p messaging
model in oslo.messaging for ZeroMQ driver. Actual architecture
uses uncharacteristic single broker architecture model. In this way we are
ignoring the key 0MQ ideas. Lets describe our message in quotes from ZeroMQ
Flavio Percoco wrote:
Still, I'd like us to learn from
previous experiences and have a better plan for this driver (and
future cases like this one).
Hi, all!
As one of a just joined ZeroMQ maintainers I have a growing plan of ZeroMQ
refactoring and development. At the most abstract view
