ansible / awx

AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
Other
13.67k stars 3.37k forks source link

Feature: Ability to import disconnected job results into Tower automatically or via an API #4028

Open tra7nce opened 5 years ago

tra7nce commented 5 years ago
ISSUE TYPE
SUMMARY

Background:

With an operations manager machine on network 1. That system is a single pane of glass management system for all other networks and machines (BM, VM, etc.). We would like to log into Tower and execute or schedule a job to run against an inventory. So far, nothing special.

However, network 2, network 3, network n, etc., are all on the other side of one or more one-way guard devices or in field locations with inconsistent connectivity or both. We need the ability to run scheduled jobs, on demand jobs and/or issue ad-hoc CLI playbooks against those systems from the Ops Mgr Tower.

Now we know that we could have Tower create a CSV file as part of the job that gets picked up in a watch folder, moved across the guard and to a location that performs the job on whatever machine on whatever network. That's not a concern.

The trick is getting the results of those jobs back into the Ops Mgr Tower on network 1. We can tell the jobs via the playbook to parse the logs or output of the jobs to text files, JSON, whatever. We can get those files back across the one-way guards.

Request:

We need the ability to import disconnected job results into Tower automatically or via an API so that the Ops Mgr Tower can remain the single pane of glass for jobs and results. Even when Tower cannot talk to the target machines directly. We are running additional Tower servers on each network, but want the Ops Mgr Tower to be the broker / primary / source of truth.

wenottingham commented 5 years ago

I think https://github.com/ansible/awx/pull/3422 is what you're looking for.