SovereignCloudStack / SovereignCloudStack/cluster-stacks
Use SCS flavors as enum in clusterclasses
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
A good way to deal with flavors that came to my mind was to use the cc.spec.variables.schema.openAPIV3Schema.enum field. Currently we use a string that can have arbitrary values. Now that we generate our clusterclasses already, It would be nice to fetch the scs flavors definitions and to set them automatically as an enum in the clusterclass. We could (debate needed) also set certain flavors for certain tasks (only SSD for controlplane for example).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with providers/openstack/scs/cluster-class/templates/cluster-class.yaml, especially the variables schema referenced in the issue, and compare it with standards/Tests/iaas/scs-0103-v1-flavors.yaml. Trace the existing clusterclass generation process. Done means generated clusterclasses use the SCS flavor definitions as enum values; whether task-specific restrictions are included needs an explicit decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, yaml
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100