AWX question from a beginner :-(

Archives Ansible Project
1

I have an Ansible environment already configured (control server and managed servers) and I want to manage it with AWX.
I have installed AWX and start a GUI but I don’t know in what way I can connect AWX to my configuration manually done.

2

AWX/Ansible Tower is designed to work with a Git repo or other Source Control holding each “project” via URI. In general this is also the simplest way to handle things. There is an option to use “manual” loaded projects but requires hand loading the playbooks into the tower container. To do this you have to manually copy the playbooks to the AWX container something like this:

  • Create a directory in /var/lib/awx/projects directory on the local ansible AWX container. Example, /var/lib/awx/projects/project1
  • Place the playbook in ‘project1’ directory. Example, var/lib/awx/projects/project1/example_playbook.yml (follow process as described here)
  • Create a manual project in Tower (follow process as described here)
  • Use that project in job template to see the playbook ‘example_playbook.yml’
3

Thanks Evan for the answer, but I have already configured my Ansible environment manually under /etc/ansible outside container.
Now, after one year I decided to install AWX and I tought was possible to manage my configuration with AWX.

What you sugget is replicate manually on AWX the same things I already done on the server :frowning:

Regards
Ciao

4

Correct. AWX was not intended managing a seperate environment. Honestly, unless you need schedules and callbacks, or shared operation management like in enterprise it is not very useful.

5

AWX and Ansible Tower are really useful when the person or team doing
structure and demanding policy compliance need to hand off specific,
well defined tasks to "Jo-Jo the Monkey Boy", the untrained intern
who's not yet and may never learn how things really work. Red Hat is
now pushing "Event Driven Ansible", integrating ansible through
Ansible Tower with status reporting and recovery operations, and for
such large scale work, it can be *really useful* to say "this team can
do these steps, these people can edit the tasks, these people can
reset privileges for other people, etc."

For a small, consistent environment? As you've found, ansible-core by
itself is enough.

Nico Kadel-Garcia