Asynchronous batch commits

Batch commit behavior is enhanced to allow asynchronous commits, scheduling of commit jobs, and fair scheduling among jobs with different priorities. By default, batch commit behavior is synchronous, meaning that the CLI waits until the commit completes before displaying the command prompt. By default, high-priority commit jobs are always processed before low-priority jobs, blocking the completion of low-priority jobs. This default behavior is not suitable for situations where there is a hard requirement to commit certain configurations in a predefined time period or to see the command-prompt within a predefined time limit, especially in a scaled environment. Now you can configure asynchronous batch commits, which allow the CLI to display the command prompt immediately following the commit request when the job is added to the commit queue. Two new CLI commands are introduced to commit the jobs asynchronously: commit asynchronous commits the low-priority jobs asynchronously, and commit priority asynchronous commits the high-priority jobs asynchronously. A new CLI configuration statement commit async/asynchronous is introduced that returns a job-id which can be used for status on these jobs. The CLI returns a job-id that you can use to monitor status with the show commit server queue id commit-id command. Use the commit async statement from batch configuration mode [edit batch] to batch an asynchronous job in the commit queue as a low-priority commit job. You can specify a high-priority asynchronous commit job with the commit priority async statement. The commit operation proceeds in the background, depending on priority and scheduling, and the CLI is available for further inputs. There is a schedule attached to low-priority asynchronous commits. The schedule specifies the time duration and maximum load under which the commit server should process the low-priority jobs. If there is no schedule specified, no schedule is used, and the commit will proceed as a normal batch commit. You can use the new commit-schedule-profile profile-name statement at the [edit system commit server] hierarchy level to define one or more sets of scheduling parameters that can be attached to low-priority commit jobs.