[rabbitmq-discuss] Federated Cluster Issue

[Richard Raseley]

I've managed to workaround the second issue I encountered but am not sure
why what I did was required. Once I modified the pattern (as you suggested)
the links came up, attempted to start several times and then sat in a
"shutdown" mode.

The error was telling me that the user I had specified (not sure if in the
URI or the "local username") didn't have access to a
"federation:queue_name" where "queue_name" was one of the queues attached
to the exchange I was federating. Granting that user the .* Configure
permission. Is this permission strictly required when federating a link? If
so - I should consider using a username that is different than the one that
producers and consumers use so that I don't grant them more permissions
than appropriate (as we don't allow dynamic queue creation, etc.).

Regards,

Richard


On Thu, Apr 25, 2013 at 9:30 AM, Richard Raseley <richard at raseley.com>wrote:

> Simon,
>
> Thank you so much for pointing out the error I made. I think the issue
> came down to my lack of understanding on how the expressions are structured
> (don't know very much about regular expressions). I had been thinking that
> a pattern like " ^this\. " would cover everything that had "this" in it
> (e.g. thisthat.andtheother). Yet another thing I need to brush up on. =]
>
> The links now are sitting in a perpetual "starting" state so I may have
> another issue to deal with as well. I will try to troubleshoot that and
> post back if I hit any walls. Thank you.
>
> Regards,
>
> Richard
>
>
> On Thu, Apr 25, 2013 at 3:44 AM, Simon MacMullen <simon at rabbitmq.com>wrote:
>
>> Thanks. In the cases where you've defined a federation policy its pattern
>> is defined as "^expense\.", but the exchanges are named like
>> "expensepay.topic". I suspect you want to change the pattern to
>> "^expensepay\.".
>>
>> Cheers, Simon
>>
>>
>> On 24/04/13 23:56, Richard Raseley wrote:
>>
>>> Simon,
>>>
>>> I will go ahead and send you the requested output directly. Thank you.
>>>
>>> Regards,
>>>
>>> Richard
>>>
>>>
>>> On Wed, Apr 24, 2013 at 6:24 AM, Simon MacMullen <simon at rabbitmq.com
>>> <mailto:simon at rabbitmq.com>> wrote:
>>>
>>>     Hi. I mainly just wanted to check the policies against the exchanges
>>>     - so the lists of all policies and all exchanges should be enough.
>>>     Also feel free to excise anything you think is sensitive and send it
>>>     privately.
>>>
>>>     Cheers, Simon
>>>
>>>
>>>     On 23/04/13 20:16, Richard Raseley wrote:
>>>
>>>         Simon,
>>>
>>>         I did not include the leading and trailing spaces when entering
>>> the
>>>         pattern in the management UI - just did it here for readability
>>>         purposes.
>>>
>>>         I have the output of "rabbitmqctl report" from the 4 nodes in
>>>         question
>>>         (two per cluster) - were there specific items that you wanted to
>>>         look at
>>>         (I'd rather not share the entire output for security reasons)? I
>>>         can see
>>>         that for the vhosts in question it is listing the federate-me
>>> policy
>>>         (not sure if that is what you were looking for).
>>>
>>>         Regards,
>>>
>>>         Richard
>>>
>>>
>>>         On Tue, Apr 23, 2013 at 7:36 AM, Simon MacMullen
>>>         <simon at rabbitmq.com <mailto:simon at rabbitmq.com>
>>>         <mailto:simon at rabbitmq.com <mailto:simon at rabbitmq.com>>> wrote:
>>>
>>>              On 23/04/13 15:28, Richard Raseley wrote:
>>>
>>>                  Simon,
>>>
>>>                  Thank you for your reply.
>>>
>>>                  1) I was trying to obfuscate my actual naming
>>>         conventions - but
>>>                  they are
>>>                  named in a similar manner. The general structure though
>>>         is that in
>>>                  cluster01 I have an exchange named something like
>>>                  "cluster01.topic" and
>>>                  in the pattern field I put " ^cluster01\. " (basically
>>>         everything in
>>>                  preceeding the "." in the exchange name). Can you
>>>         confirm that this
>>>                  would be the correct pattern?
>>>
>>>
>>>              In the quotation marks you have leading and trailing spaces
>>>         which
>>>              would obviously stop the match from working. But other than
>>>         that it
>>>              looks fine.
>>>
>>>
>>>                  2) I do not see "federate-me" show up in the management
>>> UI
>>>                  exchange list
>>>                  - but I see the policy in the Admin section. Would it
>>>         show up as a
>>>                  discrete exchange itself?
>>>
>>>
>>>              Some federation-related infrastructure (including
>>>         exchanges) would
>>>              show up once federation starts, but if you don't see
>>>         "federate-me"
>>>              in the policy column for any exchange then the policy is not
>>>              matching and nothing will happen.
>>>
>>>              If you can post the results of "rabbitmqctl report" then I
>>>         can look
>>>              at why the policy pattern is not matching.
>>>
>>>
>>>              Cheers, Simon
>>>
>>>              --
>>>              Simon MacMullen
>>>              RabbitMQ, VMware
>>>
>>>
>>>
>>>
>>>     --
>>>     Simon MacMullen
>>>     RabbitMQ, VMware
>>>
>>>
>>>
>>
>> --
>> Simon MacMullen
>> RabbitMQ, VMware
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130425/ff5c4bdb/attachment.htm>