Forge Home

corosync

This module installs and manages corosync

9,854 downloads

9,854 latest version

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

  • 3.0.1 (latest)
released Dec 13th 2013
This module has been deprecated by its author since Oct 28th 2019.

The reason given was: No longer maintained

The author has suggested puppet-corosync as its replacement.

Start using this module

Documentation

example42/corosync — version 3.0.1 Dec 13th 2013

#corosync

####Table of Contents

  1. Overview
  2. Module Description
  3. Setup
  4. Usage
  5. Operating Systems Support
  6. Development

##Overview

This module installs, manages and configures corosync.

##Module Description

The module is based on stdmod naming standards version 0.9.0.

Refer to http://github.com/stdmod/ for complete documentation on the common parameters.

##Setup

###Resources managed by corosync module

  • This module installs the corosync package
  • Enables the corosync service
  • Can manage all the configuration files (by default no file is changed)

###Setup Requirements

  • PuppetLabs stdlib module
  • StdMod stdmod module
  • Puppet version >= 2.7.x
  • Facter version >= 1.6.2

###Beginning with module corosync

To install the package provided by the module just include it:

    include corosync

The main class arguments can be provided either via Hiera (from Puppet 3.x) or direct parameters:

    class { 'corosync':
      parameter => value,
    }

The module provides also a generic define to manage any corosync configuration file:

    corosync::conf { 'sample.conf':
      content => '# Test',
    }

##Usage

  • A common way to use this module involves the management of the main configuration file via a custom template (provided in a custom site module):

      class { 'corosync':
        config_file_template => 'site/corosync/corosync.conf.erb',
      }
    
  • You can write custom templates that use setting provided but the config_file_options_hash paramenter

      class { 'corosync':
        config_file_template      => 'site/corosync/corosync.conf.erb',
        config_file_options_hash  => {
          opt  => 'value',
          opt2 => 'value2',
        },
      }
    
  • Use custom source (here an array) for main configuration file. Note that template and source arguments are alternative.

      class { 'corosync':
        config_file_source => [ "puppet:///modules/site/corosync/corosync.conf-${hostname}" ,
                                "puppet:///modules/site/corosync/corosync.conf" ],
      }
    
  • Use custom source directory for the whole configuration directory, where present.

      class { 'corosync':
        config_dir_source  => 'puppet:///modules/site/corosync/conf/',
      }
    
  • Use custom source directory for the whole configuration directory and purge all the local files that are not on the dir. Note: This option can be used to be sure that the content of a directory is exactly the same you expect, but it is desctructive and may remove files.

      class { 'corosync':
        config_dir_source => 'puppet:///modules/site/corosync/conf/',
        config_dir_purge  => true, # Default: false.
      }
    
  • Use custom source directory for the whole configuration dir and define recursing policy.

      class { 'corosync':
        config_dir_source    => 'puppet:///modules/site/corosync/conf/',
        config_dir_recursion => false, # Default: true.
      }
    

##Operating Systems Support

This is tested on these OS:

  • RedHat osfamily 5 and 6
  • Debian 6 and 7
  • Ubuntu 10.04 and 12.04

##Development

Pull requests (PR) and bug reports via GitHub are welcomed.

When submitting PR please follow these quidelines:

  • Provide puppet-lint compliant code
  • If possible provide rspec tests
  • Follow the module style and stdmod naming standards

When submitting bug report please include or link:

  • The Puppet code that triggers the error
  • The output of facter on the system where you try it
  • All the relevant error logs
  • Any other information useful to undestand the context