From a45ac7b8ef9f8ee8059caacd06c76011ad3fa857 Mon Sep 17 00:00:00 2001
From: Adam Talbot <12817534+adamrtalbot@users.noreply.github.com>
Date: Fri, 4 Oct 2024 11:32:57 +0100
Subject: [PATCH] Use machineType for Azure Batch configuration instead of

An idea to use process.machineType instead of a specific VM image. This will mean the autopools feature will be used fully and appropriate sized VM pools will be created for every process.

Also switched to E*d_v5 based on the Azure blog.
---
 conf/azurebatch.config | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/conf/azurebatch.config b/conf/azurebatch.config
index 5c77e0a9..f6337417 100644
--- a/conf/azurebatch.config
+++ b/conf/azurebatch.config
@@ -14,7 +14,7 @@ params {
     batch_name                 = null
     batch_key                  = null
 
-    vm_type                    = "Standard_D8s_v3"
+    vm_type                    = "Standard_E*d_v5"
     autopoolmode               = true
     allowpoolcreation          = true
     deletejobs                 = true
@@ -33,7 +33,8 @@ process {
 
 azure {
     process {
-        queue = params.az_worker_pool
+        queue       = params.az_worker_pool
+        machineType = params.vm_type
     }
     storage {
         accountName = params.storage_name
@@ -51,7 +52,6 @@ azure {
         deletePoolsOnCompletion = params.deletepools
         pools {
             auto {
-                vmType     = params.vm_type
                 autoScale  = true
                 vmCount    = 1
                 maxVmCount = 12