Open Stack

On Thu, Feb 21, 2013 at 12:24 PM, Eric Windisch <eric at cloudscaling.com>wrote:

> The more I think about this, the more I think the solution might be:
>
> 1. (Grizzly)  Merge an AMQP-specific check
> 2. (Havana) Merge a message-signing oriented check which will:
>   a) refactor the AMQP-specific check for DYI purposes, without
> significantly affecting its behavior or functionality except as otherwise
> noted below.
>   b) make the AMQP-specific check disable itself if message-signing is
> enabled.
>   c) enable a duplicate-check in rpc-common if message-signing is enabled.
>
> I think this will eliminate both my own concerns for the long-term, the
> concerns regarding ease-of-configuration, as well as the immediate concerns
> for Grizzly.
>
> We'd be eliminating any significant duplication of code through reusing
> the implementation, preventing concerns of forward/backward compatibility
> or double-checking by simply disabling the AMQP-specific code-path when the
> not-backwards-compatible message-signing feature is enabled.
>

Sounds good to me and it looks like we're headed down that path with
https://review.openstack.org/20567: "Needs to skip duplicated messages when
using rabbitmq mirrored queue"

Ray
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130221/69fd50e7/attachment.html>