Re: [openstack-dev] [oslo][messaging] configurable ack-then-process (at least/most once) behavior

2015-12-01 Thread Davanum Srinivas
Bogdan, Which service would use this flag to start with? and how would the code change to provide "app side is fully responsible for duplicates handling"? Thanks, Dims On Tue, Dec 1, 2015 at 4:27 AM, Bogdan Dobrelya wrote: > On 30.11.2015 14:28, Bogdan Dobrelya wrote: >> Hello. >> Please let's

Re: [openstack-dev] [oslo][messaging] configurable ack-then-process (at least/most once) behavior

2015-12-01 Thread Nikola Đipanov
On 11/30/2015 01:28 PM, Bogdan Dobrelya wrote: > Hello. > Please let's make this change [0] happen to the Oslo messaging. > This is reasonable, straightforward and backwards compatible change. And > it is required for OpenStack applications - see [1] - to implement a > sane HA. The only thing left

Re: [openstack-dev] [oslo][messaging] configurable ack-then-process (at least/most once) behavior

2015-12-01 Thread Bogdan Dobrelya
On 30.11.2015 14:28, Bogdan Dobrelya wrote: > Hello. > Please let's make this change [0] happen to the Oslo messaging. > This is reasonable, straightforward and backwards compatible change. And > it is required for OpenStack applications - see [1] - to implement a > sane HA. The only thing left is

[openstack-dev] [oslo][messaging] configurable ack-then-process (at least/most once) behavior

2015-11-30 Thread Bogdan Dobrelya
Hello. Please let's make this change [0] happen to the Oslo messaging. This is reasonable, straightforward and backwards compatible change. And it is required for OpenStack applications - see [1] - to implement a sane HA. The only thing left is to cover this change by unit tests. [0] https://revie