Hi Gilad, two questions about the 'balance' api. 1. do we filter out all VMs which cannot be migrated before passing the list to the 'balance' method? otherwise, the user-implemented code may select a VM which cannot be migrated for some reason. 2. do we make sure that the user-implemented 'balance' method do not select the same VM over and over again? if the 'balance' selects a non-migrateable VM (like described in 1 above) the VM will not migrate and the exact same input will be passed again. (infinite loop) thanks Ofri ----- Original Message -----
From: "Laszlo Hornyak" <lhornyak@redhat.com> To: "Gilad Chaplik" <gchaplik@redhat.com> Cc: "engine-devel" <engine-devel@ovirt.org> Sent: Wednesday, May 29, 2013 3:23:12 AM Subject: Re: [Engine-devel] oVirt Scheduler API Design
Hi Gilad,
Some questions to start the discussion :) External scheduler API: - Why are you mixing xml into json? - I am missing from the documentation how the external scheduler can communicate to the engine
Thx, Laszlo
----- Original Message -----
From: "Gilad Chaplik" <gchaplik@redhat.com> To: "engine-devel" <engine-devel@ovirt.org> Sent: Tuesday, May 28, 2013 4:34:11 PM Subject: [Engine-devel] oVirt Scheduler API Design
Hi all,
Attached links for oVirt Scheduler API design wiki page.
High level overview: http://www.ovirt.org/Features/oVirtScheduler Detailed design: http://www.ovirt.org/Features/oVirtSchedulerAPI
You are more than welcome to share you thoughts.
Thanks, Gilad. _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel