redhat-developer / redhat-developer/mapt
[EPIC] Cost calculation
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 36
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 8
Description
One key benefit for mapt is the usage of spot instances, a cool thing to showcase the actual benefit on using it is to show the cost calculation of the execution within mapt (from create to destroy) and compare it with the cost in case for on-demand machines.
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
No files, tests, or entry points are named in the issue, so start by locating the provisioning and instance-lifecycle code. Define how execution time and spot pricing are recorded from creation through destruction, then compare that result with the equivalent on-demand cost for supported providers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100