FileClusterStateProvider plans
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 11
- Avg merge
- 7d 23h
- Merged PRs (30d)
- 3
Description
Originally FileClusterStateProvider was tightly integrated with running a live system. However, now that this code is focused on simulation and not driving the autoscaling algorithm itself, there is a lot of extra code.
But, we want to have some way to look the simulator back up to a live system to make realtime prediction (rather than reading the data from csvs), so we need to make a plan for how to do that.
This one will be a bit more complicated and requires discussion.
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
Start by reviewing FileClusterStateProvider and how the simulator currently reads data from CSVs. Discuss the live-system connection and which code remains necessary, with “done” being an agreed plan for realtime prediction and the simulator’s scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100