nextflow-io / nextflow-io/nextflow
Fair sharing of azure batch resources
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
New feature
Add a azure.batch.schedulingPriority, similar to the aws batch plugin, to allow prioritizing separate nextflow runs on a shared azure batch environment
Usage scenario
End user submits two runs, one that should obtain Azure Batch resources in priority compared to the other one
Suggest implementation
Modify the plugin to include the schedulingPriority in the AzBatchService job creation
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
Start in plugins/nf-azure/src/main/nextflow/cloud/azure/batch/AzBatchService.groovy at the AzBatchService job creation near line 364. Compare the AWS Batch plugin's schedulingPriority handling, then trace how the Azure job creation receives configuration. Done means separate Nextflow runs can assign priorities that Azure Batch uses to order resource allocation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, groovy
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100