livepeer / livepeer/go-livepeer
Ability to reserve capacity for a specific Broadcaster
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 586
- Forks
- 226
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 19
Description
Is your feature request related to a problem? Please describe.
Having the ability to reserve capacity/sessions for a specific Broadcaster to allow Orchestrators to guarantee availability for Broadcasters that commit to a specific amount of work.
Describe the solution you'd like
The ability to reserve capacity for a specific Broadcaster
Describe alternatives you've considered
Having a dedicated node(s) for a specific client
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 tracing how broadcasters, orchestrators, and capacity or sessions are represented and allocated. Done should define and implement the reservation behavior for a specific broadcaster, including its interaction with the alternative of dedicated nodes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100