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
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,9 +20,7 @@ This quickstart uses Azure CLI commands and scripts to create and manage Batch r
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
-
You can also [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.
24
-
25
-
If you use a local installation, sign in to Azure by using the [az login](/cli/azure/reference-index#az-login) command.
23
+
You can also [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.
26
24
27
25
## Create a resource group
28
26
@@ -60,7 +58,7 @@ az batch account create \
60
58
--location eastus2
61
59
```
62
60
63
-
Sign in to the new Batch account by running the [az batch account login](/cli/azure/batch/account#az-batch-account-login) command. After you authenticate with Batch, the rest of the `az batch` quickstart commands use this account context.
61
+
Sign in to the new Batch account by running the [az batch account login](/cli/azure/batch/account#az-batch-account-login) command. After you authenticate your account with Batch, the rest of the `az batch` quickstart commands use this account context.
Copy file name to clipboardExpand all lines: articles/batch/quick-create-portal.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,7 +62,7 @@ Next, create a pool of Windows compute nodes in your Batch account. The followin
62
62
63
63
1. Accept the defaults for the remaining settings, and select **OK** at the bottom of the page.
64
64
65
-
Batch creates the pool immediately, but takes a few minutes to allocate and start the compute nodes. On the **Pools** page, select **myPool** to go to the **myPool** page and see the pool status of **Resizing** under **Essentials** > **Allocation state**. You can do the following steps to create a job and tasks while the pool state is still resizing.
65
+
Batch creates the pool immediately, but takes a few minutes to allocate and start the compute nodes. On the **Pools** page, select **myPool** to go to the **myPool** page and see the pool status of **Resizing** under **Essentials** > **Allocation state**. You can follow the next steps to create a job and tasks while the pool state is still resizing.
66
66
67
67
After a few minutes, the **Allocation state** changes to **Steady**, and the nodes start. To check the state of the nodes, select **Nodes** in the **myPool** page left navigation. When a node's state is **Idle**, it's ready to run tasks.
68
68
@@ -82,7 +82,7 @@ Now create a job to run on the pool. A Batch job is a logical group of one or mo
82
82
83
83
## Create tasks
84
84
85
-
Jobs can contain multiple tasks that Batch queues and distributes to run on the compute nodes. When you create a task, you specify your app or script in a command line. Batch provides several ways to deploy apps and scripts to compute nodes.
85
+
Jobs can contain multiple tasks that Batch queues and distributes to run on the compute nodes. Batch provides several ways to deploy apps and scripts to compute nodes. When you create a task, you specify your app or script in a command line.
86
86
87
87
The following procedure creates and runs two identical tasks in your job. Each task runs a command line that displays the Batch environment variables on the compute node, and then waits 90 seconds.
88
88
@@ -126,7 +126,9 @@ When you no longer need any of the resources you created for this quickstart, yo
126
126
127
127
## Next steps
128
128
129
-
In this quickstart, you created a Batch account and pool, and created and ran a Batch job and tasks. You monitored node and task status, 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.
129
+
In this quickstart, you created a Batch account and pool, and created and ran a Batch job and tasks. You monitored node and task status, and viewed task output from the nodes.
130
+
131
+
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.
Typicalruntimeusingthedefaultconfigurationisapproximatelyfiveminutes. Initialpoolnodesetuptakesthemosttime. Torerunthejob, deletethejobfromthepreviousrun, butdon't delete the pool. On a preconfigured pool, the job completes in a few seconds.
84
+
Typicalruntimewiththedefaultconfigurationisapproximatelyfiveminutes. Initialpoolnodesetuptakesthemosttime. Torerunthejob, deletethejobfromthepreviousrun, butdon't delete the pool. On a preconfigured pool, the job completes in a few seconds.
0 commit comments