snakemake / snakemake/snakemake-interface-software-deployment-plugins
feat request: make resources available to the plugin
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 2
- Avg merge
- 7m
- Merged PRs (30d)
- 9
Description
Deployment plugins currently don't receive rule-level resource constraints (e.g., threads, resources.mem_mb, resources.gpu).
It would be very useful to pass resource allocation for container tools like podman to enforce them. This would basically turn the scheduler into a userspace container orchestrator.
Proposed Solution
Expose the threads and resources objects to the deployment plugin interface so authors can translate them into native backend flags (including CPU, memory, and accelerators).
rule train_model:
threads: 8
resources:
mem_mb=32000,
gpu=1
So that this becomes:
podman run --cpus=8 --memory=32000m --device nvidia.com/gpu=1 <image>
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 by locating the deployment plugin interface and the handling of rule-level threads and resources; the issue names no files or tests. Done means plugin authors can access these values and translate CPU, memory, and accelerator allocations into backend-specific flags such as the podman example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100