Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-29 Thread Itamar Heim
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'

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-29 Thread Livnat Peer
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 feels strongly

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-28 Thread Livnat Peer
Cc: Ori Lielol...@redhat.com, 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 of the parameter yet

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-15 Thread Miki Kenneth
- Original Message - From: Itamar Heim ih...@redhat.com To: Eoghan Glynn egl...@redhat.com 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 Glynn wrote: * MetaTask

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-15 Thread Itamar Heim
On 05/15/2012 05:44 PM, Miki Kenneth wrote: - Original Message - From: Itamar Heimih...@redhat.com To: Eoghan Glynnegl...@redhat.com 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

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-14 Thread Ori Liel
, 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-id? correlation-id??? job-id will confuse us with engine's job-id which

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-14 Thread Yair Zaslavsky
: [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-id? correlation-id??? job-id will confuse us with engine's job-id which is a single command today. correleation-id

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-14 Thread Eoghan Glynn
* 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 being a

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-14 Thread Itamar Heim
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

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-08 Thread Itamar Heim
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

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-06 Thread Ori Liel
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

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-06 Thread Itamar Heim
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

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-06 Thread Mike Kolesnik
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

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-06 Thread Ayal Baron
- 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 which is a single command

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-06 Thread Gilad Chaplik
- Original Message - From: Ayal Baron aba...@redhat.com To: Ori Liel ol...@redhat.com 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 - On 05/06/2012 10:03 AM, Ori Liel

[Engine-devel] REST-API: Exposing correlation-ID

2012-05-03 Thread Ori Liel
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

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-03 Thread Yaniv Kaul
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

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-03 Thread Eoghan Glynn
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

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-03 Thread Itamar Heim
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.

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-03 Thread Itamar Heim
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

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-03 Thread Ori Liel
- Original Message - From: Itamar Heim ih...@redhat.com To: Eoghan Glynn egl...@redhat.com Cc: Ori Liel ol...@redhat.com, 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

Re: [Engine-devel] REST-API: Exposing correlation-ID

2012-05-03 Thread Itamar Heim
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