On Sun, Jul 21, 2013 at 10:29:03PM +0300, Itamar Heim wrote:
> On 07/21/2013 12:14 PM, Dan Kenigsberg wrote:
> >Introducing a new verb, getMigrationStatuses(), would allow Engine to
> >collect this piece of statistics in the exact frequency that it needs
> >it. Coupling this data with the frequently-polled state of VM begs for
> >future complaints that getVMList(full=False) is too heavy, and that we
> >must introduce getVMList(full=False, veryveryskinny=True).
> so the most likely outcome is engine would be calling this every
> time it calls getAllVmStats?
Having two different verbs allows the client to play with the frequency
of polling. Last word I've heard was that getAllVmStats is too heavy to
be called in the frequency that getMigrationStatuses is needed.
If Engine is happy to lock the frequency of getMigrationStatuses to that
of getAllVmStats, we can include migrateStatus within getAllVmStats. I
already conceded to this earlier in this thread.
vdsm-devel mailing list