Open Stack

> On Apr 6, 2016, at 11:14 AM, Sean Dague <sean at dague.net> wrote:
> 
> On 04/06/2016 01:28 PM, Dean Troyer wrote:
>> On Wed, Apr 6, 2016 at 12:10 PM, Tim Bell <Tim.Bell at cern.ch
>> <mailto:Tim.Bell at cern.ch>> wrote:
>> 
>>    I think Heat needs more of an query engine along the lines of “give me a
>>    flavor with at least X cores and Y GB RAM” rather than hard coding
>>    m1.large.
>>    Core performance is another parameter that would be interesting to
>>    select,
>>    “give me a core with at least 50000 bogomips”
>> 
>> 
>> I've played with a version of OSC's "server create" command that uses
>> --cpu, --ram, etc rather than --flavor to size the created VM.  It is a
>> tiny bit of client-side work to do this, Heat could easily do it too... 
>> The trick is to not get carried away with spec'ing every last detail.
> 
> Or even just put it in Nova.
> 
> GET /flavors/?min_ram=1G&min_cpu=2
> 
> I think would be an entirely reasonable add for the flavors GET call.
> It's an API add, so would need a spec, but it's fundamentally pretty
> easy and probably not very controversial.

Huge, happy, and huggable +1*. 

I see interesting scheduling fun that can come out of this, as well as big interoperability wins.

—j

*I don’t rate anything bigger than a +1, so I have to vary the size and materials to carry emphasis.