Hi,
Is it possible to put something in there about standardizing the format of
the events on the event bus to a JSON format similar to how the resource
state transition and usage events work?
Jeff
On Wed, Apr 16, 2014 at 10:55 AM, Sonal Ojha wrote:
> Hello ,
>
> I have started putting up thou
Hello ,
I have started putting up thoughts into the wiki article related to
enhancing the cloudstack events.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enhance+cloudstack+events+to+be+more+detailed
Kindly let me know any thoughts / suggestions.
-Sonal
On Wed, Mar 19, 2014 at 6:29
Sonal, you're in
On Wed, Mar 19, 2014 at 11:23 AM, Sonal Ojha wrote:
> Can someone grant me permission to create a page in cwiki?
>
>
> On Tue, Mar 18, 2014 at 4:55 PM, Chip Childers wrote:
>
>> Jira for tracking progress, and a design page on the wiki for any design
>> info.
>>
>> > On Mar 18, 2
Can someone grant me permission to create a page in cwiki?
On Tue, Mar 18, 2014 at 4:55 PM, Chip Childers wrote:
> Jira for tracking progress, and a design page on the wiki for any design
> info.
>
> > On Mar 18, 2014, at 6:34 AM, Sonal Ojha wrote:
> >
> > Shall I go ahead and open a jira item
Jira for tracking progress, and a design page on the wiki for any design info.
> On Mar 18, 2014, at 6:34 AM, Sonal Ojha wrote:
>
> Shall I go ahead and open a jira item on this to add more details?
>
>
>> On Tue, Mar 18, 2014 at 3:59 PM, Sonal Ojha wrote:
>>
>> Hello Nitin,
>>
>> I agree
I just noticed this here. I'm working on a plugin that we've chosen to
implement in an event-based fashion, using the event bus. The event bus
events have basically no information on them, and the database-recorded
events have non-standard description formats which usually have useful
information.
Shall I go ahead and open a jira item on this to add more details?
On Tue, Mar 18, 2014 at 3:59 PM, Sonal Ojha wrote:
> Hello Nitin,
>
> I agree with you, to start with we can replace the event descriptions to
> include the resource UUIDs of the required parameters only. For example,
> DetachIs
Hello Nitin,
I agree with you, to start with we can replace the event descriptions to
include the resource UUIDs of the required parameters only. For example,
DetachIsoCmd needs only virtualMachineId as the required parameter. Hence,
the event description should include the resource UUID for the v
Sonal - This is a great proposal. In addition, you should also include all
the first class entities involved in the event.
Say its a detach iso on a vm - then I should have uuids for both the iso
and the vm. This would definitely help giving more information and in
debugging.
Thanks,
-Nitin
On 1
On #1 I would say “display UUID INSTEAD of the DB id in the events API”.
We should never expose the DB ids to the API caller, especially if the
caller is not an admin. I guess we just never revised the events after
UUIDs were introduced.
On #4. We should distinguish between end user and an admin a
I didn’t see comments from others, but this sounds great to me. More info is
always better IMHO.
On Mar 11, 2014, at 2:31 AM, Sonal Ojha
mailto:sonal.o...@sungard.com>> wrote:
Currently the event logged in CloudStack doesn't give detailed information
about the event that has occurred. The infor
Currently the event logged in CloudStack doesn't give detailed information
about the event that has occurred. The information provided in each event
shown on the cloudstack ui doesn't provide specifics, particularly in case
of errors. For example, the message shown on the cloudstack ui is just
"Err
12 matches
Mail list logo
