Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Practical Ansible 2

You're reading from   Practical Ansible 2 Automate infrastructure, manage configuration, and deploy applications with Ansible 2.9

Arrow left icon
Product type Paperback
Published in Jun 2020
Publisher Packt
ISBN-13 9781789807462
Length 410 pages
Edition 1st Edition
Tools
Arrow right icon
Authors (4):
Arrow left icon
Fabio Alessandro Locati Fabio Alessandro Locati
Author Profile Icon Fabio Alessandro Locati
Fabio Alessandro Locati
James Freeman James Freeman
Author Profile Icon James Freeman
James Freeman
Daniel Oh Daniel Oh
Author Profile Icon Daniel Oh
Daniel Oh
Oh Se Young Oh Se Young
Author Profile Icon Oh Se Young
Oh Se Young
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Section 1: Learning the Fundamentals of Ansible
2. Getting Started with Ansible FREE CHAPTER 3. Understanding the Fundamentals of Ansible 4. Defining Your Inventory 5. Playbooks and Roles 6. Section 2: Expanding the Capabilities of Ansible
7. Consuming and Creating Modules 8. Consuming and Creating Plugins 9. Coding Best Practices 10. Advanced Ansible Topics 11. Section 3: Using Ansible in an Enterprise
12. Network Automation with Ansible 13. Container and Cloud Management 14. Troubleshooting and Testing Strategies 15. Getting Started with Ansible Tower 16. Assessments 17. Other Books You May Enjoy

Using the run_once option

When working with clusters, you will sometimes encounter a task that should only be executed once for the entire cluster. For example, you might want to upgrade the schema of a clustered database or issue a command to reconfigure a Pacemaker cluster that would normally be issued on one node and replicated to all other nodes by Pacemaker. You could, of course, address this with a special inventory with only one host in it, or even by writing a special play that references one host from the inventory, but this is inefficient and starts to make your code fragmented.

Instead, you can write your code as you normally would, but make use of the special run_once directive for any tasks you want to run only once on your inventory. For example, let's reuse the 10-host inventory that we defined earlier in this chapter. Now, let's proceed to demonstrate...

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 €18.99/month. Cancel anytime