On 29/05/12 09:03, Itamar Heim wrote:
> On 05/29/2012 08:56 AM, Livnat Peer wrote:
>> On 28/05/12 21:31, Itamar Heim wrote:
>>> On 05/28/2012 02:35 PM, Ori Liel wrote:
Quite a few people liked flow-id, and no one objected to it
explicitly, so I'll just go with that.
If someone f
On 05/29/2012 08:56 AM, Livnat Peer wrote:
On 28/05/12 21:31, Itamar Heim wrote:
On 05/28/2012 02:35 PM, Ori Liel wrote:
Quite a few people liked flow-id, and no one objected to it
explicitly, so I'll just go with that.
If someone feels strongly against, please reply.
I still like 'label' be
>>
>> Ori
>>
>> - Original Message -
>> From: "Michael Pasternak"
>> To: "Moti Asayag"
>> Cc: "Ori Liel", engine-devel@ovirt.org
>> Sent: Monday, May 28, 2012 2:26:10 PM
>> Subject: Re: [Engine-devel] REST-API: Exp
ak"
To: "Moti Asayag"
Cc: "Ori Liel", engine-devel@ovirt.org
Sent: Monday, May 28, 2012 2:26:10 PM
Subject: Re: [Engine-devel] REST-API: Exposing correlation-ID
On 05/15/2012 05:31 PM, Moti Asayag wrote:
On 05/14/2012 02:19 PM, Ori Liel wrote:
No decision about the name o
virt.org
Sent: Monday, May 28, 2012 2:26:10 PM
Subject: Re: [Engine-devel] REST-API: Exposing correlation-ID
On 05/15/2012 05:31 PM, Moti Asayag wrote:
> On 05/14/2012 02:19 PM, Ori Liel wrote:
>> > No decision about the name of the parameter yet, and this is blocking m
On 05/15/2012 05:31 PM, Moti Asayag wrote:
> On 05/14/2012 02:19 PM, Ori Liel wrote:
>> > No decision about the name of the parameter yet, and this is blocking me.
>> >
>> > Names that were suggested so far:
>> >
>> > * flow-id
+1
--
Michael Pasternak
RedHat, ENG-Virtualization R&D
On 05/16/2012 12:18 AM, Itamar Heim wrote:
> On 05/15/2012 05:44 PM, Miki Kenneth wrote:
>>
>>
>> - Original Message -
>>> From: "Itamar Heim"
>>> To: "Eoghan Glynn"
>>> Cc: engine-devel@ovirt.org
>>> Sent: Monda
On 05/15/2012 05:44 PM, Miki Kenneth wrote:
- Original Message -
From: "Itamar Heim"
To: "Eoghan Glynn"
Cc: engine-devel@ovirt.org
Sent: Monday, May 14, 2012 7:07:07 PM
Subject: Re: [Engine-devel] REST-API: Exposing correlation-ID
On 05/14/2012 07:05 PM
- Original Message -
> From: "Itamar Heim"
> To: "Eoghan Glynn"
> Cc: engine-devel@ovirt.org
> Sent: Monday, May 14, 2012 7:07:07 PM
> Subject: Re: [Engine-devel] REST-API: Exposing correlation-ID
>
> On 05/14/2012 07:05 PM, Eoghan
_entry_id' (although I consider some of the other options
> viable as well). Does someone disagree with 'log_entry_id'?
>
> Thanks,
>
> Ori.
>
> - Original Message -
> From: "Itamar Heim"
> To: "Eoghan Glynn"
> Cc: &
On 05/14/2012 07:05 PM, Eoghan Glynn wrote:
* MetaTask-ID
-1, too pompous?
Me, pompous? Never! ;)
a maybe to remove the "ID" from name, since there is no uniqueness
guarantee.
Sure, MetaTask-Tag for example would be less connoting of uniqueness.
I like 'Tag'
only problem is we have t
> >> * MetaTask-ID
>
> -1, too pompous?
Me, pompous? Never! ;)
> a maybe to remove the "ID" from name, since there is no uniqueness
> guarantee.
Sure, MetaTask-Tag for example would be less connoting of uniqueness.
But in general, I'd +1 any of the options that aren't suggestive of
this bein
on_id sounds best to me.
Thanks,
Ori.
- Original Message -
From: "Itamar Heim"
To: "Eoghan Glynn"
Cc: "Ori Liel", engine-devel@ovirt.org
Sent: Tuesday, May 8, 2012 12:40:25 PM
Subject: Re: [Engine-devel] REST-API: Exposing correlation-ID
On 05/0
quot;
> Cc: "Ori Liel" , engine-devel@ovirt.org
> Sent: Tuesday, May 8, 2012 12:40:25 PM
> Subject: Re: [Engine-devel] REST-API: Exposing correlation-ID
>
> On 05/08/2012 12:00 PM, Eoghan Glynn wrote:
>>
>>
>>>>>>> 1) what's t
.org
Sent: Tuesday, May 8, 2012 12:40:25 PM
Subject: Re: [Engine-devel] REST-API: Exposing correlation-ID
On 05/08/2012 12:00 PM, Eoghan Glynn wrote:
>
>
>>>>>> 1) what's the name you'd give this parameter? job-id? batch-id?
>>>>>> flow-id? command
On 05/08/2012 12:00 PM, Eoghan Glynn wrote:
1) what's the name you'd give this parameter? job-id? batch-id?
flow-id? command-id? correlation-id???
job-id will confuse us with engine's job-id which is a single
command
today.
correleation-id is pretty long and confusing as implies on
correlati
> >> >> 1) what's the name you'd give this parameter? job-id? batch-id?
> >> >> flow-id? command-id? correlation-id???
> >>
> >> job-id will confuse us with engine's job-id which is a single
> >> command
> >> today.
> >> correleation-id is pretty long and confusing as implies on
> >> correlation
- Original Message -
> From: "Ayal Baron"
> To: "Ori Liel"
> Cc: engine-devel@ovirt.org
> Sent: Sunday, May 6, 2012 11:45:22 PM
> Subject: Re: [Engine-devel] REST-API: Exposing correlation-ID
>
>
>
> - Original Message
- Original Message -
> >> On 05/06/2012 10:03 AM, Ori Liel wrote:
> >> > Still need to decide about this:
> >> >
> >> >> 1) what's the name you'd give this parameter? job-id? batch-id?
> >> >> flow-id? command-id? correlation-id???
> >>
> >> job-id will confuse us with engine's job-id wh
>> On 05/06/2012 10:03 AM, Ori Liel wrote:
>> > Still need to decide about this:
>> >
>> >> 1) what's the name you'd give this parameter? job-id? batch-id?
>> >> flow-id? command-id? correlation-id???
>>
>> job-id will confuse us with engine's job-id which is a single command
>> today.
>> correlea
> On 05/06/2012 10:03 AM, Ori Liel wrote:
> > Still need to decide about this:
> >
> >> 1) what's the name you'd give this parameter? job-id? batch-id?
> >> flow-id? command-id? correlation-id???
>
> job-id will confuse us with engine's job-id which is a single command
> today.
> correleation-id i
On 05/06/2012 10:03 AM, Ori Liel wrote:
Still need to decide about this:
1) what's the name you'd give this parameter? job-id? batch-id?
flow-id? command-id? correlation-id???
job-id will confuse us with engine's job-id which is a single command today.
correleation-id is pretty long and confu
Still need to decide about this:
>1) what's the name you'd give this parameter? job-id? batch-id?
>flow-id? command-id? correlation-id???
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
On 05/03/2012 09:49 PM, Ori Liel wrote:
...
Hi Ori,
Is the intent here to allow correlation between multiple backend actions
initiated from a single restapi call, or an over-arching correlation
across multiple restapi calls?
If the former, then I'd agree with Yaniv, just generate the ID intern
- Original Message -
From: "Itamar Heim" >
To: "Eoghan Glynn" >
Cc: "Ori Liel" >, engine-devel@ovirt.org
Sent: Thursday, May 3, 2012 7:10:32 PM
Subject: Re: [Engine-devel] REST-API: Exposing correlation-ID
On 05/03/2012 06:15 PM, Eoghan Glynn
On 05/03/2012 06:15 PM, Eoghan Glynn wrote:
Correlation-ID feature allows 'tagging' a call to a Backend command
with a String ID, and this ID will be appended to all log messages
that result from this command.
http://www.ovirt.org/wiki/Features/TaskManagerDetailed
In REST-API, we would like
On 05/03/2012 05:34 PM, Yaniv Kaul wrote:
On 05/03/2012 05:24 PM, Ori Liel wrote:
Correlation-ID feature allows 'tagging' a call to a Backend command
with a String ID, and this ID will be appended to all log messages
that result from this command.
http://www.ovirt.org/wiki/Features/TaskManagerD
> Correlation-ID feature allows 'tagging' a call to a Backend command
> with a String ID, and this ID will be appended to all log messages
> that result from this command.
>
> http://www.ovirt.org/wiki/Features/TaskManagerDetailed
>
> In REST-API, we would like to enable the user to pass a
> co
On 05/03/2012 05:24 PM, Ori Liel wrote:
Correlation-ID feature allows 'tagging' a call to a Backend command
with a String ID, and this ID will be appended to all log messages
that result from this command.
http://www.ovirt.org/wiki/Features/TaskManagerDetailed
In REST-API, we would like to enab
Correlation-ID feature allows 'tagging' a call to a Backend command
with a String ID, and this ID will be appended to all log messages
that result from this command.
http://www.ovirt.org/wiki/Features/TaskManagerDetailed
In REST-API, we would like to enable the user to pass a correlation-ID
when
30 matches
Mail list logo
