Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

So is this horse dead now, 'cuz I wanna turn hitting it... First of all, this thread brings up two separate messaging concepts: 1) at-least-once delivery 2) message acknowledgement For #1 - oslo.messaging cannot guarantee that messages will not be duplicated. Specifically in the case of

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

> On 04 Jun 2016, at 04:16, Doug Hellmann wrote: > > Excerpts from Joshua Harlow's message of 2016-06-03 09:14:05 -0700: >> Deja, Dawid wrote: >>> On Thu, 2016-05-05 at 11:08 +0700, Renat Akhmerov wrote: > On 05 May 2016, at 01:49, Mehdi Abaakouk

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

Excerpts from Joshua Harlow's message of 2016-06-03 09:14:05 -0700: > Deja, Dawid wrote: > > On Thu, 2016-05-05 at 11:08 +0700, Renat Akhmerov wrote: > >> > >>> On 05 May 2016, at 01:49, Mehdi Abaakouk >>> > wrote: > >>> > >>> > >>> Le 2016-05-04

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

Deja, Dawid wrote: On Thu, 2016-05-05 at 11:08 +0700, Renat Akhmerov wrote: On 05 May 2016, at 01:49, Mehdi Abaakouk > wrote: Le 2016-05-04 10:04, Renat Akhmerov a écrit : No problem. Let’s not call it RPC (btw, I completely agree with that).

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

On Thu, 2016-05-05 at 11:08 +0700, Renat Akhmerov wrote: On 05 May 2016, at 01:49, Mehdi Abaakouk > wrote: Le 2016-05-04 10:04, Renat Akhmerov a écrit : No problem. Let’s not call it RPC (btw, I completely agree with that). But it’s one of the

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

On Tue, May 10, 2016 at 03:13:46PM -0400, Zane Bitter wrote: The alternative proposed was to create some sort of proxy that listens for notifications, sanitises them and drops them into the appropriate Zaqar queues. So this would be an example that: * Requires at-least-once delivery semantics

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

Excerpts from Zane Bitter's message of 2016-05-10 15:13:46 -0400: > Another data point: at this summit session we discussed delivering to > users notifications about events in the cloud: > https://etherpad.openstack.org/p/newton-alternatives-to-polling > > It's pretty critical that this have

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

Another data point: at this summit session we discussed delivering to users notifications about events in the cloud: https://etherpad.openstack.org/p/newton-alternatives-to-polling It's pretty critical that this have at-least-once delivery semantics, because in future people will be using

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

Dmitry Tantsur wrote: On 05/07/2016 01:00 AM, Joshua Harlow wrote: Dmitry Tantsur wrote: On 05/03/2016 11:24 PM, Joshua Harlow wrote: Howdy folks, So I meet up with *some* of the mistral folks during friday last week at the summit and I was wondering if we as a group can find a path to help

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

On 05/07/2016 01:00 AM, Joshua Harlow wrote: Dmitry Tantsur wrote: On 05/03/2016 11:24 PM, Joshua Harlow wrote: Howdy folks, So I meet up with *some* of the mistral folks during friday last week at the summit and I was wondering if we as a group can find a path to help that project move

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

Dmitry Tantsur wrote: On 05/03/2016 11:24 PM, Joshua Harlow wrote: Howdy folks, So I meet up with *some* of the mistral folks during friday last week at the summit and I was wondering if we as a group can find a path to help that project move forward in their desire to have some kind of

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

So then let's all get onboard https://review.openstack.org/#/c/260246/? I've yet to see what all these things called 'process-than-ack' not seemingly fit into that API in that review. IMHO most of what people are trying to fit into oslo.messaging here isn't really messages but are jobs to be

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

On 05/03/2016 11:24 PM, Joshua Harlow wrote: Howdy folks, So I meet up with *some* of the mistral folks during friday last week at the summit and I was wondering if we as a group can find a path to help that project move forward in their desire to have some kind of process than ack (vs the

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

On 05/04/2016 08:21 AM, Mehdi Abaakouk wrote: Hi, That said, I agree with Mehdi that *most* RPC calls throughout OpenStack, not being idempotent, should not use process-then-ack. That why I think we must not call this RPC. And the new API should be clear the expected idempotent of the

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

> On 05 May 2016, at 01:49, Mehdi Abaakouk wrote: > > > Le 2016-05-04 10:04, Renat Akhmerov a écrit : >> No problem. Let’s not call it RPC (btw, I completely agree with that). >> But it’s one of the messaging patterns and hence should be under >> oslo.messaging I guess, no?

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

Le 2016-05-04 10:04, Renat Akhmerov a écrit : No problem. Let’s not call it RPC (btw, I completely agree with that). But it’s one of the messaging patterns and hence should be under oslo.messaging I guess, no? Yes and no, we currently have two APIs (rpc and notification). And personally I

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

> On 04 May 2016, at 13:21, Mehdi Abaakouk wrote: > > >> That said, I agree with Mehdi that *most* RPC calls throughout OpenStack, >> not being idempotent, should not use process-then-ack. > > That why I think we must not call this RPC. And the new API should be clear >

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

> On 04 May 2016, at 04:47, Dmitriy Ukhlov wrote: > > Hi Joshua. > > I think than Mistral have already fast solution - they customised > oslo.messaging rpc to achieve ack-after-process in Mistral code base Dmitri, I disagree. This is not any kind of a decent solution,

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

Excerpts from Doug Hellmann's message of 2016-05-03 16:45:47 -0500: > Excerpts from Joshua Harlow's message of 2016-05-03 14:24:13 -0700: > > Howdy folks, > > > > So I meet up with *some* of the mistral folks during friday last week at > > the summit and I was wondering if we as a group can find

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

Excerpts from Joshua Harlow's message of 2016-05-03 14:24:13 -0700: > Howdy folks, > > So I meet up with *some* of the mistral folks during friday last week at > the summit and I was wondering if we as a group can find a path to help > that project move forward in their desire to have some kind