Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flavor specs: Add rationale for encoding info into names #73

Closed
garloff opened this issue Jun 21, 2022 · 1 comment
Closed

Flavor specs: Add rationale for encoding info into names #73

garloff opened this issue Jun 21, 2022 · 1 comment

Comments

@garloff
Copy link
Contributor

garloff commented Jun 21, 2022

While we encourage to use the short names in the SCS flavor naming, we do have the capability to encode a lot of details into the flavor names. This is useful, as we may have (large) clouds, where customers have the ability to chose between very finegrained flavor types for selecting capabilities and we need to do this by chosing the flavor names. (The mechanism to use extra_specs and match it with images is broken -- requiring custom images just to be able to select the right VM flavor is a concept broken by design IMVHO.)
We should clarify this in the docs.

@garloff
Copy link
Contributor Author

garloff commented Mar 3, 2023

Addressed by #121.

@garloff garloff closed this as completed Mar 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant