Forge Home

keepalived

Keepalived module, for both or either of LVS and VRRP.

28,781 downloads

18,126 latest version

4.3 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.0.5 (latest)
  • 1.0.4
  • 1.0.3
  • 1.0.2 (deleted)
  • 1.0.1
  • 1.0.0
  • 0.1.5
  • 0.1.4
  • 0.1.3
  • 0.1.2
  • 0.1.1
  • 0.0.1
released Jul 11th 2016
This version is compatible with:
  • Puppet Enterprise >=3.0.0 <=2015.4.0
  • Puppet >=2.7.20 <5.0.0
  • , , Gentoo,

Start using this module

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

Add this module to your Puppetfile:

mod 'thias-keepalived', '1.0.5'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add thias-keepalived
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install thias-keepalived --version 1.0.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.

Download
Tags: vrrp, lvs, keepalive

Documentation

thias/keepalived — version 1.0.5 Jul 11th 2016

puppet-keepalived

Overview

Install, enable and configure the keepalived VRRP and LVS management daemon.

  • keepalived : Main class to install, enable and configure the service.
  • keepalived::vrrp : Wrapper class for VRRP-only keepalived setups.

The configuration file to be used can be specificed using either the $content parameter (typically for templates), or the $source parameter. If neither is specified, you will need to manage it rom elsewhere.

See the templates/sysconfig.erb file for the possible $options values. The default is -D which enables both VRRP and LVS.

Examples

Typical installation for VRRP only (no LVS), using a static existing configuration file :

class { '::keepalived':
  source  => "puppet:///${module_name}/keepalived.conf",
  options => '-D --vrrp',
}

Similar to the above, but using a template, which can be useful with multiple servers which will be part of the same VRRP group and/or have the same LVS configuration :

class { '::keepalived':
  content => template("${module_name}/keepalived.conf.erb"),
}

For the keepalived::vrrp class, configuration for the template needs to be passed into the $global_defs and $instances hash parameters. Their structure follows the structure of the keepalived.conf file :

case $::hostname {
  'web1':  { $vrrp_state = 'MASTER' $vrrp_priority = '50' }
  default: { $vrrp_state = 'BACKUP' $vrrp_priority = '10' }
}
class { '::keepalived::vrrp':
  global_defs => {
    router_id => $::hostname,
  },
  instances => {
    web => {
      advert_int        => '3',
      authentication    => {
        auth_type => 'PASS',
        auth_pass => 'abcd1234',
      },
      interface         => 'eth1',
      priority          => $vrrp_priority,
      state             => $vrrp_state,
      virtual_ipaddress => {
        '10.0.0.13/24' => 'dev eth0 label eth0:13',
        '10.0.1.13/24' => 'dev eth1 label eth1:13',
      },
      virtual_router_id => '13',
    },
  },
}

Note that you may also set the $global_defs_defaults parameter, which will be merged with the more specific $global_defs, which is especially useful with hiera :

---
keepalived::vrrp::global_defs_defaults:
  notification_email:
    - 'root@example.com'
  notification_email_from: 'root@example.com'
  router_id: "%{::hostname}"
  smtp_connect_timeout: '30'
  smtp_server: '10.0.45.156'