9:34 a.m.
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.
7:23 p.m.
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(a)redhat.com>
To: "engine-devel" <engine-devel(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
1:46 a.m.
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(a)redhat.com>
To: "Gilad Chaplik" <gchaplik(a)redhat.com>
Cc: "engine-devel" <engine-devel(a)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(a)redhat.com>
> To: "engine-devel" <engine-devel(a)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(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>
_______________________________________________
Engine-devel mailing list
Engine-devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
3:26 a.m.
inline.
----- Original Message -----
From: "Ofri Masad" <omasad(a)redhat.com>
To: "Laszlo Hornyak" <lhornyak(a)redhat.com>
Cc: "Gilad Chaplik" <gchaplik(a)redhat.com>, "engine-devel"
<engine-devel(a)ovirt.org>
Sent: Wednesday, May 29, 2013 9:46:40 AM
Subject: Re: [Engine-devel] oVirt Scheduler API Design
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)
hi Ofri,
the answer is no for both questions.
balance is a periodic task that oVirt (we) use for VM balancing, the user can use it for
all other actions exposed by the REST and not even use our mechanism (return VM=null),
having said that I don't think we should make the api more complicated only because we
want the user to work like us.
so yes the user is responsible to prevent loops and not selecting non-migratable vms.
thanks
Ofri
----- Original Message -----
> From: "Laszlo Hornyak" <lhornyak(a)redhat.com>
> To: "Gilad Chaplik" <gchaplik(a)redhat.com>
> Cc: "engine-devel" <engine-devel(a)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?
JSON is preferable. I use xml because the ovirt-python-sdk supports xml->python
conversion, and when it'll support JSON we'll use that.
> - I am missing from the documentation how the external
scheduler can
> communicate to the engine
XML-RPC
I think it's written there (somewhere :))
>
> Thx,
> Laszlo
>
> ----- Original Message -----
> > From: "Gilad Chaplik" <gchaplik(a)redhat.com>
> > To: "engine-devel" <engine-devel(a)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(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/engine-devel
> >
> _______________________________________________
> Engine-devel mailing list
> Engine-devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>
3:45 a.m.
----- Original Message -----
From: "Gilad Chaplik" <gchaplik(a)redhat.com>
To: "engine-devel" <engine-devel(a)ovirt.org>
Sent: Tuesday, May 28, 2013 5: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.
Adding to users' list for all those asking about the new oVirt
scheduling features. Feel free to review and feedback.
4224
days inactive
4226
days old
4 comments
4 participants
participants (4)
-
Doron Fediuck -
Gilad Chaplik -
Laszlo Hornyak -
Ofri Masad