Introduce Provider-Neutral Configs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 1
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 6
Description
Summary
Create a ComputeConfig and StorageConfig classes for provider neutral configuration. This will help with standardizing the package and can help pick the right VM based on compute info.
Example: ComputeConfig(cpu=16, memory = "64GB", gpu=1)
Blockers/Related work
Note blockers here and in the relationship panel
Definition of Done
Create the two config classes.
Expected amount of work (days)
4
Remove question label once details are complete, change task to bug if bug.
Contributor guide
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
No files, tests, or entry points are named. Start by locating the package's configuration entry points and existing provider-specific configuration, then use the ComputeConfig example and the Definition of Done to scope the work. Done means both ComputeConfig and StorageConfig classes are created.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100