A simple server/agent architecture with all services running on a single machine.
Intended Audience
This architecture is intended for small to medium static infrastructures and is easier to set up and maintain than a load balanced compiler farm. Generally speaking, redundancy and HA are most useful for dynamic environments. A stopped Puppet server doesn’t prevent the existing configuration from being enforced but it will halt any new deployments or configuration updates. If those constraints fit your needs, then this architecture is suggested.
Setup and Usage
{write a guide on how to deploy, configure, and use this architecture}
Git Repository
We recommend organizing your code as a Control Repository with branches for environments. See the reference repository for an example.
Foreman
Foreman is a complete lifecycle management tool for physical and virtual servers. It will provide you with a graphical classifier, a Hiera data source, and report monitoring. It also includes the power to easily automate repetitive tasks, quickly deploy applications, and proactively manage servers, on-premise or in the cloud.
Puppet Webhook
Configure Puppet Webhook to receive webhook events from your code repository and automate your code deploys.
Code Deployment
r10k is considered the default Puppet code deployment tool. Install it on your server in your infrastructure and use it to deploy your control repository as needed.
If you’re a Golang shop, you might consider g10k as well.
Puppet Stack
We recommend managing each of these components with the supported module.
- PuppetDB
- puppetlabs/puppetdb
- The default PostgreSQL database is recommended.
- Puppet Server
- Puppet Agents
- Puppet Metrics Dashboard
- Hiera Data Manager (HDM)