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

Summary

In this chapter, we have seen how Puppet can scale while our infrastructure grows. We have to consider all the components involved.

For test or small environments, we may have an all-in-one server, but it makes sense to separate these components from the beginning on dedicated nodes:

  • A Puppet Master under Passenger
  • PuppetDB and its backend database (we might decide to move the PostgreSQL service to a dedicated server too)
  • Eventually an ENC such as Foreman and its backend database (which might be moved to a dedicated node too)

When we need to scale further, or want high availability on these components, we can start to scale out horizontally and load balance the Puppet Master, Foreman, and PuppetDB systems (they all provide stateless HTTP(s) ...

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