Open Stack

Le 28/11/2013 17:04, Chris Friesen a écrit :
> On 11/28/2013 09:50 AM, Gary Kotton wrote:
>
>> One option worth thinking about is to introduce a new scheduling 
>> driver to
>> nova - this driver will interface with the external scheduler. This will
>> let us define the scheduling API, model etc, without being in the 
>> current
>> confines of Nova. This will also enable all of the other modules, for
>> example Cinder to hook into it.
>
> I see a couple nice things about this proposal:
>
> 1) Going this route means that we're free to mess with the APIs to 
> some extent since they're not really "public" yet.
>
> 2) Once we have API parity with the current schedulers all in one 
> place then we'll be able to more easily start extracting common stuff.

I agree with Gary. From my POV, I think it's really important to define 
what the interfaces are, what is passed to the scheduler and what is 
given by the scheduler.
Of course, Nova is the first starting point for knowing what to define, 
but we need to make sure the I/Os are enough modular to support any type 
of things to schedule (Cinder backends, Manila FSes, Climate 
compute-hosts and so far...)

-Sylvain