limits

deprecated
Puppet module for limits

Example42

example42

8,568 downloads

7,571 latest version

3.8 quality score

Version information

  • 2.0.3 (latest)
  • 2.0.2
released Aug 18th 2015
This module has been deprecated by its author since Oct 28th 2019.

The reason given was: No longer maintained

The author has suggested saz-limits as its replacement.

Start using this module

Documentation

example42/limits — version 2.0.3 Aug 18th 2015

#limits

####Table of Contents

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

##Overview

This module configures limits.

##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 limits module

  • Can manage all the configuration files (by default no file is changed)

###Setup Requirements

###Beginning with module limits

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

     include limits

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

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

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

     limits::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 { 'limits':
       config_file_template => 'site/limits/limits.conf.erb',
     }
  • You can write custom templates that use setting provided but the config_file_options_hash paramenter
     class { 'limits':
       config_file_template      => 'site/limits/limits.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 { 'limits':
       config_file_source => [ "puppet:///modules/site/limits/limits.conf-${hostname}" ,
                               "puppet:///modules/site/limits/limits.conf" ],
     }
  • Use custom source directory for the whole configuration directory, where present.
     class { 'limits':
       config_dir_source  => 'puppet:///modules/site/limits/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 { 'limits':
       config_dir_source => 'puppet:///modules/site/limits/conf/',
       config_dir_purge  => true, # Default: false.
     }
  • Use custom source directory for the whole configuration dir and define recursing policy.
     class { 'limits':
       config_dir_source    => 'puppet:///modules/site/limits/conf/',
       config_dir_recursion => false, # Default: true.
     }

##Operating Systems Support

This is tested on these OS:

  • RedHat osfamily 6
  • Debian 7
  • Ubuntu 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