External-Mirrors/awx
2
0
Fork 0
mirror of https://github.com/ansible/awx.git synced 2026-01-19 13:41:28 -03:30
Code Issues Packages Projects Releases Wiki Activity

Add alt text for image directives in job_capacity.rst & job_slices.rst (#14549)

Browse Source 
Co-authored-by: Kishan Mehta <kishan@scrapinghub.com>
Co-authored-by: TVo <thavo@redhat.com>
This commit is contained in:
Kishan Mehta 2023-10-20 19:04:04 +05:30 committed by GitHub
parent bcefcd8cf8
commit c4ab54d7f3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/docsite/rst/userguide/job_capacity.rst
View File

@ -106,4 +106,5 @@ The instance field ``capacity_adjustment`` allows you to select how much of one
To view or edit the capacity in the user interface, select the **Instances** tab of the Instance Group.
.. image:: ../common/images/instance-group-instances-capacity-callouts.png
.. image:: ../common/images/instance-group-instances-capacity-callouts.png
:alt: Instances tab of Instance Group showing sliders for capacity adjustment.

2
docs/docsite/rst/userguide/job_slices.rst
View File

@ -28,6 +28,7 @@ Consider the following when setting up job slices:
- When executed, a sliced job splits each inventory into a number of "slice size" chunks. It then queues jobs of ansible-playbook runs on each chunk of the appropriate inventory. The inventory fed into ansible-playbook is a pared-down version of the original inventory that only contains the hosts in that particular slice. The completed sliced job that displays on the Jobs list are labeled accordingly, with the number of sliced jobs that have run:
.. image:: ../common/images/sliced-job-shown-jobs-list-view.png
:alt: Sliced job shown in Jobs list view
- These sliced jobs follow normal scheduling behavior (number of forks, queuing due to capacity, assignation to instance groups based on inventory mapping).
@ -54,6 +55,7 @@ Job slice execution behavior
When jobs are sliced, they can run on any node and some may not run at the same time (insufficient capacity in the system, for example). When slice jobs are running, job details display the workflow and job slice(s) currently running, as well as a link to view their details individually.
.. image:: ../common/images/sliced-job-shown-jobs-output-view.png
:alt: Sliced job shown in Jobs output view
By default, job templates are not normally configured to execute simultaneously (``allow_simultaneous`` must be checked in the API or **Enable Concurrent Jobs** in the UI). Slicing overrides this behavior and implies ``allow_simultaneous`` even if that setting is unchecked. See :ref:`ug_JobTemplates` for information on how to specify this, as well as the number of job slices on your job template configuration.