-
Book Overview & Buying
-
Table Of Contents
-
Feedback & Rating

Puppet 8 for DevOps Engineers
By :

Heritage can be more daunting for implementation; the extent of configuration drift can make it hard to know where to start. Your organization could have been part of several mergers and acquisitions, which have led to not only multiple configuration standards for the core organization itself but also for anything that has been onboarded.
A common pattern of adoption is to progressively build up the automation levels in heritage servers to build confidence, and we will step through a common approach to this.
Installing an agent on all nodes to gather facts is a common starting point, and having this data stored in PuppetDB to create a valuable CMDB source. Then, as was discussed in Chapter 13, this data can be sent to services such as ServiceNow to integrate with central CMDB services. In Puppet Enterprise, this gives us access to the package view and the ability to manage patching, as was demonstrated in Chapter 14. This rollout gives...