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
Extending Puppet

You're reading from   Extending Puppet Design, manage, and deploy your Puppet architecture with the help of real-world scenarios.

Arrow left icon
Product type Paperback
Published in Jun 2014
Publisher
ISBN-13 9781783981441
Length 328 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Alessandro Franceschi Alessandro Franceschi
Author Profile Icon Alessandro Franceschi
Alessandro Franceschi
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Puppet Essentials FREE CHAPTER 2. Hiera 3. PuppetDB 4. Designing Puppet Architectures 5. Using and Writing Reusable Modules 6. Higher Abstraction Modules 7. Deploying and Migrating Puppet 8. Code Workflow Management 9. Scaling Puppet Infrastructures 10. Writing Puppet Plugins 11. Beyond the System 12. Future Puppet Index

Things change


Once we introduce a tool like Puppet in our infrastructure, everything changes and we should be well aware of this.

Infrastructure as code

There's a wonderful term that describes what tools like Puppet or Chef have introduced in IT operations: infrastructure as code. We define our IT infrastructure with formal code, the configurations of our servers, the procedures to set them up, and whatever is needed to turn a piece of bare metal or a blank VM to a system that provides services for our purposes.

When we can use a programming language to configure our systems, a lot of powerful collateral effects take place. These are inherently related to the fact that we are dealing with code.

Versioning

Code can be versioned with an SCM. The history of our commits reflects the history of our infrastructure. We can know who did a change and when and why they did it. There's a huge intrinsic value in this: the power of contextual documentation and communication. Puppet code is inherently the...

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