O'Reilly logo

Extending Puppet by Alessandro Franceschi

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Propagating Puppet changes

Deployment of the Puppet code on production is a matter of updating the files on the directories served by Puppet Master (or, in a Masterless setup, distributing these files on each node), but contrary to other typical application deployments, the process doesn't end here: we need to run Puppet on our nodes in order to apply the changes.

How this is done largely depends on the policy we follow to manage Puppet execution. We can manage Puppet runs in different ways, and this affects how our changes can be propagated:

  • Running Puppet as a service: In this case, any change on the Puppet production environment (or what is configured as default) is propagated to the whole infrastructure in the runinterval timeframe.
  • Running Puppet ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required