MatterMiners / MatterMiners/lapis
Assignment of more than one job to a single machine in Classad-Scheduler
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
The Classad-Scheduler currently assigns only one job per machine during one scheduling cycle as otherwise the underlying clusters would change meaning, that for each job each machine cluster would have to be skipped.
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
Start at the Classad-Scheduler scheduling cycle and trace how a machine is assigned to a job and how underlying clusters are represented. Determine how multiple assignments could preserve the current cluster semantics; done means one machine can receive more than one job in a cycle without requiring each job to skip that machine's cluster.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100