redhat-developer / redhat-developer/mapt
[enhancement] Design a way to overcome issues when data for spot instances fails
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 36
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 8
Description
Currently we are experiencing issues getting information to calculate the best spot option. This is breaking all automation which expects to have that information.
We need to overcome this with some solution:
- Mixed approach with partial data (ie. try spot if possible on lowest price if we get it....) otherwise on demand
- Add an option to run on demand if spot info is not available
- Create a long term subsystem as fallback mechanism
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
The issue names no files, tests, or entry points. First inspect the existing spot-price automation and decide which fallback behavior is intended among partial data, on-demand execution, or a long-term subsystem. Done means automation continues when spot-instance data is unavailable, with the chosen behavior tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100