External-Mirrors/awx
2
0
Fork 0
mirror of https://github.com/ansible/awx.git synced 2026-01-31 17:18:59 -03:30
Code Issues Packages Projects Releases Wiki Activity

Tag jobs started via special cases with node & group

Browse Source
This commit is contained in:
AlanCoding
2017-06-22 14:32:11 -04:00
parent 04ca47ffab
commit 9e07b3f777
5 changed files with 18 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/clustering.md
View File

@@ -115,9 +115,9 @@ rabbitmq_enable_manager=false
### Security Isolated Rampart Groups
In Tower versions 3.2+ customers may optionally define isolated groups
inside security-restricted networking zones to run jobs from.
inside security-restricted networking zones to run jobs and ad hoc commands from.
Instances in these groups will _not_ have a full install of Tower, but will have a minimal
set of utilities used to run jobs on them. These must be specified
set of utilities used to run jobs. Isolated groups must be specified
in the inventory file prefixed with `isolated_group_`. An example inventory
file is shown below.
@@ -150,7 +150,8 @@ the `isolatedA` and `isolatedB` hosts).
When a job is scheduled to run on an "isolated" instance:
* The "controller" instance compiles metadata required to run the job and copies
it to the "isolated" instance via `rsync`. This metadata includes:
it to the "isolated" instance via `rsync` (any related project or inventory
updates are run on the controller instance). This metadata includes:
- the entire SCM checkout directory for the project
- a static inventory file