Open Stack

Chris Behrens wrote:
> There's also discussion about turning the scheduler into its own openstack service… (there may be a blueprint for this already).   As an example, when using volumes with compute, you may want to schedule an instance based on both compute and volume information.  This type of scheduler doesn't belong in nova because volumes live outside.   

Sounds like a discussion for Portland ! Please don't add more to the
already-full grizzly Nova plate :)

> A new scheduling service that knows about 'all of the things' is needed.  When we have that, how scheduling works in nova changes quite a bit.  Nova would ask the scheduler questions and get responses vs proxying messages via it.

Knows about all the things and give mortal services answers to their
questions about the future... Sounds like the name for it should be
"Oracle". Unless that's already taken, in which case I'd suggest "Pythia":

http://en.wikipedia.org/wiki/Pythia

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack