If you’ve used Puppet Enterprise (PE) for a long time, you know that our terminology has changed over the years. Here’s a list to help you make sense of those changes. You might still see old terminology used in the UI or in code of some products because it takes a long time to change every instance of these terms in code.
Version and installation information
PE version: All
List of old and current Puppet Enterprise terms
|Old term||Current term||Changed in version||Additional info|
|compile master||compiler||PE 2019.1||n/a|
|high availability (PE)||disaster recovery||PE 2018.7||Other products have high availability as a feature, this is PE-specific.|
|master of masters||primary server||PE 2019.8.2||In 2019.1 master of masters changed to master|
|master||primary server||PE 2019.8.2||n/a|
|master (branch)||main (branch)||fall 2020||n/a|
|monolithic||standard, large, or extra large||PE 2019.2||See the following table for architecture terminology changes.|
Architecture terminology changes
In PE 2019.2, we updated the terms we use to talk about PE reference architecture types and stopped using the term monolithic.
|Old term||Current term||Configuration||Nodes|
|Monolithic||Standard||All infrastructure components are installed on the primary server.||Up to 4,000|
|Monolithic with compilers||Large||All infrastructure components are installed on the primary server, plus one or more compilers and a load balancer.||4,000 to 20,000|
|Monolithic with compilers and standalone PE-PostgreSQL||Extra large||All infrastructure components are installed on the primary server, plus one or more compilers and a load balancer, plus separate PE-PostgreSQL node(s) which run PuppetDB.||More than 20,000|
For more information and diagrams, see the Supported architectures PE documentation.
How can we improve this article?
Please sign in to leave a comment.