Forge Home


Puppet module for Frontier configuration


7,603 latest version

2.1 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.1.3 (latest)
  • 0.1.2
  • 0.1.1
  • 0.1.0
released Feb 23rd 2017

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'desalvo-frontier', '0.1.3'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add desalvo-frontier
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install desalvo-frontier --version 0.1.3

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



desalvo/frontier — version 0.1.3 Feb 23rd 2017


Puppet module for managing Frontier configurations.

Table of Contents

  1. Overview - What is the frontier module?


This module is intended to be used to install and configure Frontier services. The Frontier distributed database caching system distributes data from data sources to many clients around the world. The name comes from "N Tier" where N is any number and Tiers are layers of locations of distribution. The protocol is http-based and uses a RESTful architecture which is excellent for caching and scales well. The Frontier system uses the standard web caching tool squid to cache the http objects at every site. It is ideal for applications where there are large numbers of widely distributed clients that read basically the same data at close to the same time, in much the same way that popular websites are read by many clients.


The following parameters are supported:

  • customize_file: the customization configuration file to be used, not used if unset
  • customize_template: the customization configuration template to be used, not used if unset
  • cache_dir: the cache directory to use
  • max_access_log: The max size of the log before rotating them
  • install_resource: set this to true if you want to instal the pacemaker FrontierSquid resource
  • resource_path: the path where to install the pacemaker resource, default "/usr/lib/ocf/resource.d/lcg"
  • $customize_params : hash that can be used to provide the customize_lines param with ... params.
  • $customize_lines : array, containing lines that will be interpreted as inline templates and will be used to fill the default Usage


This is a simple example to configure a frontier squid.

Using the frontier squid module

class { 'frontier::squid':
    customize_file => 'puppet:///modules/mymodule/',
    cache_dir      => 'var/squid/cache'


Release Notes


  • Update the frontier repo RPM version
  • Squid 3.5 support
  • Puppet 4 support


  • Add the max_access_log parameter


  • Change the default of cache_dir to /var/squid/cache.


  • Initial version.