Please add your name in here:
In an OpenStack environment, what is the best way to schedule workloads against the correct variant (i.e. revision) of a flavor when using the Compute API? In other words, if there are multiple variants for a given flavor, such as version 1, ver 2, ver 3, etc., what is the best way to utilize the Compute API to instantiate the correct variant for a workload. Two examples are provided, but we are open to other options:
a. Create a new flavor every time a new version of a profile is needed, then overload the flavor’s name w/ the variant. For example, Basic_v1, Basic_v2, etc. API calls would populate flavorRef = Basic_v2, etc.
b. Have a single, static, base flavor name (e.g., Basic), and use a scheduler_hint parameter to identify the variant. In this scenario, API calls would populate flavorRef = Basic, and populate os:scheduler_hints = v2
c. Other ideas?
CONCLUSION: We will synchronize the variant numbers w/ the CNTT release number for the time being. We can revisit this policy n the future, if needed.