openmcp-project / openmcp-project/backlog
Epic: Dynamic Cross Charging
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Understand the Epic
Define and implement a feature for the cross charging mechanism which takes into account that some mcp-worker shoot clusters have been adjusted in size/resource usage.
Context / Background
Currently, we apply cross charging equally on all our mcp-worker shoots. However, we recently had to increase the sizes of certain mcp-worker shoots based on user requests and needs. In order to reflect this additional recource usage in the charging, we see the need to adapting our cross charging mechanism by e.g. apply a certain factor to the calculation for shoots that were adjusted in size.
User Stories or tasks
No response
What is required to accept the Epic as finished.
- An ADR/concept of dynamic cross charging is created, discussed and approved
- dynamic cross charging is implemented
- dynamic cross charging is validated to charge correct amounts
- New cost calculation is disclosed to users
- dynamic cross charging is running on landscape all landscapes where cross charging needs to be active
Dependencies of this Epic
- ControlPlane (V2) support for cross charging
- dynamic worker nodes / control planes on V2 (unclear right now)
Risks of this Epic
No response
Known Stakeholders of this Epic
No response
Milestone Definitions for this Epic.
No response
Metrics Definition for this Epic.
No response
Any further valuable resources.
No response
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 clarifying the ControlPlane V2 and dynamic worker-node dependencies, then read the acceptance checklist and develop the required ADR/concept before implementation. Done means the concept is approved, dynamic charging is implemented and validated, costs are disclosed, and it runs on all required landscapes.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100