You're reading from Puppet 8 for DevOps Engineers Automate your infrastructure at an enterprise scale

Product type Paperback

Published in Jun 2023

Publisher Packt

ISBN-13 9781803231709

Length 416 pages

Edition 1st Edition

Tools

Puppet

Concepts

DevOps

Author (1):

David Sandilands

View More author details

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 FREE CHAPTER

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

Why subscribe?

21. Other Books You May Enjoy

Moving to the cloud

The move to the public cloud has huge opportunities, particularly in terms of flexibility, with opportunities to use cloud-specific technologies to reduce the operational burden on your organization. For example, the ease of using availability zones for compilers to reduce the risk of data center failures is a complex feature to implement in private data centers.

Unfortunately, there are two commonly seen anti-patterns for the cloud adoption approach. The first is a wholesale copy of all infrastructure, processes, and components as they work in the private data centers to the public cloud. This often happens with “cloud-first” programs, which tend to be a result of Chief Information Officers’ (CIOs) disappointment in the take up of public cloud resources. This forces deployments into the public cloud before organizations are ready and understand what is a suitable fit. This results in surprise bills as the infrastructure deployed is not planned...