Open Stack

On 05/16/2013 10:16 PM, Dan Smith wrote:
> I think that the general consensus is that the notion of dynamic
> flavors is an unfavorable approach. Since we happen to be having this
> discussion while an API redesign is happening, I'd say the more
> productive path forward is to figure out how we want per-instance usage
> to be exposed which makes sense both with and without fine-grained
> resource tweaks. Perhaps a flavorRef is the wrong way.
> 
> Right now, if you create an instance from flavor 1, then change the
> parameters of flavor 1, the flavorRef will be wrong anyway. Before I
> moved instance_type information to system_metadata, doing that would
> even cause billing stuff to be incorrect. Lets figure out how to
> represent the actual instance parameters in APIv3, which I think will
> serve everyone's needs.

Sounds like a good plan to me.

As you said, given the timing with the v3 API work, we have an
opportunity to do some refactoring here and do it "right".

-- 
Russell Bryant