original spec: https://review.opendev.org/#/c/663563 with -2s
The first round of discussion was resulted in no agreement. Then on Friday we revisited the issue based on mdbooth's proposal about composability.
Agreement in the room: * Do not try to change the model of the flavor in nova code and in the db. * Define a "ComposableFlavorBit" (bikeshed on the name please) REST API entity that can hold any kind of flavor bits (extra specs, normal flavor fields), propose some format in the spec for it. This entity can only be created by the admin by default * Extend the server create REST API to allow the end user to specify what "ComposableFlavorBit"s she wants to add to the "base" flavor she used in the create request. * The nova api then merges the "ComposableFalvorBit"s with the base flavor and embed the resulted flavor object into the instance. * Do a similar thing for resize
TODOs: * brinzhang (with possible help from yawang) to re-write the spec
Cheers, gibi