You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/batch/quick-create-cli.md
+50-84Lines changed: 50 additions & 84 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: 'Quickstart: Use the Azure CLI to create a Batch account and run a job'
3
3
description: Follow this quickstart to use the Azure CLI to create a Batch account, a pool of compute nodes, and a job that runs basic tasks on the pool.
# Quickstart: Use the Azure CLI to create a Batch account and run a job
@@ -20,91 +20,63 @@ After you complete this quickstart, you understand the [key concepts of the Batc
20
20
21
21
You can run the Azure CLI commands in this quickstart interactively in Azure Cloud Shell. To run the commands in the Cloud Shell, select **Open Cloudshell** at the upper-right corner of a code block. Select **Copy** to copy the code, and paste it into Cloud Shell to run it. You can also [run Cloud Shell from within the Azure portal](https://shell.azure.com). Cloud Shell always uses the latest version of the Azure CLI.
22
22
23
-
Alternatively, you can [install Azure CLI locally](/cli/azure/install-azure-cli) to run the commands. The steps in this article require Azure CLI version 2.0.20 or later. Run [az version](/cli/azure/reference-index?#az-version) to see your installed version and dependent libraries, and run [az upgrade](/cli/azure/reference-index?#az-upgrade) to upgrade. If you use a local installation, sign in to Azure by using the appropriate command.
23
+
Alternatively, you can [install Azure CLI locally](/cli/azure/install-azure-cli) to run the commands. The steps in this article require Azure CLI version 2.0.20 or later. Run [az version](/cli/azure/reference-index?#az-version) to see your installed version and dependent libraries, and run [az upgrade](/cli/azure/reference-index?#az-upgrade) to upgrade. If you use a local installation, sign in to Azure by using the [az login](/cli/azure/reference-index#az-login) command.
24
24
25
25
>[!NOTE]
26
26
>For some regions and subscription types, quota restrictions might cause Batch account or node creation to fail or not complete. In this situation, you can request a quota increase at no charge. For more information, see [Batch service quotas and limits](batch-quota-limit.md).
27
27
28
28
## Create a resource group
29
29
30
-
Run the following [az group create](/cli/azure/group#az-group-create) command to create an Azure resource group. The resource group is a logical container that holds the Azure resources for this quickstart.
30
+
Run the following [az group create](/cli/azure/group#az-group-create) command to create an Azure resource group named `qsBatch` in the `eastus2` Azure region. The resource group is a logical container that holds the Azure resources for this quickstart.
Use the [az storage account create](/cli/azure/storage/account#az-storage-account-create) command to create an Azure Storage account to link to your Batch account. Although this quickstart doesn't use the storage account, most real-world Batch workloads use a linked storage account to deploy applications and store input and output data.
63
41
64
-
Run the following command to create a Standard_LRS SKU storage account in your resource group:
42
+
Run the following command to create a Standard_LRS SKU storage account named `mybatchstorage`in your resource group:
Run the following [az batch account create](/cli/azure/batch/account#az-batch-account-create) command to create a Batch account in your resource group and link it with the storage account.
54
+
Run the following [az batch account create](/cli/azure/batch/account#az-batch-account-create) command to create a Batch account named `mybatchaccount`in your resource group and link it with the`mybatchstorage` storage account.
Sign in to the new Batch account by running the [az batch account login](/cli/azure/batch/account#az-batch-account-login) command. Once you authenticate your account with Batch, subsequent `az batch` commands in this session use this account context.
91
65
92
66
```azurecli-interactive
93
67
az batch account login \
94
-
--name $BATCH_ACCOUNT \
95
-
--resource-group $RESOURCE_GROUP \
68
+
--name mybatchaccount \
69
+
--resource-group qsBatch \
96
70
--shared-key-auth
97
71
```
98
72
99
73
## Create a pool of compute nodes
100
74
101
-
Run the [az batch pool create](/cli/azure/batch/pool#az-batch-pool-create) command to create a pool of Linux compute nodes in your Batch account. The following example creates a pool that consists of two Standard_A1_v2 size VMs running Ubuntu 20.04 LTS OS. This node size offers a good balance of performance versus cost for this quickstart example.
75
+
Run the [az batch pool create](/cli/azure/batch/pool#az-batch-pool-create) command to create a pool of Linux compute nodes in your Batch account. The following example creates a pool named `myPool`that consists of two Standard_A1_v2 size VMs running Ubuntu 20.04 LTS OS. This node size offers a good balance of performance versus cost for this quickstart example.
Batch creates the pool immediately, but takes a few minutes to allocate and start the compute nodes. To see the pool status, use the [az batch pool show](/cli/azure/batch/pool#az-batch-pool-show) command. This command shows all the properties of the pool, and you can query for specific properties. The following command queries for the pool allocation state:
115
87
116
88
```azurecli-interactive
117
-
az batch pool show --pool-id $POOL_ID \
118
-
--query "{allocationState: allocationState}"
119
-
```
120
-
121
-
Results:
122
-
123
-
<!-- expected_similarity=0.3 -->
124
-
125
-
```JSON
126
-
{
127
-
"allocationState": "resizing"
128
-
}
89
+
az batch pool show --pool-id myPool \
90
+
--query "allocationState"
129
91
```
130
92
131
93
While Batch allocates and starts the nodes, the pool is in the `resizing` state. You can create a job and tasks while the pool state is still `resizing`. The pool is ready to run tasks when the allocation state is `steady` and all the nodes are running.
132
94
133
95
## Create a job
134
96
135
-
Use the [az batch job create](/cli/azure/batch/job#az-batch-job-create) command to create a Batch job to run on your pool. A Batch job is a logical group of one or more tasks. The job includes settings common to the tasks, such as the pool to run on. The following example creates a job that initially has no tasks.
97
+
Use the [az batch job create](/cli/azure/batch/job#az-batch-job-create) command to create a Batch job to run on your pool. A Batch job is a logical group of one or more tasks. The job includes settings common to the tasks, such as the pool to run on. The following example creates a job called `myJob` on `myPool`that initially has no tasks.
The command output shows the settings for each task. Batch distributes the tasks to the compute nodes.
162
122
163
123
## View task status
164
124
165
-
After you create the tasks, Batch queues them to run on the pool. Once a node is available, a task runs on the node.
125
+
After you create the task, Batch queues the task to run on the pool. Once a node is available, the task runs on the node.
166
126
167
127
Use the [az batch task show](/cli/azure/batch/task#az-batch-task-show) command to view the status of Batch tasks. The following example shows details about the status of `myTask1`:
168
128
169
129
```azurecli-interactive
170
130
az batch task show \
171
-
--job-id $JOB_ID \
131
+
--job-id myJob \
172
132
--task-id myTask1
173
133
```
174
134
@@ -179,39 +139,29 @@ The command output includes many details. For example, an `exitCode` of `0` indi
179
139
Use the [az batch task file list](/cli/azure/batch/task#az-batch-task-file-show) command to list the files a task created on a node. The following command lists the files that `myTask1` created:
180
140
181
141
```azurecli-interactive
182
-
# Wait for task to complete before downloading output
The [az batch task file download](/cli/azure/batch/task#az-batch-task-file-download) command downloads output files to a local directory. Run the following example to download the *stdout.txt* file:
If you want to continue with Batch tutorials and samples, you can use the Batch account and linked storage account that you created in this quickstart. There's no charge for the Batch account itself.
193
+
194
+
Pools and nodes incur charges while the nodes are running, even if they aren't running jobs. When you no longer need a pool, use the [az batch pool delete](/cli/azure/batch/pool#az-batch-pool-delete) command to delete it. Deleting a pool deletes all task output on the nodes, and the nodes themselves.
195
+
196
+
```azurecli-interactive
197
+
az batch pool delete --pool-id myPool
198
+
```
199
+
200
+
When you no longer need any of the resources you created for this quickstart, you can use the [az group delete](/cli/azure/group#az-group-delete) command to delete the resource group and all its resources. To delete the resource group and the storage account, Batch account, node pools, and all related resources, run the following command:
201
+
202
+
```azurecli-interactive
203
+
az group delete --name qsBatch
204
+
```
205
+
240
206
## Next steps
241
207
242
208
In this quickstart, you created a Batch account and pool, created and ran a Batch job and tasks, and viewed task output from the nodes. Now that you understand the key concepts of the Batch service, you're ready to use Batch with more realistic, larger scale workloads. To learn more about Azure Batch, continue to the Azure Batch tutorials.
243
209
244
210
> [!div class="nextstepaction"]
245
-
> [Tutorial: Run a parallel workload with Azure Batch](./tutorial-parallel-python.md)
211
+
> [Tutorial: Run a parallel workload with Azure Batch](./tutorial-parallel-python.md)
0 commit comments