Forge Home


multi instance redis


6,528 latest version

5.0 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.5 (latest)
  • 0.1.4
  • 0.1.3
  • 0.1.2
released Aug 21st 2017
This version is compatible with:
  • Puppet Enterprise 2023.7.x, 2023.6.x, 2023.5.x, 2023.4.x, 2023.3.x, 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x, 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >= 3.0.0
  • , , , , ,

Start using this module

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

Add this module to your Puppetfile:

mod 'eyp-redis', '0.1.5'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

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

Manually install this module globally with Puppet module tool:

puppet module install eyp-redis --version 0.1.5

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.



eyp/redis — version 0.1.5 Aug 21st 2017


Table of Contents

  1. Overview
  2. Module Description
  3. Setup
  4. Usage
  5. Reference
  6. Limitations
  7. Development


multi instance redis

Module Description

This module manages redis instances.


What redis affects

  • manages redis package
  • disables default redis service, on CentOS 7 also masks it
  • creates as many services as redis instances

Setup Requirements

  • This module requires pluginsync enabled.
  • eyp/systemd is required, but it's only used on CentOS 7
  • on RH based systems eyp-epel is required

Beginning with redis

class { 'redis': }

redis::instance { '6666':


class redis, by default, installs redis and disables the default redis service:

class { 'redis': }

using redis::instance you can create as many instances as needed on a sigle host:

redis::instance { '6666':

redis::instance { '6667':


redis::instance { 'instance_A':
  port => '6666',

redis::instance { 'instance_B':
  port => '6667',




  • manage_package: = true,
  • package_ensure: = 'installed',
  • manage_service: = true,
  • manage_docker_service: = true,
  • service_ensure: = 'stopped',
  • service_enable: = false,



  • redis related variables:
    • port: port to listen to (default: resource's name)
    • bind: bind address (default:
    • timeout: (default: 0)
    • datadir: redis datadir (default: /var/lib/redis-${name})
    • redis_user: redis username (default: redis)
    • redis_group: redis group (default: redis)
    • password: optional password for redis (default: undef)
  • package and service related variables:
    • ensure: = 'running',
    • manage_service: = true,
    • manage_docker_service: = true,
    • enable: = true,


Tested on:

  • CentOS 5
  • CentOS 6
  • CentOS 7
  • Ubuntu 14.04
  • Ubuntu 16.04


We are pushing to have acceptance testing in place, so any new feature should have some test to check both presence and absence of any feature


TODO list


  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request