Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learning Ansible 2.7

You're reading from   Learning Ansible 2.7 Automate your organization's infrastructure using Ansible 2.7

Arrow left icon
Product type Paperback
Published in Apr 2019
Publisher Packt
ISBN-13 9781789954333
Length 266 pages
Edition 3rd Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Fabio Alessandro Locati Fabio Alessandro Locati
Author Profile Icon Fabio Alessandro Locati
Fabio Alessandro Locati
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Section 1: Creating a Web Server Using Ansible FREE CHAPTER
2. Getting Started with Ansible 3. Automating Simple Tasks 4. Section 2: Deploying Playbooks in a Production Environment
5. Scaling to Multiple Hosts 6. Handling Complex Deployment 7. Going Cloud 8. Getting Notification from Ansible 9. Section 3: Deploying an Application with Ansible
10. Creating a Custom Module 11. Debugging and Error Handling 12. Complex Environments 13. Section 4: Deploying an Application with Ansible
14. Introducing Ansible for Enterprises 15. Getting Started with AWX 16. Working with AWX Users, Permissions, and Organizations 17. Other Books You May Enjoy

Using AWX jobs

AWX jobs are executions of AWX jobs templates, in the same way as Ansible runs are executions of Ansible playbooks.

When you launch a job, you'll see a window just like the following one:

This is the AWX version of the output of Ansible, when run on the command line.

After a few seconds, in the right-hand grey box a very familiar output will start to pop out, since it's exactly the same stdout of Ansible, just redirected there.

If later you click on Jobs on the left menu bar, you will find yourself on a different screen, listing all previously run jobs:

As you can notice, we have two jobs that have been executed, while we've only executed the Demo Job Template. This is because the Demo Project has been pulled before and due to the Demo Job Template execution. This allows the operator to be always comfortable to run a job, knowing that it will always...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image