- Original Message -
> On 04/24/2012 07:37 PM, Ayal Baron wrote:
> >
> > - Original Message -
> >> On 04/24/2012 02:07 AM, Ayal Baron wrote:
> >>> - Original Message -
> On 04/22/2012 12:28 PM, Ayal Baron wrote:
> >>> This way we'd have a 2 stage process:
> >>
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 wrote:
>>
>>
>>> Correlation-ID feature allow
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
On 05/03/2012 06:43 PM, Doron Fediuck wrote:
On 03/05/12 17:56, Shu Ming wrote:
Hi,
I am checking the VDSM and ovirt-engine workspace for "vds_bootstrap.py" file. It was found
that vds_bootstrap.py file was in VDSM workspace and was packaged into vdsm-bootstrap rpm package. Also, it
was
On 03/05/12 17:56, Shu Ming wrote:
> Hi,
> I am checking the VDSM and ovirt-engine workspace for "vds_bootstrap.py"
> file. It was found that vds_bootstrap.py file was in VDSM workspace and was
> packaged into vdsm-bootstrap rpm package. Also, it was found that in the
> host installation pr
On 04/25/2012 04:52 PM, Deepak C Shetty wrote:
This seems interesting.
I am interested in pursuing this further and helping contribute to the
vdsm lsm integration. lsm is still in the early stages, but i feel its
the right time to start influencing it so that vdsm integration can be
smooth.
> 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
Hi,
I am checking the VDSM and ovirt-engine workspace for
"vds_bootstrap.py" file. It was found that vds_bootstrap.py file was in
VDSM workspace and was packaged into vdsm-bootstrap rpm package. Also,
it was found that in the host installation process, host node will try
to get the "vds_b
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
Hi,
Thanks for the input. Please see my inline comments.
Thanks
Gary
On 05/03/2012 12:02 PM, Irena Berezovsky wrote:
Gary,
Thank you for a very detailed proposal.
I would like to address several issues of the proposed Quantum-oVirt
integration.
1. User Interface:
Network Management
I suggest t
> >> The new design of logical network 'usages' collection came out a
> >> bit
> >> problematic or shall i say annoying.
> >> The idea is to send the entire collection elements every time a
> >> user
> >> wants to update a single usage otherwise the missing elements will
> >> be
> >> automaticall
Gary,
Thank you for a very detailed proposal.
I would like to address several issues of the proposed Quantum-oVirt
integration.
1. User Interface:
Network Management
I suggest to consider Logical Network Management to indicate if the Network
should be managed by Quantum or not. This may lead to
15 matches
Mail list logo
