-
> From: "Vinzenz Feenstra"
> To: devel@ovirt.org
> Sent: Monday, July 14, 2014 5:05:17 PM
> Subject: [ovirt-devel] "Host.queryVms": A proposal for new a VDSM API verb
>
> Hi,
>
> This proposal is a follow up on a previous discussion about
> optimizi
Re: [ovirt-devel] "Host.queryVms": A proposal for new a VDSM API
verb
On 07/14/2014 04:05 PM, Vinzenz Feenstra wrote:
Hi,
Since this mail did not receive enough attention I am bumping it again.
For this proposal exists currently a draft patch
http://gerrit.ovirt.org/#/c/28819/
The patch is
On 07/22/2014 02:00 PM, Francesco Romani wrote:
- Original Message -
From: "Vinzenz Feenstra"
To: devel@ovirt.org
Sent: Tuesday, July 22, 2014 11:29:40 AM
Subject: Re: [ovirt-devel] "Host.queryVms": A proposal for new a VDSM API verb
On 07/14/2014 04:05 PM, Vinzenz
- Original Message -
> From: "Vinzenz Feenstra"
> To: devel@ovirt.org
> Sent: Tuesday, July 22, 2014 11:29:40 AM
> Subject: Re: [ovirt-devel] "Host.queryVms": A proposal for new a VDSM API verb
>
> On 07/14/2014 04:05 PM, Vinzenz Feenstra wrote:
>
On 07/14/2014 04:05 PM, Vinzenz Feenstra wrote:
Hi,
Since this mail did not receive enough attention I am bumping it again.
For this proposal exists currently a draft patch
http://gerrit.ovirt.org/#/c/28819/
The patch is not final since the query function should not require to
update all the
On Jul 14, 2014, at 16:20 , Sven Kieske wrote:
> Thanks for this effort, I hope I understand
> this correctly, that your new API still works
> the same way?
> So engine pulls constantly from vdsm?
yes
>
> If I understand the architecture correctly
> this should not be necessary, so vdsm could
Thanks for this effort, I hope I understand
this correctly, that your new API still works
the same way?
So engine pulls constantly from vdsm?
If I understand the architecture correctly
this should not be necessary, so vdsm could
push updates to engine, when there are updates
and engine could just
Hi,
This proposal is a follow up on a previous discussion about
optimizing the communication between VDSM and the ovirt-engine.
Currently the engine polls VDSM every 3 seconds with the `list`
verb to retrieve the status of all VMs. Every 5th time (every 15
seconds) it alternates to 'getAllVmSta
