Book Image

Mastering Puppet 5

By : Ryan Russell-Yates, Jason Southgate
Book Image

Mastering Puppet 5

By: Ryan Russell-Yates, Jason Southgate

Overview of this book

Puppet is a configuration management system and a language written for and by system administrators to manage a large number of systems efficiently and prevent configuration drift. The core topics this book addresses are Puppet's latest features and mastering Puppet Enterprise. You will begin by writing a new Puppet module, gaining an understanding of the guidelines and style of the Puppet community. Following on from this, you will take advantage of the roles and profiles pattern, and you will learn how to structure your code. Next, you will learn how to extend Puppet and write custom facts, functions, types, and providers in Ruby, and also use the new features of Hiera 5. You will also learn how to configure the new Code Manager component, and how to ensure code is automatically deployed to (multiple) Puppet servers. Next, you will learn how to integrate Puppet with Jenkins and Git to build an effective workflow for multiple teams, and use the new Puppet Tasks feature and the latest Puppet Orchestrator language extensions. Finally, you will learn how to scale and troubleshoot Puppet. By the end of the book, you will be able to deal with problems of scale and exceptions in your code, automate workflows, and support multiple developers working simultaneously.
Table of Contents (19 chapters)
Title Page
Dedication
Packt Upsell
Contributors
Preface
Index

Chapter 7. Continuous Integration

Continuous Integration as a practice is ensuring that each time code is committed, it is built and tested the same way consistently. We use Continuous Integration systems to automate this practice, making it practical for use on every commit. Some Continuous Integration pipelines eventually evolve into Continuous Delivery or Continuous Deployment pipelines. The key difference between Continuous Integration and delivery is that delivery ensures that every time code is committed, it is also wrapped up (or packaged) and delivered to the doorstep of the server it needs to run on. Continuous Delivery requires the ability to deploy your entire infrastructure and application consistently with a single orchestration command. Continuous Deployment requires an end-to-end suite of tests for every component in your infrastructure, but is the simple task of automating that single orchestration command when every test passes.

 

 

 

How these systems become useful to the individual...