Merge pull request #105070 from LauraBrenner/laura-job-scheduling

Laura job scheduling

Author: tiburd

articles/batch/TOC.yml

@@ -123,6 +123,8 @@
       href: batch-user-accounts.md
     - name: Submit a large number of tasks
       href: large-number-tasks.md
+    - name: Schedule jobs for efficiency
+      href: batch-job-schedule.md
     - name: Check for job and task errors
       href: batch-job-task-error-checking.md
     - name: Detecting and handling Batch service errors

articles/batch/batch-automatic-scaling.md

@@ -130,8 +130,8 @@ You can get the value of these service-defined variables to make adjustments tha
 | $SucceededTasks |The number of tasks that finished successfully. |
 | $FailedTasks |The number of tasks that failed. |
 | $CurrentDedicatedNodes |The current number of dedicated compute nodes. |
-| $CurrentLowPriorityNodes |The current number of low-priority compute nodes, including any nodes that have been pre-empted. |
-| $PreemptedNodeCount | The number of nodes in the pool that are in a pre-empted state. |
+| $CurrentLowPriorityNodes |The current number of low-priority compute nodes, including any nodes that have been preempted. |
+| $PreemptedNodeCount | The number of nodes in the pool that are in a preempted state. |
 
 > [!TIP]
 > The read-only, service-defined variables that are shown in the previous table are *objects* that provide various methods to access data associated with each. For more information, see [Obtain sample data](#getsampledata) later in this article.

articles/batch/batch-job-schedule.md

@@ -0,0 +1,88 @@
+---
+title: Schedule your jobs
+description: Use job scheduling to manage your tasks.
+services: batch
+author: LauraBrenner
+manager: evansma
+editor: ''
+
+ms.assetid: 63d9d4f1-8521-4bbb-b95a-c4cad73692d3
+ms.service: batch
+ms.topic: article
+ms.workload: big-compute
+ms.date: 02/20/2020
+ms.author: labrenne
+ms.custom: seodec18
+
+---
+
+# Schedule jobs for efficiency
+
+Scheduling Batch jobs enables you to prioritize the jobs you want to run first while taking into account tasks that have dependencies on other tasks. By scheduling your jobs, you can make sure you use the least amount of resources. Nodes can be decommissioned when not needed, tasks that are dependent on other tasks are spun up just in time optimizing the workflows. Only one job at a time runs. A new one won't start until the previous one completes. You can set your job to autocomplete. 
+
+## Benefit of job scheduling
+
+The benefit of scheduling jobs is that you can specify a schedule for job creation.The tasks you schedule using job manager task are associated with a job. The job manager task will create tasks for the job. To do so, the job manager task needs to authenticate with the Batch account. Use the the AZ_BATCH_AUTHENTICATION_TOKEN access token. The token will allow access to the rest of the job. 
+
+## Use the portal to schedule a job
+
+   1. Sign in to [Azure portal](https://portal.azure.com/).
+
+   2. Select the Batch account you want to schedule jobs in.
+
+   3. Select **Add** to create a new job schedule and complete the **Basic form**.
+
+
+
+![Schedule a job][1]
+
+**Job schedule ID**: The unique identifier for this job schedule.
+
+**Display name**: The display name for the job doesn't have to be unique but has a maximum length of 1024 characters.
+
+**Do not run until**: Specifies the earliest time the job will run. If you don't set this, the schedule becomes ready to run jobs immediately.
+
+**Do not run after**: No jobs run after the time you set here. If you don't specify a time, then you are creating a recurring job schedule which remains active until you explicitly terminate it.
+
+**Recurrence interval**: You can specify the amount of time between jobs. You can have only one job at a time scheduled, so if it is time to create a new job under a job schedule, but the previous job is still running, the Batch service will not create the new job until the previous job finishes.  
+
+**Start window**: Here you specify the time interval, starting from the time the schedule indicates a job should be created, until it should be completed. If the current job doesn't complete during its window, the next job won't start.
+
+At the bottom of the basic form, you will specify the pool on which you want the job to run. To find your pool ID information, select **Update**. 
+
+![Specify pool][2]
+
+
+**Pool ID**: Identify the pool you will run the job on.
+
+**Job configuration task**: Select **Update** to name the Job Manager task as well as the Job preparation and release tasks, if you are using them.
+
+**Priority**: Give the job a priority.
+
+**Max wall clock time**: Set the maximum amount of time the job can run for. If it doesn't complete within the time frame, Batch terminates the job. If you don't set this, then there is no time limit for the job.
+
+**Max task retry count**: Specify the number of times a task can be retried up to a maximum of four times. This is not the same as the number of retries an API call might have.
+
+**When all tasks complete**: The default is no action.
+
+**When a task fails**: The default is no action. A task fails if the retry count is exhausted or there was an error when starting the task. 
+
+After you select **Save**, if you go to **Job schedules** in the left navigation, you can track the execution of the job, by selecting **Execution info**.
+
+
+## For more information
+
+To manage a job using the Azure CLI, see [az batch job-schedule](https://docs.microsoft.com/cli/azure/batch/job-schedule?view=azure-cli-latest).
+
+## Next steps
+
+[Create task dependencies to run tasks that depend on other tasks](batch-task-dependencies.md).
+
+
+
+
+
+[1]: ./media/batch-job-schedule/add_job_schedule-02.png
+[2]: ./media/batch-job-schedule/add_job_schedule-03.png
+
+