Well, a multi-machine scheduler.

In the HPC world, there are many of these: SLURM, Torque, PBS.

Don't forget Globus and Condor!

How could you overlook (son of) Grid Engine

Well yes, but the elegance here is how they layered their scheduler to be on top of scheduling the resources they paid for at AWS with a meta-scheduler, which when they originally did this was rather novel in the consumer market.

No, the underlying instances were reserved. It reduces to the same problem as scheduling on bare metal.

So, are you saying this is simplistic.?

What is your solution.?

It's not simplistic. It's simple. And a fine solution.

Ah yes, good correction of the statement.

I think we both agree, just that I was more clumsy with my language.

Thanks

Scheduling implies this is simply done on a clock, while this is more about real-time maximization of CPU resources with feedback based on measured load.

> Scheduling implies this is simply done on a clock

That's a very outdated definition of scheduling in regards to cloud computing. The schedulers of Mesos, Omega, Borg, etc. all do allow for CPU-load based scheduling, and have schedulers for other scenarios.