From Playbook to Production: Projects, Templates, Jobs, and Workflows in Practice

We've been practicing different features and objects in AWX, but it's time to put it all together and run some real jobs.

Previously, we've seen how to configure Instances and Instance Groups, including the two default groups: default and controlplane.

Since we're going to run user jobs, I recommend following these instructions:

• Keep controlplane reserved for AWX's own internal work (project syncs, inventory syncs, scheduler housekeeping) so the AWX pod stays responsive.
• Create a separate instance group called execution and add awx-2 to it.
• Assign that group to your inventories so user playbooks and ad-hoc commands run on the dedicated execution node instead of competing with AWX itself.