Forge Home

redis

Configure Redis and/or Sentinel. Only for systemd!

9,567 downloads

9,110 latest version

4.6 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 Mar 24th 2015
This version is compatible with:
  • ,

Start using this module

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

Add this module to your Puppetfile:

mod 'redbeebv-redis', '0.1.3'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add redbeebv-redis
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install redbeebv-redis --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.

Download
Tags: redis, sentinel

Documentation

redbeebv/redis — version 0.1.3 Mar 24th 2015

Redis

Table of Contents

  1. Overview
  2. Module Description - What the module does and why it is useful
  3. Usage - Configuration options and additional functionality
  4. Limitations - OS compatibility, etc.

Overview

Build Status

Easy deployment of multiple redis or instances for systems that work with systemd.

Module Description

This module can configure multiple redis or sentinel instances on one server for systems that work with systemd.

Usage

redis::instance { 'one':
  ip_address = '0.0.0.0',
  port = '6379',
  slaveof = false,
  ensure = running,
  enable = true
}

redis::sentinel { 'cluster':
  dir = '/tmp',
  port = '26379',
  ensure = running,
  enable = true,
  monitors => {
    'master' => {
      master_host             => '127.0.0.1',
      master_port             => 6378,
      quorum                  => 2,
      down_after_milliseconds => 30000,
      parallel-syncs          => 1,
      failover_timeout        => 180000
    },
    'cluster' => {
      master_host             => '10.20.30.1',
      master_port             => 6379,
      quorum                  => 2,
      down_after_milliseconds => 30000,
      parallel-syncs          => 5,
      failover_timeout        => 180000,
      auth-pass               => 'password',
      notification-script     => '/tmp/notify.sh',
      client-reconfig-script  => '/tmp/reconfig.sh'
    }
}

Limitations

The systems need to be able to use systemd unit files. If not, this module will not work for you.