On 23/09/2014 12:58 PM, Clint Byrum cl...@fewbar.com wrote:
Excerpts from Geoff O'Callaghan's message of 2014-09-22 17:30:47 -0700:
On 23/09/2014 1:59 AM, Clint Byrum cl...@fewbar.com wrote:
Geoff, do you expect all of our users to write all of their messaging
code in Python?
On 09/20/2014 10:17 AM, Geoff O'Callaghan wrote:
Hi all,
I'm just trying to understand the messaging strategy in openstack.It
seems we have at least 2 messaging layers.
Oslo.messaging and zaqar, Can someone explain to me why there are
two?To quote from the zaqar faq :
-
On 09/22/2014 08:00 AM, Flavio Percoco wrote:
oslo messaging is highly tight to AMQP semantics whereas Zaqar is not.
The API for oslo.messaging is actually quite high level and could easily
be mapped to different messaging technologies.
There is some terminology that comes from older
On 09/22/2014 11:04 AM, Gordon Sim wrote:
On 09/22/2014 08:00 AM, Flavio Percoco wrote:
oslo messaging is highly tight to AMQP semantics whereas Zaqar is not.
The API for oslo.messaging is actually quite high level and could easily
be mapped to different messaging technologies.
There is
On 09/22/2014 10:56 AM, Flavio Percoco wrote:
What I meant is that oslo.messaging is an rpc library and it depends on
few very specific message delivery patterns that are somehow tight/based
on AMQP semantics.
RPC at it's core is the request-response pattern which is directly
supported by
On 09/22/2014 02:35 PM, Gordon Sim wrote:
On 09/22/2014 10:56 AM, Flavio Percoco wrote:
What I meant is that oslo.messaging is an rpc library and it depends on
few very specific message delivery patterns that are somehow tight/based
on AMQP semantics.
RPC at it's core is the
So
On 22/09/2014 10:01 PM, Zane Bitter zbit...@redhat.com wrote:
On 20/09/14 04:17, Geoff O'Callaghan wrote:
Hi all,
I'm just trying to understand the messaging strategy in openstack.It
seems we have at least 2 messaging layers.
Oslo.messaging and zaqar, Can someone explain to me why
On 22/09/14 10:40, Geoff O'Callaghan wrote:
So
On 22/09/2014 10:01 PM, Zane Bitter zbit...@redhat.com wrote:
On 20/09/14 04:17, Geoff O'Callaghan wrote:
Hi all,
I'm just trying to understand the messaging strategy in openstack.It
seems we have at least 2 messaging layers.
Oslo.messaging
On 09/22/2014 03:40 PM, Geoff O'Callaghan wrote:
That being said I'm not sure why a well constructed zaqar with an rpc
interface couldn't meet the requirements of oslo.messsaging and much more.
What Zaqar is today and what it might become may of course be different
things but as it stands
Geoff, do you expect all of our users to write all of their messaging
code in Python?
oslo.messaging is a _python_ library.
Zaqar is a service with a REST API -- accessible to any application.
As Zane's sarcastic reply implied, these are as related as sharks are
to tornados. Could they be
On Sep 22, 2014, at 12:19 PM, Gordon Sim g...@redhat.com wrote:
On 09/22/2014 03:40 PM, Geoff O'Callaghan wrote:
That being said I'm not sure why a well constructed zaqar with an rpc
interface couldn't meet the requirements of oslo.messsaging and much more.
What Zaqar is today and what it
On 23/09/2014 1:59 AM, Clint Byrum cl...@fewbar.com wrote:
Geoff, do you expect all of our users to write all of their messaging
code in Python?
oslo.messaging is a _python_ library.
Zaqar is a service with a REST API -- accessible to any application.
No I do not. I am suggesting thaf a
Excerpts from Geoff O'Callaghan's message of 2014-09-22 17:30:47 -0700:
On 23/09/2014 1:59 AM, Clint Byrum cl...@fewbar.com wrote:
Geoff, do you expect all of our users to write all of their messaging
code in Python?
oslo.messaging is a _python_ library.
Zaqar is a service with a
Hi all,
I'm just trying to understand the messaging strategy in openstack.It
seems we have at least 2 messaging layers.
Oslo.messaging and zaqar, Can someone explain to me why there are two?
To quote from the zaqar faq :
-
How does Zaqar compare to oslo.messaging?
oslo.messsaging is
14 matches
Mail list logo
