recordsansible/ara
Code Issues Proposed changes
ara/doc/source/architecture.rst
David Moreau Simard 41a2e339fc
Update the recording workflow diagram to be more accurate 
Attempting to picture the client as an individual aspect of the workflow
diagram made the workflow seem much worse than it actually was.

The callback uses the client to send the data to the API. Document it as
such.

Change-Id: I12795820c269d2aa9a8032c703285b86624ca7fe
2019-04-03 22:04:30 -04:00

989 B
Raw Blame History

Architecture and Workflows

Recording data from Ansible

ARA Records Ansible playbooks through an Ansible callback plugin.

image

  1. ARA is installed and Ansible is configured to use the callback plugin
  2. An ansible-playbook command is executed
  3. Ansible triggers the callback plugin for every event (v2_playbook_on_start, v2_runner_on_failed, etc.)
  4. The relevant information is retrieved from the Ansible playbook execution context and is sent to the API server
  5. The API server validates and serializes the data before storing it the configured database backend
  6. The API server sends a response back to the API client with the results
  7. The callback plugin returns, ending the callback hook
  8. Ansible continues running the playbook until it fails or is completed (back to step 2)