Batch
How can we improve Azure Batch? Do you have an idea, suggestion or feedback based on your experience? We would love to hear it!
-
61 votes
-
Implement local Batch emulation
Please allow full emulation of Batch jobs to facilitate local development and testing prior to deployment.
54 votes -
Add diagnostics support for Azure Batch
Currently Azure Batch does not support diagnostics/telemetry/performance counters. It would be really useful to have something like a New relic or an App insights integration.
33 votesThanks for the suggestion. We are actively working on diagnostic feature for Azure Batch service.
-
Support on Premise Batch Nodes
It would be great to have support for on-premise nodes to support hybrid workloads. This could help with connectivity issues for specific types of specialized data sources. Having a "Batch Agent" that could be installed on any server so it can register in a pool and be sent work would be really valuable.
21 votesInteresting idea. Hybrid scenario is definitely something we will look at. Have you tried Windows HPC?
-
Jobs of equal priority should be executed in submission order
If I have a fixed number of dedicated VMs, then it is important that queued jobs run in submission order. Sure I could use the priority to achieve this, but then I can't use priority for real business use case prioritisation. Sure I could reserve priority ranges, but this is getting complicated when it should just process them in submission order.
15 votes -
Allow use of a container as single resource for a task
Currently the resource files have a 32k character limitation which caps the number of files you can upload or nested folder structures. If you could supply just a container and use all the blobs in the container as a resource then it would simplify this.
The current work around is to use/install zip utilities or use application packages which do not have a rest api.
11 votesWork is underway in this area.
-
Allow initial value for TargetDedicated when autoscale is enabled for a pool.
Otherwise it takes at least 5 minutes to start the tasks!
9 votes -
Deploy certificate from Azure Key Vault to compute node
Rather than having to associate a certificate with a pool, being able to associate a certificate in a Key Vault that's been created with the -EnabledForDeployment flag would help centralize management of certificates being deployed to both VM's and Batch nodes.
8 votes -
Virtual Network Support for Marketplace Batch VMs (ARM)
CloudService based batch compute nodes already have VNet support.
6 votes -
Support deployment through Azure Resource Manager
Setting up a new batch account together with a pool should be supported through Azure Resource Manager.
4 votes -
4 votes
Work is underway in this area.
-
Visual Studio Project - Batch Application
There needs to be a simpler way to deploy Batch Applications, preferably directly from Visual Studio.
Having a mechanism to deploy my Azure Batch programs directly to my Batch Applications with a method similar to deploying Azure Web Apps would save heaps of time.
3 votes -
Support os family 5
OS Family 5 is out, and we need 4.6 support
3 votesWe are actively working to roll out support for OS Family 5.
If you are able to use VirtualMachine / Marketplace configuration for your scenario, Windows Server 2016 is already available as an option.
-
Job cancellation support
Improve Batch API to support job cancellation in an async/await fashion.
3 votes -
Allow a way to add RequestOptionsPolicy in CloudTask/CloudJob's CustomBehaviour Collection for calls to Blob Storage
We are encrypting the files before uploading to Blob Storage by specifying Encryption Policy in RequestOptions.
These files are later used as the ResourceFiles to the CloudTask but there is no way to specify the Encryption Policy.
3 votesThanks for the suggestion. For now you can use Azure Storage library to achieve this on your own. We are working with Azure storage team to deliver an end to end storage integration story. More to see in the future.
-
Setting up Azure Batch needs to be easier
To start with, there should be no need to use any assemblies etc in order to create a new batch process.
All it should take is some configuration - could be some JSON payload - that can be transmitted using the Batch APIs.
That content should determine what executable file to start, what CLI parameters to pass on, etc. On top, it should all work like within a regular folder structure - whatever you need, you just drop it e. g. via FTP or APIs again to some location and then you have your dosomething.exe file in the root dir,…2 votesWork in this area is underway.
- Don't see your idea?
