A complete server/agent architecture with multiple compilers and load balancing for redundancy.
Intended Audience
This architecture is intended for large infrastructures or dynamic infrastructures that require the redundancy of multiple compilers.
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 webhook-go to receive webhook events from your code repository and automate your code deploys. This service should be installed on the main OpenVox Server. You might consider using the Bolt task from the puppet-r10k module to trigger code deployments on each compiler, or you can also install webhook-go on each (puppet-r10k can configure it).
Code Deployment
r10k is considered the default Puppet code deployment tool. Install it on the main OpenVox Server and each compiler 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.
Load Balancer
OpenVox Agent Server connections are connections with long duration. Therfore it is highly recommended to use least_connection algorithm.
Any kind of load-balancer is sufficient. HAProxy is well supported and allows flexibility.
OpenVox Stack
We recommend managing each of these components with the supported module.
- OpenVoxDB
- puppetlabs/puppetdb
- The default PostgreSQL database is recommended.
- OpenVox Servers and agents
- Puppet Metrics Dashboard
- Hiera Data Manager (HDM)
- HAproxy LoadBalancer