Hi,
so I found how to plug into it - one needs to add a routing key to
queue: notification.info
from
bind the following:
topic/exchange: nova
routing key: compute.#
the # is a lazy wildcard matching 0 or more words - you can also use * but
that only matches at most 1 word ;) ... otherwise you'll need to plug into
the queue for every hypervisor - and you dont want to need to do that :)
--
The json payload is a bit weird, it's like a json encapsulating json :
{"oslo.message": "{\"_context_roles\": [\"_member_\"], .... ,
"oslo.version": "2.0"}
Hope it helps someone!
Alex
On 1 October 2014 21:18, Alex Leonhardt <[email protected]> wrote:
> Hi Andy,
>
> Thanks! I guess they come in via the compute queue and I should match
> compute.instance.* to the notification.info queue ?
>
> Alex
>
> On 1 October 2014 19:23, Andy Hill <[email protected]> wrote:
>
>> I believe the notifications you're looking for are:
>>
>> - compute.instance.rebuild.start
>> - compute.instance.rebuild.end
>>
>>
>> -AH
>>
>> On Wed, Oct 1, 2014 at 11:44 AM, Alex Leonhardt <[email protected]>
>> wrote:
>> > HI all,
>> >
>> > I'm looking for the notifications a "rebuild instance" should be
>> publishing,
>> > but I can't seem to see any messages arriving in the "
>> notifications.info"
>> > nor "notifications.error" queue.
>> >
>> > We already use this to dynamically create/delete DNS entries, however,
>> > rebuilding a VM screws with our puppet certs for the client and we will
>> need
>> > to trigger a deletion of the client cert if a rebuild happens.
>> >
>> > Any pointers ?
>> >
>> > Alex
>> >
>> >
>> > _______________________________________________
>> > OpenStack-operators mailing list
>> > [email protected]
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>> >
>>
>
>
_______________________________________________
OpenStack-operators mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
