Open Stack

2013/9/26 Joe Gordon <joe.gordon0 at gmail.com>:
>> Yes, when moving beyond simple flavours, the idea as initially proposed
>> falls apart.  I see two ways to fix that:
>>
>>  * Don't move beyond simple flavours. Seriously. Amazon have been pretty
>>    darn succesful with just their simple instance types.
> Who says we have to support one scheduler model?  I can see room for several
> scheduler models that have different tradeoffs, such as performance / scale
> vs features/

Sure. I didn't mean necessarily removing the support for richer
instance configurations, but simply making them simple to disable and
thus enable the O(1) scheduler.




-- 
Soren Hansen             | http://linux2go.dk/
Ubuntu Developer         | http://www.ubuntu.com/
OpenStack Developer      | http://www.openstack.org/