cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Murali Reddy <Murali.Re...@citrix.com>
Subject Re: event bus details
Date Tue, 25 Jun 2013 12:05:33 GMT

Opened bug CLOUDSTACK-3190 for this.

On 25/06/13 4:03 PM, "Murali Reddy" <Murali.Reddy@citrix.com> wrote:

>
>Marcus,
>
>Events bus framework with current AMQP default implementation, has routing
>key with format 
>'Eventsource.EventCategory.EventType.EntityType.EntityUUID' as described
>in [1]. If you see from the log you pasted below events of type
>'ResourceStateEvent' has details of entity UUID. Since it was new event
>type and was added in 4.1 it was easy to design so that all the entity
>details are published. Also intention of this event was for programatic
>consumption of events by external entities.
>
>Action Events existed from long time, and was implemented and used
>primarily for auditing messages for non-programmtic use. Unfortunately
>there is huge number of places for different actions corresponding to
>different entities need to be cleaned up. Please file a bug for some one
>to pick it up and work on it.
>
>[1] http://s.apache.org/MZS
>
>Thanks,
>Murali
>
>On 25/06/13 9:53 AM, "Marcus Sorensen" <shadowsor@gmail.com> wrote:
>
>>Here's another, when deleting a VPC. I see the details of all of the
>>things it's doing (removing the router, networks, etc), but I can't
>>tell which VPC was being deleted. I feel like that '*' under
>>ActionEvent should be telling me the uuid, like that position does in
>>the other events:
>>
>>[x] 
>>'management-server.ActionEvent.VPC-DELETE.Vpc.*':'{"status":"Scheduled","
>>e
>>vent":"VPC.DELETE","account":"f668198a-bbdf-11e2-8bb5-52540014c04d","user
>>"
>>:"f66f14d8-bbdf-11e2-8bb5-52540014c04d"}'
>> [x] 
>>'management-server.ResourceStateEvent.StopRequested.Network.b18e3e07-aed0
>>-
>>473a-aeb2-bfad00bfb236':'{"id":"b18e3e07-aed0-473a-aeb2-bfad00bfb236","ol
>>d
>>-state":"Running","new-state":"Stopping","resource":"Network"}'
>> [x] 
>>'management-server.ResourceStateEvent.OperationSucceeded.Network.b18e3e07
>>-
>>aed0-473a-aeb2-bfad00bfb236':'{"id":"b18e3e07-aed0-473a-aeb2-bfad00bfb236
>>"
>>,"old-state":"Stopping","new-state":"Stopped","resource":"Network"}'
>> [x] 
>>'management-server.ResourceStateEvent.ExpungeOperation.Network.b18e3e07-a
>>e
>>d0-473a-aeb2-bfad00bfb236':'{"id":"b18e3e07-aed0-473a-aeb2-bfad00bfb236",
>>"
>>old-state":"Stopped","new-state":"Expunging","resource":"Network"}'
>> [x] 
>>'management-server.ResourceStateEvent.DestroyRequested.Volume.5dca4da7-d4
>>2
>>8-4f6f-a474-11eee55fdf3a':'{"id":"5dca4da7-d428-4f6f-a474-11eee55fdf3a","
>>o
>>ld-state":"Ready","new-state":"Destroy","resource":"Volume"}'
>> [x] 
>>'management-server.ResourceStateEvent.DestroyRequested.Volume.5dca4da7-d4
>>2
>>8-4f6f-a474-11eee55fdf3a':'{"id":"5dca4da7-d428-4f6f-a474-11eee55fdf3a","
>>o
>>ld-state":"Ready","new-state":"Destroy","resource":"Volume"}'
>> [x] 
>>'management-server.ResourceStateEvent.OperationSucceeded.Volume.5dca4da7-
>>d
>>428-4f6f-a474-11eee55fdf3a':'{"id":"5dca4da7-d428-4f6f-a474-11eee55fdf3a"
>>,
>>"old-state":"Destroy","new-state":"Destroy","resource":"Volume"}'
>> [x] 
>>'management-server.ResourceStateEvent.OperationSucceeded.Volume.5dca4da7-
>>d
>>428-4f6f-a474-11eee55fdf3a':'{"id":"5dca4da7-d428-4f6f-a474-11eee55fdf3a"
>>,
>>"old-state":"Destroy","new-state":"Destroy","resource":"Volume"}'
>>...
>>
>>On Mon, Jun 24, 2013 at 10:11 PM, Marcus Sorensen <shadowsor@gmail.com>
>>wrote:
>>> Hi all,
>>>    I've been playing around with the new event bus, trying to see if
>>> it could be useful, and I'm a bit confused about the output. If I
>>> subscribe to all topics, and try to reboot a virtual machine, this is
>>> all I see:
>>>
>>> 
>>>'management-server.ActionEvent.VM-REBOOT.VirtualMachine.*':'{"status":"S
>>>c
>>>heduled","event":"VM.REBOOT","account":"f66d4d60-bbdf-11e2-8bb5-52540014
>>>c
>>>04d","user":"f66f14d8-bbdf-11e2-8bb5-52540014c04d"}'
>>>
>>> I see the account info, but nothing about which VM is being rebooted.
>>>
>>> If I try to stop/start a VM, I likewise see no details in the
>>> ActionEvent, about the subject being acted upon:
>>>
>>> 
>>>'management-server.ActionEvent.VM-STOP.VirtualMachine.*':'{"status":"Sch
>>>e
>>>duled","event":"VM.STOP","account":"f66d4d60-bbdf-11e2-8bb5-52540014c04d
>>>"
>>>,"user":"f66f14d8-bbdf-11e2-8bb5-52540014c04d"}'
>>>
>>> I do however see some details regarding a 'Network' resource, though
>>> if I were to write something to parse this output I wouldn't
>>> immediately know that it was related to a VM (note the 'id' here
>>> actually matches the VM I'm stopping, but there's nothing in the event
>>> to tell me it's a VM):
>>>
>>> 
>>>'management-server.ResourceStateEvent.StopRequested.Network.d287a0fa-6b3
>>>b
>>>-4e8b-8fb2-2677778ec32c':'{"id":"d287a0fa-6b3b-4e8b-8fb2-2677778ec32c","
>>>o
>>>ld-state":"Running","new-state":"Stopping","resource":"Network"}'
>>>
>>> I'm just subscribing to "#", so I assume I'm getting everything, but
>>> I'm just having trouble making sense of the output.
>>
>
>
>



Mime
View raw message