Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Puppet 8 for DevOps Engineers

You're reading from  Puppet 8 for DevOps Engineers

Product type Book
Published in Jun 2023
Publisher Packt
ISBN-13 9781803231709
Pages 416 pages
Edition 1st Edition
Languages
Concepts
Author (1):
David Sandilands David Sandilands
Profile icon David Sandilands

Table of Contents (22) Chapters

Preface 1. Part 1 – Introduction to Puppet and the Basics of the Puppet Language
2. Chapter 1: Puppet Concepts and Practices 3. Chapter 2: Major Changes, Useful Tools, and References 4. Chapter 3: Puppet Classes, Resource Types, and Providers 5. Chapter 4: Variables and Data Types 6. Chapter 5: Facts and Functions 7. Part 2 – Structuring, Ordering, and Managing Data in the Puppet Language
8. Chapter 6: Relationships, Ordering, and Scope 9. Chapter 7: Templating, Iterating, and Conditionals 10. Chapter 8: Developing and Managing Modules 11. Chapter 9: Handling Data with Puppet 12. Part 3 – The Puppet Platform and Bolt Orchestration
13. Chapter 10: Puppet Platform Parts and Functions 14. Chapter 11: Classification and Release Management 15. Chapter 12: Bolt for Orchestration 16. Chapter 13: Taking Puppet Server Further 17. Part 4 – Puppet Enterprise and Approaches to the Adoption of Puppet
18. Chapter 14: A Brief Overview of Puppet Enterprise 19. Chapter 15: Approaches to Adoption 20. Index 21. Other Books You May Enjoy

Roles and profiles method

In the previous section, the modules we discussed are what are known as component modules since they cover single implementations. These modules are mostly of interest to users directly involved with the technology implementation, such as Unix or Windows administrators, where understanding that specific resources have been applied is the most important aspect of the configuration. But different users are not interested in how a node is configured; instead, they are interested in what it does. An application specialist, for example, would care that, for their application, Tomcat and MySQL were installed, not how it was configured. A project manager would care that they got a server that met a business need but not what technical stacks were used. The project manager may also see each implementation as unique, but there will often be a lot of similarities, such as various technology stacks being used across multiple applications using Apache or Java with variations...

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 $15.99/month. Cancel anytime}