nextflow
nextflow copied to clipboard
nextflow-io
4920: Azure Batch supports process.disk directive
This PR adds the process.disk directive support to Azure Batch. After adding this directive, Azure Batch will:
- Factor disk and VM disk size into the number of slots a single task occupies
- Create autopools that use VMs with sufficiently large enough storage disks for a single Azure Batch task
Deploy Preview for nextflow-docs-staging canceled.
| Name | Link |
|---|---|
| Latest commit | f1d0d1d7c2d6bb2dabb603e5deae1cfbd815f573 |
| Latest deploy log | https://app.netlify.com/sites/nextflow-docs-staging/deploys/67aca4b3712595000878d6b2 |
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
If anyone fancies being a rubber duck, I can't work out why the best match for northeurope is a Standard_B4ls_v2 instead of a Basic_A3 now, especially when a Standard_B4ls_v2 has zero disk attached!
@bentsherman after many long hours and mental calculations about slots, I've finally finished this one.
The only problem I've found is it doesn't account for existing the funnel for cacheing the pool after creation. Not sure how necessary this is but it currently has no awareness of the cpus, memory and disk, just the name. But I wonder if this is indicating I'm missing something?
Closing in favour of https://github.com/nextflow-io/nextflow/pull/5784 which is on the right fork