Forge Home

varnish

Puppet Varnish module

32,675 downloads

12,859 latest version

3.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

  • 1.99.22 (latest)
  • 1.99.21
  • 1.99.20
  • 1.99.19
  • 1.99.17
  • 1.99.16
  • 1.99.15
  • 1.99.14
  • 1.99.13
  • 1.99.12
  • 1.99.10
  • 1.99.9
  • 1.99.8
  • 1.99.7
  • 1.99.6
  • 1.99.5
  • 1.99.4
  • 1.99.3
  • 1.99.2
  • 1.99.1
  • 1.99.0
  • 1.1.1
  • 1.1.0
  • 1.0.2
  • 1.0.1
  • 1.0.0
  • 0.0.1 (deleted)
released Aug 21st 2015
This version is compatible with:
  • Puppet Enterprise 3.x
  • Puppet 3.x
  • , ,

Start using this module

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

Add this module to your Puppetfile:

mod 'camptocamp-varnish', '1.99.22'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add camptocamp-varnish
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install camptocamp-varnish --version 1.99.22

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.

Download

Documentation

camptocamp/varnish — version 1.99.22 Aug 21st 2015

Varnish

Puppet Forge Version Puppet Forge Downloads Build Status Gemnasium By Camptocamp

Overview

This puppet module installs and configures varnish.

Usage

class { 'varnish':
  multi_instances => false,
}

To manage varnishlog:

class { 'varnish::log': }

To manage varnishncsa:

class { 'varnish::ncsa': }

Reference

Classes:

Resources:

###Class: varnish

####enable Should the service be enabled during boot time?

####multi_instances Wether or not use the multi-instance configuration (see notes).

####start Should the service be started by Puppet?

####admin_listen_address Admin interface listen address.

####admin_listen_port Admin interface listen port.

####group Group for the varnishd worker processes

####listen_address Default address to bind to.

####listen_port Default port to bind to.

####secret_file Shared secret file for admin interface.

####storage Backend storage specification.

####ttl Default TTL used when the backend does not specify one.

####user User for the varnishd worker processes.

####vcl_conf Main configuration file.

###Class: varnish::log

###Class: varnish::ncsa

###Resource: varnish_param

This resource is a native type and a series of Augeas-based providers.

It allows to modify varnish parameters where OSes put them by default:

  • in /etc/default/varnish for Debian wheezy (as a list of parameters)
  • in /etc/systemd/system/varnish.service for Debian jessie (as a list of parameters)
  • in /etc/sysconfig/varnish for RedHat 6 (as standalone variables)
  • in /etc/varnish/varnish.params for RedHat 7 (as standalone variables)

Example:

varnish_param { 'listen_address':
  ensure => present,
  value   => 'localhost',
}

Notes

  • Version 1.x supported only multi-instances configuration. As we never use this use case, we decided to switch to a single instance configuration.
  • Version 1.99.x adds support for single instance configuration but still defaults to multi-instances configuration.
  • Version 2.x will default to single instance configuration and deprecate multi-instances configuration.
  • Version 3.x will remove multi-instances configuration support.