garloff
commented
1 year ago Maybe reframing this discussion a bit: If we want to avoid the need to mandate standardized names, we could need three things, IMVHO: (1) We'd still have to define a set of standard flavors, so finding the correct flavor by properties would reliably yield results (2) We'd need to make sure that all relevant parameters are expressed in standardized ways in the flavors. (This goes beyond vCPU/RAM/Disk, so we'd need to define some extra_specs properties. See https://github.com/SovereignCloudStack/standards/issues/74) (3) We'd need to have convenient and robust mechanisms in IaC tools to select a flavor by properties.
@jschoone's observation was about (3) and specifically terraform: We would need a fuzzy matching mechanism, where we could specify what we want and then have a capability in terraform to use the best match in case there are several matches. Would be nice to have some simple logic that would chose the flavor the has the properties that are the closest to the desired min_XXX values and the least unrequested extra capabilities.
fkr
artificial-intelligence
jschoone
mbuechse
As a DevOps team (=SCS user), I want to have the ability to dynamically select an SCS flavor by only providing the needed specifications (RAM, VCPUs, Disk) e.g. with IaC tools so that I don't need to know the existing flavors by name.
It should be possible to use terms like
min-ramandmin-diskto select a proper flavor in case there is no exact match.Inspiration: There is an existing Terraform Data Source which unfortunately is (currently) not able to deal with multiple responses.
Definition of Ready:
Definition of Done: