nextflow-io / nextflow-io/nextflow
Deprecation of Azure Low Priority VMs
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
Azure Low Priority VMs are going away: https://learn.microsoft.com/en-us/azure/batch/low-priority-vms-retirement-migration-guide
For Nextflow, this means a user using Azure low priority VM pools in a Batch Managed account will fail.
We should handle this with a clear error message or failure so a user understands the issue and knows how to deal with it.
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 with the Azure Batch low-priority VM retirement and migration guide, then inspect linked PR #6267 to understand the work already in progress. Confirm that a Batch Managed account configured with low-priority VM pools produces a clear failure explaining the retirement and the available migration path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, groovy
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100