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) ...
Get Extending Puppet now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
